From the website:
Allura is an open source implementation of a software “forge”, a web site that manages source code repositories, bug reports, discussions, mailing lists, wiki pages, blogs and more for any number of individual projects.
SourceForge.net is running an instance of Allura (aka New Forge, or Forge 2.0)….
Among the many areas where topic maps could make a noticeable difference is software development.
If you have ever tried to use any of the report databases, maintained by either commercial vendors or open source projects, you know what I mean.
Some are undoubtedly better than others but I have never seen one I would want to re-visit.
But, no source code management project is going to simply adopt topic maps because you or I suggest it or someone else thinks it is a good idea.
Well, its an open project so here is your chance to work towards topic maps becoming part of this project!
Before you join the discussion lists, etc., a few questions/suggestions:
- Spend some time studying the project and its code. What are its current priorities? How can you contribute to those, so that later suggestions by you may find favor?
- Where in a source code management system is subject identity the most critical? Suggest you find 2 or at the most 3 and then propose changes for only 1 initially.
- How would you measure the difference that management of subject identity makes for participants? (Whether they are aware of the contribution of topic maps or not.)