Perhaps a change in philosophy going forward will assist in keeping the documentation complete. Documentation is not something that is done after code has been accepted it should be considered a part of the code just like the BSD's do, missing or incomplete documentation is considered a bug. The hacking part of the manual talks about epydoc (which is good) but it doesn't specify that all input/output be documented -- nor does it specify the use of __doc__ strings in enough detail to make things consistent between two developers / documenters. Is there a documentation czar in the TG project? Someone with enough sway to make sure documentation is ready before the thing is blessed by TG?
+1 from me. As someone who occasionally has to work under very tight deadlines when surprises are not welcome, I would love to see some form of Linux/Debian'ish dual stable-devel branch philosophy for TG. If it is stable, it should be frozen except for bug fixes and properly documented and *always* available for download in a known good and deployable state, no matter what. If it is devel, than you know what you're getting into and you can expect to look at mailing lists, trac, etc. At the moment, I feel TG is in a bit of a weird no man's land between the two with some bits on one end, some on the other, and no clear map as to what's where. This causes real problems for new users deploying in the real world to clients who don't care about TG and only care that their websites work tomorrow. This is more work for TG admittedly, but I honestly believe a better separation of stable production ready document TG and devel TG would *greatly* increase user adoption. It's pretty much my only reservation when it comes to recommending TG to other coders. Iain --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears?hl=en -~----------~----~----~----~------~----~------~--~---
