That's a very good idea. I know I've confused people in the past, since the general practice was to name lists "foo-users" and "foo-developers". It wasn't intentional, I just hadn't seen what other projects have done. Tapestry users talk on "foo-developers" (i.e., "I develop *with* Tapestry").
It's time to create a "tapestry-contributors" list, i.e, "I contribute code to Tapestry". The move to Apache/Jakarta will probably entail moving mailing lists from SF to Jakarta ... at that time, we can start fresh and have a "-users" and "-developers" lists, like everyone expects. I'll be setting up the tapestry-contributors list shortly, unless there are any objections. ----- Original Message ----- From: "Craig Miskell" <[EMAIL PROTECTED]> To: "Howard M. Lewis Ship" <[EMAIL PROTECTED]> Cc: "Tapestry Developer" <[EMAIL PROTECTED]> Sent: Wednesday, October 30, 2002 1:55 PM Subject: Re: [Tapestry-developer] [VOTE] Adopt Apache Voting Rules > This may be a little premature, but may I suggest that this might be the > point to split the mailing list in two... one for "users", and one for > "developers". Issues coming up for vote could be advertised in the > "users" mailing list, but I wouldn't want to see the user mailing list > cluttered with +1/-1 replies whenever a voting issue comes up. That > should be reserved for the devel list. Those who just want to use > Tapestry can ignore "devel" and just watch "users". > > Any thoughts? > > Craig > > > On Thu, 2002-10-31 at 02:19, Howard M. Lewis Ship wrote: > > DISCUSSION: > > > > I think we should do a vote to check that the "grandfathered" committers are reachable (subscribed to and monitoring the list) and in the loop (ready to discuss and vote). We can then vote on future items, such as addining additional committers, changing the license for the framework and (eventually) moving over to Apache and/or Jakarta. > > > > There are also other decisions coming with the framework; for instance, my ideas for Tapestry Lite are controversial and could be discussed further. > > > > See http://jakarta.apache.org/site/guidelines.html for details on what this entails. > > > > What does this mean? > > > > It means that for all significant decisions, an action item will be created and a vote called for. The results of the vote determine whether the action item proceeds or is discarded. > > > > I'm hoping Dion and Oliver (our new friends at Jakarta) will be able to help with the exact process. To be honest, I haven't been able to determine (from the documentation) the exact granularity of an action item. For instance, I doubt we'd need to vote on whether to fix bugs in the bug list ... but what if the fix causes a non-backwards compatible change? > > > > PROPOSAL: > > > > The Tapestry community should immediately adopt the voting meritocracy guidelines of the Apache project, as detailed in > > http://jakarta.apache.org/site/guidelines.html. > > > > VOTES: > > > > Howard Lewis Ship: +1 > > Mind Bridge: > > Malcolm Edgar: > > Richard Lewis-Shell: > > > > ---- > > Howard Lewis Ship > > [EMAIL PROTECTED] > > http://tapestry.sf.net > > > > > ------------------------------------------------------- This sf.net email is sponsored by: Influence the future of Java(TM) technology. Join the Java Community Process(SM) (JCP(SM)) program now. http://ads.sourceforge.net/cgi-bin/redirect.pl?sunm0004en _______________________________________________ Tapestry-developer mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/tapestry-developer
