> > If you can draw diagrams, or convert files from wiki markup to REST, > > you can make a meaningful contribution. So, the only reason not to > > get involved is that you have other higher priority things to do. > > And if that's the case, please don't vent your frustration at other > > people who might also have other important things to do and spend less > > time on documentation that you would like. > > I don't think Steve is *just* venting, and I believe his comments > definitely have a place.
Agreed, it's the tone of the conversation that got my hackles up. We are in agreement that the problem right now is 1.0 documentation. And the solution is hard work. Policy changes can impact 1.1 or 2.0 features but we're not there yet. Our current problem can only be solved by working on 1.0 docs. If we want that done right away, we could use some help. What I was saying is that nobody is obligated to do that work. Not me, not you, not Steve. But if we work together we might be able to get it done faster. > Telling him not to say things like this simply > encourages people to "silently leave". I certianly didn't mean to tell Steve not to raise the issue. It is an important issue, which I've been raising in a different way by trying to host Doc Sprints, and work involve more people in the Documentation process. > If there is no room for critique and > argument over project direction, that alone would send me away and > ensure I never become a contributor. Of course, that's not what we want. Your participation and contribution should be encouraged. And, I don't even mind critisism. What I mind is that what we need *right now* is more people writing docs, and your posts seemed to me likely to discurage the people who've been working hard on the problem, and to encourage us to make policy changes which might help in the future, but which won't solve the current problem. > I understand your frustration with the vent having obviously put a lot > of time into docs. I think the situation is something that should be > discussed more thoroughly at the project management level. I agree with this. Though I personally haven't done all that much with the online docs. It's just that I know other people who have, and I feel bad for them. I believe we are on the right trajectory again, after we veered off course with the docs in 2006. I think issues concering 1.1 (and later) docs would be helpful on the Trunk list where those decisions are currently being made. But right here, right now, the key is putting in the work to get the 1.0 docs up to speed. And most importantly that means getting API docs generated. We need to find a way to make one of the API documentation programs work on our code base. If anybody can help with this, please let me know --Mark Ramm --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
