On Jan 14, 2011, at 10:19 AM, Massimo Di Pierro wrote: > > +1 One good practice that would help out a lot. When possible, whenever you find or fix a bug in gluon, write a unit test that shows the bug, and *then* fix the bug.
> > On Jan 14, 11:37 am, cjrh <caleb.hatti...@gmail.com> wrote: >> On Jan 14, 5:21 pm, António Ramos <ramstei...@gmail.com> wrote: >> >>> hello, to help web2py in the best possible way and in the least amount of >>> time , why dont Maximo suggest the plugins or areas where ther is a lack of >>> a plugin or code. >> >> There is always a need for testing, as trunk is quite active, and >> there is always a need for improved documentation. Coding always gets >> the glamour, but the other stuff is hard work too, and arguably as >> worthwhile. >> >>> This way we, discipules of py, dont loose time with details and get a real >>> chalenge from the Master ? >> >> Testing and documentation are so challenging that very few open-source >> projects spend any time at all on them :) >> >> The other, REALLY important point to make, for anyone else reading >> this, is that testing and documentation are perfectly suited to >> newbies, because they are least likely to gloss over poor areas that >> experienced people simply ignore, especially with documentation.
