On 2/6/07, DarkBlue <[EMAIL PROTECTED]> wrote: > > > > 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.
yes indeed, but I stand clear with the users concept I agree that you will be a "user" if your first starting with the framework but you can't stay there because that will just hurt the comunity. At least if everyone is there. >>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. At that point in time I was refering to a comment that suggested stop developing and get to write docs, in that case "we are all equal" because the only ones that knows how some bit of code works is whoever wrote it. 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. same as above. 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. Yes indeed but we should focus on developing documentation for the "glue code" TG is and of course any plugin and/or application that is made on top of it, like catwalk or tg-admin. Now if there is a deficiency on documentation for one of the projects that are the foundation of TG that needs to be address first with them and then try to do it at "their site" and last making a duplicate. because not reusing documentation sources is as bad as not reusing code from those projects. > 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 -~----------~----~----~----~------~----~------~--~---
