JIRA and TRAC both have remote capabilities which is how Eclipse is able to interoperate with both directly. So by that same token, you could create a ExtJS frontend for either.
However, Trac is free, JIRA is not. And there might be confusion with their open source exception, so it is best to just avoid it and any hastles that might come from that.
As for the idea of having workarounds -- I like that. Perhaps if we have our own bug database, we can restrict bug reports to only those that have workarounds. Not being in the Core group of ExtJS, I don't see much of a point of handling one otherwise.
I have a version of Trac for ExtJS. I'll populate it with some changes to Ext that I made over the years. Would be a better source of documentation than I have now! Anyone else interested in putting in bugs that have fixes or workarounds?
Definitely willing to help transfer stuff from the forums.
Since there is already a bug forum here, and I don't want to replace it as a forum to ask if something is a bug, etc. But for those that are above noob level, know what the problem is AND have a solution, then this might be a good source.
I think it ought to be for things already filtered with proposed fixes for it to be worthwhile.
Excellent, thank you. This is a great place to start, though it strikes me as more of a patch tracker than a bug tracker I still believe that we really need a single bugtracker that store the current state of knowledge about defects in ExtJS. But that will require involvement from the devs, who have been silent hitherto.
Anyway, thanks very much Stever. How do you want to play it? Should people apply to you for logins, or do you want to update it yourself?