And that's why you use dogfooding, so your software is solid. I'm sure the web2py.com site is solid and bug-free, but that issue tracking is not dogfooded and it is very buggy and difficult to use, if usable at all. It may be a starting point for building an app, but for example the issues linking to projects are by ID number, not by name, so it's broken if you are trying to track issues for multiple projects. To create a manager you have to manually modify the authentication tables, and there are a lot of places where you reference by ID number instead of by the name of the object. That may be okay if you have ID numbers all memorized. I'm guessing most people don't and certainly wouldn't want to memorize those ID numbers.
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. On Monday, April 23, 2012 2:37:47 PM UTC-7, Derek wrote: > > That issue tracking app is quite broken, having tried it myself. though > from what I hear the forum is solid. I don't know why we aren't using > pyforum. > > On Monday, April 23, 2012 1:33:13 PM UTC-7, Anthony wrote: >> >> >> Back to the original topic though - Why doesn't web2py do more >>> dogfooding? I know that using code.google.com is good since it's free, >>> but come one, let's show the world that Massimo puts his money where his >>> mouth is... >>> >> >> Currently on the canine menu: >> http://web2py.com <http://web2py.com/examples/default/index> >> http://web2py.com/book >> http://www.web2pyslices.com <http://www.web2pyslices.com/home> >> http://web2py.com/poweredby >> http://www.web2py.com/appliances >> http://web2py.com/layouts >> http://web2py.com/demo_admin/default/site >> (not to mention some legacy apps, such as AlterEgo, web2py Plugins, >> and web2py Wiki) >> >> And of course, Massimo and all the contributors are using web2py for >> their private projects. >> >> I'd rather see the community spend more time improving (and documenting) >> the framework and building a robust CMS than adding dog food just for the >> sake of "dogfooding." Note, the community isn't using them, but we do have >> existing forum <http://pyforum.org/>, Q&A <http://www.qa-stack.com/>, and >> issue-tracking <http://www.i-track.org/> apps. >> >> Anthony >> >> >
