So, I think the first step is to figure out who the PMC is, and who the Chair is.
I think a good guess for the PMC would be all the active members of Tapestry (in no order): HLS, HK, DS, MB, JK, KT, GL, PF, RLS In terms of Chair, we're looking for someone with a long term experience with Tapestry. We have a wide mix of activity levels at different times. Over the long term, DS and MB are probably the biggest contributors after HLS. PF and JK are on the way up, but are fairly recent. GL has moved mountains, but from the outside (Spindle). Please don't interpret these as slights; these are my observations. So, I think a good start would be to see if DS or MB is interested in the Chair. I'm hoping that the Chair position is not a big time sink; I really think it's mostly about quarterly communication with the apache board; you can see Henri's most recent report: http://jakarta.apache.org/site/pmc/board-report-december2005.html Thoughts? Comments? On 1/12/06, David Solis <[EMAIL PROTECTED]> wrote: > IMO, this topic is very important and it would be the next level for > Tapestry. Some of my clients think Tapestry depends too much on Howard > Ship. > > Regards > > D. > On 1/10/06, Howard Lewis Ship <[EMAIL PROTECTED]> wrote: > > Anyone up for tapestry.apache.org? (I noticed we did have a discussion > > about this back in March.) > > > > I've been saying for some time that Jakarta is turning into more of a > > second-level incubator; all successful projects (including Ant and > > Struts) have migrated up to top-level projects. It's been made clear > > to me that this is not only possible for Tapestry, it is desirable. > > > > In organizational terms, this would mean that Tapestry would have its > > own Project Management Comittee. We would have to produce quarterly > > reports to the Apache board. Our home page address and mailing list > > addresses would change. > > > > The advantage is that we could break Tapestry into smaller pieces > > (projects within the TLP) and each sub-project could have its own set > > of committers. This, combined with using Maven 2 for builds, would > > give us a lot more flexibility and room to breathe. > > > > However, it requires a chairman to report to the board and I'm pretty > > desperate for that to ** not ** be me. I say this out of a mix of > > lazyness (I'm already too busy), self awareness (I do terribly at any > > kind of organization stuff) and political savvy (it would some ways > > demonstrate that Tapestry can survive without HLS). > > > > A TLP move would also be a good time to: > > - Rethink our release numbering strategy > > - Create new project marketting assets (icons, etc.) > > - Ask HiveMind if they would like to move from Jakarta to Tapestry > > > > > > On that second point ... does anyone have any ideas about refreshing > > the Tapestry marketting assets? It might be nice to have someone > > (semi-)professional design new icons and such. The Circle-T is really > > looking dated! > > > > > > -- > > Howard M. Lewis Ship > > Independent J2EE / Open-Source Java Consultant > > Creator, Jakarta Tapestry > > Creator, Jakarta HiveMind > > > > Professional Tapestry training, mentoring, support > > and project work. http://howardlewisship.com > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Howard M. Lewis Ship Independent J2EE / Open-Source Java Consultant Creator, Jakarta Tapestry Creator, Jakarta HiveMind Professional Tapestry training, mentoring, support and project work. http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
