Any project such as bug tracking or CMS should go on their own. That would be the best solution. It would do the following: - prove that a different group of people not directly involved in web2py core development can build a complex app on top of web2py. - help testing web2py on a large project with a positive feedback to web2py itself. - push improvement on documentation to ease the adoption of web2py. - show that there web2py is suitable for long term projects.
Just take Redmine as example. Redmine is not developed as part of the RubyOnRails effort. mic Il 24 aprile 2012 21:49, pbreit <[email protected]> ha scritto: > Google Groups is very good so I don't see any need to move away from it. > StackOverflow doesn't work very well for these types of discussions. > > As far as dogfood, it would be nice to have a package or two getting some > usage such as Blog, CMS or wiki. A wiki for tips, tricks and sample code > would be great (yes, I'm aware of Slices).
