> > So, why does the issue tracking suck? Because it was just written as a > proof of concept. Why isn't it getting any better? because we aren't using > it. Why aren't we using it? Because it sucks. I think if others saw that > web2py was a stable solution by virtue of the fact that we are using itself > to track the issues instead of relying on google code, it would be a good > thing. You've got janrain, so let everyone login using their google account. >
Yes, if we were using the issue tracking app, we would make it better. We simply have to ask whether that is the best use of our time. How important is it for web2py to have a great issue tracker (given the many excellent existing options out there), rather than, say, a great CMS, or better documentation, or more test coverage, etc.? For issue tracking, Rails uses Github and Django uses Trac; and both use Google Groups for support (and both have a major presence on Stack Overflow as well). We don't have to dogfood everything. Anthony
