+1. My suggestion is to have an as detailed as possible changelog when a new version is released. This is a lot of time, admittedly, but would allow for people who do not enjoy spending the whole day in the gluon dir to integrate these detailed changelogs into the actual docs and take some load off Massimo wrt to docs. Sooner or later most OSS projects come to the point where they need to appoint someone to be in charge of docs as usually the core developers are more keen on coding than formatting docs or making examples. I don't know if we are just near or have already crossed that point :)
On Feb 24, 10:15 am, Joe Barnhart <joe.barnh...@gmail.com> wrote: > It seems to me that we have reached a critical point in web2py. > > The development of web2py has been at such an accelerated pace that > the environment has far outpaced its pool of documentation and > examples. I am using the latest stable version and loving the new > capabilities of "auth" and "crud", but I find I'm spending an > increasing amount of time in the gluon directory, trying to read and > understand the source. > > Maissmo's web2py book is an excellent starting point, and it got me > through the basics and well into my first web2py site. But there is > so much to learn -- so many ways of solving the common problems that > surface again and again. I look to the wiki and the mailing list, but > the answers just aren't there, or are so diffuse that it's hard to > find them. > > This is a critical point because we have the chance to make web2py > "mainstream", but only if we can get the information flowing at a pace > equivalent to development. Documenting is not as fun as development. > But if users must read the source to understand how to create sites, > we will never turn the corner and make web2py the success it could be. > > From where I sit, documentation and examples are the #1 problem faced > by web2py today. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py Web Framework" group. To post to this group, send email to web2py@googlegroups.com To unsubscribe from this group, send email to web2py+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---