Count me in for documentation. I don't know if I'm the right person to lead it, but I'll definitely be doing what I can for it.
I've got some products that I want to create that will benefit from using turbogears as the backend. And, in order to use them (and sell service/support to my customers), I need the documentation to be top notch. We'll get things noticeably improved soon. I'm probably not the best choice for contributing to QA, though I'll try. As for the changelog, though... I'll start working on it. Will probably need some small help getting myself started from one of the core devs. I'll just hit you guys up via IM/IRC tomorrow, make sure I've got the startup that I need, and start harassing people from there. Michael J. Pedersen My IM IDs: Jabber/[email protected], ICQ/103345809, AIM/pedermj022171 Yahoo/pedermj2002, MSN/[email protected] On Sun, Jul 5, 2009 at 3:32 PM, Mark Ramm <[email protected]>wrote: > > There are two other areas that I think need focused leadership attention: > > * Documentation > * Quality Assurance > > There's been quite a bit of good activity on the documentation front, > and I'm particularly interested in merging some of that work back in > to the docs trunk soon. One piece of the documentation picture that's > not been working as it should is the 2.1 changelog. If someone would > volunteer to go through the commit history on bitbucket and make sure > to pester 2.1 developers who made changes to take a few min out of > their busy schedules, and document them that would be great. > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears Trunk" 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-trunk?hl=en -~----------~----~----~----~------~----~------~--~---
