Closing issues is the way to go. Rewriting anything - bright idea at first, the worst idea at the second thought. Fixing documentation is a more correct approach, because it won't require hunderds of hours spent just to make it look 'the way you think is the best'. Better start small like closing issues, fixing documentation. 99.9% of contributors get tired at this stage already.
2013/5/15 Leandro - ProfessionalIT - Soluções em Tecnologia da Informação. < lean...@professionalit.com.br> > Hi Tae, > > I think that is very interessant too, we have a "way", a standard, or > conventions to create a project with web.py, a convention to create files, > for example, ever init your project with a file called code.py, have a file > called forms.py, have a file called render.py, put your templates in a > folder called templates and your static files in a folder called static, or > be, a example_project, AKA blank_project in another frameworks. > > I don't know but my first impression of web.py was: OK, it's easy, > let-me free to choice, but what's the best way to create a project ? how to > organize a project with subapps ? and etc. > > Atenciosamente, > Leandro Severino - *P*rofessional in *I*nformation *T*echnology. > *MSN*: lean...@professionalit.com.br | *GTalk*: lsever...@gmail.com |* > Skype*: leandro-professionalit > *Site*: http://www.professionalit.com.br | *Blog*: > http://blog.professionalit.com.br | *Twitter:* > http://twitter.com/professionalit > *Mobile:* (51) 9390.3511 (Claro) e (51) 8272.5841 (TIM) > > > > > > > On Wed, May 15, 2013 at 10:28 AM, Tae Sandoval Murgan > <taeci...@gmail.com>wrote: > >> I think the first step is to close issues. Some of them seems already >> solved, but aren't closed so the project seems abandoned. We need >> Anand for that, no? >> >> The second step could be to rewrite the documentation. There's is a >> lot of repeated information, and also a lot of missing information. I >> think we should merge the Cookbook with the Tutorials. What do you >> thing about that? >> >> I'll work on improving the Form class this weekend, considering the >> Steven's suggestion ;) >> >> -- >> You received this message because you are subscribed to the Google Groups >> "web.py" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to webpy+unsubscr...@googlegroups.com. >> To post to this group, send email to webpy@googlegroups.com. >> Visit this group at http://groups.google.com/group/webpy?hl=en. >> For more options, visit https://groups.google.com/groups/opt_out. >> >> >> > -- > You received this message because you are subscribed to the Google Groups > "web.py" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to webpy+unsubscr...@googlegroups.com. > To post to this group, send email to webpy@googlegroups.com. > Visit this group at http://groups.google.com/group/webpy?hl=en. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- You received this message because you are subscribed to the Google Groups "web.py" group. To unsubscribe from this group and stop receiving emails from it, send an email to webpy+unsubscr...@googlegroups.com. To post to this group, send email to webpy@googlegroups.com. Visit this group at http://groups.google.com/group/webpy?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
