On 1/16/07, Mark Ramm <[EMAIL PROTECTED]> wrote:
You're more than welcome. I'll definitely be organizing at least a couple more of these over the next month or two.
Thanks for organizing this Mark. I've been wishing for more help for months. ;] One question for you: I saw you mention that you'd done some diagrams but I didn't see them show up on the wiki. Did I miss them? I'd also like to thank all the sprint participants. I'm doing an editing pass on them, so look for them to start showing up on the index page this week. Rather than trying to track down the email of everybody, I'll post the pages I noticed along with some comments. If you could reply to the list, I'd appreciate it. John: * 1.0/AutoCompleteField * 1.0/BreadCrumbNaviation * 1.0/CheckedCheckBox * 1.0/DataGridWidget Have these been tested on 1.0? Florent: * 1.0/RoughDocs/CalendarDatePicker This looks mostly complete from a technical standpoint. Any problems if I edit/integrate this? Christopher: * 1.0/RoughDocs/FormValidationWithSchemas I haven't read this and it's too long to glance over. Spot checks look good. :] Andreas: * 1.0/UsingPylintToImproveYourCodesQuality This is something I really don't know about, so I get to be the test dummy. Again, thanks to everybody who participated. If I missed someone, please let me know.
> - Sprints are good for producing documentation but we need to plan time > to review, organize, revise and integrate the results as well. Karl has been looking after this, and I am very much interested in helping out in that area as well. If we have people producing content at a reasonable rate, we should be able to edit, organize and integrate it as we go.
I can do copy editing, formatting, organization/integration pretty quickly. It's easier because I can put in an hour here and there without getting lost. I like to have a full afternoon to write a new doc because I lose track of what I'm doing and never get around to finishing stuff. The big time sink is actually testing stuff to ensure what you're writing is true.
I'll also try to help by pointing people to the areas that need the most documentation work, so that they are producing the right kind of new content.
If you're looking for something to do, shoot me an email with how much work you'd like and I can definitely direct you to something.
I think lots of effort needs to take place outside of the DocSprints, and I expect that effort to happen more and more as we involve new people in the project through aditional Doc Sprints. At the same time, I think we're actually closer to having full 1.0 quality docs than your 10 sprints figure would suggest.
I think that there's around 80-100 man hours left in what I planned for 1.0 docs. The vast majority of it is in widgets and docstrings.
I don't think we should unlock everything, but I think we should definitely grant the equivelent of SVN commit access to the Docs a bit more liberally.
I'm quite liberal about this. I don't want to do any more than I have to. If I see someone making substantial comments/edits that I'm basically rubber stamping, you get editor access. Additionally, all current SVN committers should have editor permissions so you can correct docs bugs (ask Kevin or Lee if you don't). The main reason it's locked down now is because I (or Adam or Fred) have personally vetted the information in the locked down pages. There are enough well-meaning but incorrect comments for me to keep it that way. I try to update the page as soon as I see the comment (I do a comments pass almost daily). I'm trying to keep this from becoming one of those project wikis where you're never sure what you're reading is correct or not. I really need to do something to make the locked down official pages more visually distinct than the freely editable ones.
I don't think we need weekly IRC meetings, but more process discussion on this list is a great idea, as is process/organizational page on the wiki.
The DocHelp[1] page isn't good enough? [1] http://docs.turbogears.org/DocHelp I'm not big on process, it's just a personal bias. I'm not opposed to IRC meetings, but there hasn't been enough people involved to make such a meeting worthwhile. What I should be doing is putting my todo list on the wiki so people can pick off the low hanging fruit (e.g. there are a number of mailing list posts that are worth saving for posterity). I got distracted from doing this before the sprint. I'll try to get this up sometime this week.
We need to work together to get more people involved in documentation, and to provide them with positive feedback right away when they contribute something.
I'm still working through the changes made during the sprint, but it's mostly looking good. Formatting wasn't quite right on most pages, but that's a quick fix. I haven't gotten to the more substantial articles yet. Those should come tomorrow and possibly the day after. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears Docs" 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-docs?hl=en -~----------~----~----~----~------~----~------~--~---
