Mark Ramm wrote: >> 2) Some more release-management assistance. It's been two months >> since 1.0b1 came out. That's *way* longer than I anticipated or >> wanted, but I haven't been in a position to do anything about it >> because of other commitments (and this has also been true for >> Elvelind). As we've broken TurboGears up into an increasing number of >> separate, but related, projects, making a release has become a bit >> more cumbersome. What I'd really like here is for someone to help >> script an easier way to put out a TG release. > > I'd like to help with this. We definitely need a way to build > releases more easily. People are encouraged to submit patches and fix > tickets when they know it will show up quickly in a released version. > And one of the most critical pieces of Open Source project managment > is keeping developers motivated and engaged.
... and one of the prime tenets of agile development is "release early, release often". The smaller the increments between releases, the easier it is for those "at the bleeding edge" to stay current without running from the repository (something which I don't even do for Python much nowadays). > >> 3) More hands in the code. I have gathered that there are many people >> who would love to help out on TG itself, but aren't sure where to >> start (both in terms of what to do and how to do it). This problem is >> easily solved and is especially important, because we're going to be >> heading more firmly into the First Class development cycle, hopefully >> with alpha releases before too long. There are some specific ideas >> for what we want to do in that release, but there are no specs that >> would allow someone other than me and a small group of others to >> really work on it. I'm not talking about stupidly long requirements >> docs that you find at a BigCo. I'm talking about a simple, plain >> English overview with a little detail as to what the feature is plus, >> importantly, some thoughts on how to do it, where to look, etc. > This would undoubtedly be helpful. But ... > We could write these specs up in a wiki somewhere. I think the docs > wiki is probably the right place to do this, because we might want to > copy stuff from the specs into the final documentation. But it's > also nice to have it in Trac, because then you can trivially link to > specs from tickets, etc. > > What do you think? > > My suggestion for how to get started on this would be to write up a > quick sample spec, that others can emulate when writing up new specs. > Then we could have a "Spec sprint" to write up some things that are > already pretty clearly going to go into first class. ... I suspect what's either (possibly) missing or (more likely) not currently pointed to determinedly enough is an architectural overview showing the API relationships of the current bits. The famous graphic is OK in terms of the gross relationships between the components, but after a month working part-time with TG I'm only just beginning to feel that I understand the architecture. Not only would such notes encourage contributors, they might also reduce the amount of time those on this list who *are* familiar with the architecture spend answering questions that seem insurmountable to the questioners but often turn out to be quite trivial for those in the know. I don't underestimate the effort this would take. Maybe we need a two-level effort, where the documenters can ask the architects off-line and then tun the answers into documentation. Or something like that. regards Steve -- Steve Holden +44 150 684 7255 +1 800 494 3119 Holden Web LLC/Ltd http://www.holdenweb.com Skype: holdenweb http://holdenweb.blogspot.com Recent Ramblings http://del.icio.us/steve.holden --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
