Forum OpenACS Q&A: Re: OpenACS.org upgrade (was: Openacs.org having problems. Refrain from using it until Sept 25th)
As I'm not able to tune bug-tracker, we have a couple of options:
a) Delay the upgrade til someone tuned bug-tracker
b) Upgrade but leave bugtracker on the old openacs.org
Last but not least, a maybe heretic question: How about tanking bug-tracker altogether for openacs.org and make use of sourceforge (for the bug-tracking)?
Though the last approach would mean we are not eating our own s*** anymore, it has a couple of advantages:
1) We could finally upgrade openacs.org
2) OpenACS would get great exposure on sourceforge
Bug tracker contains a lot of code to handle categories in a hierarchical manner, if we'd use category system, we could just reuse the functions written therein. Furthermore, it would be a good reason to integrate categories with listbuilder (unless it is already done), meaning, you can map multiple category trees to a package and the listbuilder would display them automatically like the bug-tracker currently does manually.
Last but not least, it would allow us to use multiple categories within one tree, something that would break the current bug-tracker. Useful if a bug e.g. belongs to more than one package.