Given the subject of this thread , I believe that anyone who renders feedback is basically taking part in a brainstorming session, to provide ideas ( good , useable or maybe utter nonsense) in order to help the actual developers , maintainers of documentation and other aspects of TG to see , what users actually want to get out of it. Any feedback posted here says WE CARE about TG . Now opinions are different.
>>It is paramount that documentation is up to speed with releases. > > Maybe any new version should only come out of beta when the docs > > are uptodate too. This would give a far better and mature impression. Jorges reply to that: > I totally disagree I prefer underdocumented and working than nothing at all. Documentation is here for those who do not know how it works , for those who want to find out how it works and for those who want to learn how it works. It is not intended for those who already know how to use the undocumented stuff of a new release. I only can say , that if it is not documented , people will test it for 2 minutes and if they cannot guess how to go beyond an initial quickstart application , they will move on to do something else. TG is a good idea , making var. opensource packages working together to increase a developers efficiency. Documentation is the main entry point and also what gives structure to the project. Especially considering TG's evolving nature and many changes which are expected in the coming releases. DB --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
