On Feb 5, 10:07 am, "Karl Guertin" <[EMAIL PROTECTED]> wrote: > On 2/5/07, tamara6 <[EMAIL PROTECTED]> wrote: > > > With my answer. I think documentation for SO could be better. I feel > > like it has been forgotten in the rush for SA. > > That would be true if we had docs for SA. Actually, we're trying to > get TG-specific components covered first and then branch out into > filling in component documentation.
I don't think Jorge Vargas agrees with you: On Feb 5, 11:37 am, "Jorge Vargas" <[EMAIL PROTECTED]> wrote: > What I want to say with this is that > we are aware of the situation we know there is a problem but it seems to be > the concensus that it's better to move to SA then "fix SO" either at the > docs or code level. Look, TG is using SO *right now* If you don't want to write docs for SO then make the switch to SA immediately and write docs for it. The point is that it is just plain dumb to incorporate something as a tool and then not have docs for how to use it. And it is very confusing to use who are just starting out. If I use SO today, will support be dropped for it tomorrow? Will I have to re- write everything using SA in a year? If so, just say so. I'll go away and come back when your projoect is more stable. But if support for SO will continue, then docs written for it today will not be wasted because they will still be of some use in the future. Tamara --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
