Having just looked through some sites regarding SCM because of the discussion regarding the beta, the fact that there's no real SDM in OACS4.5 and due to some of my thoughts for the new OACS site (specifically a developer.openacs.org which I mentioned in a thread a few months ago), I would like to start a discussion of how we can address a system that is either for or in the new toolkit.
I know that there are some people out there that have thought about what a new system might look like (namely Carl Coryell-Martin and a fellow whom I met at the SF social named Alan, IIRC). I think both of them have looked at both ticket-tracker and SDM as a solution. I also know that Gilbert also posted a call to the bboards about possibly looking to build a software development package using OACS.
One question that should be asked is whether the community might abandon trying to build this kind of application all together. Ben did a great job with SDM and it's an amazing starting template for a new system. However, it's in the old toolkit and no one seems to be continuing to work on it.
Also, rather than just porting the code to OACS4 it seems (based on some conversations with others) that it's better to start all over and write a new system using nice OACS4.x pieces like workflow and/or subsites.
However, I would also hope we're not overcome by NIH syndrome. There are some decent pieces of code out there that are probably not as good as what can be built using OACS4.x, but they are already built.
So the first question to ask is whether there is community interest and justification for building another open source development manager. The solution to this might be using another system, porting SDM to OACS4 or just continuing to use SDM in OACS3.x
If the answer is yes (and I do expect that it will be), then I suggest we use this thread as a call for a feature list of items for what we might want. This includes some of the following items that are important for the OACS project, but also would be tremendously helpful for vendors or consultants servicing clients (many of which come from what I need for my clients):
- Bug tracking and bug assignment
- Feature requests
- QA and assignment
- Support requests and assignment
- SCM integration (either tied to CVS or abstracted to work with any SCM tool like Subversion, Perforce or Bitkeeper) I think this is a very general list so I hope that others have ideas that they can add.