> > Mr. Ship has approached Apache about Tapestry becoming a Jakarta project. > We're impressed by the amount of support, etc. this project has and the > community building around it. Great job!
Thanks. It's been a lot of work. > > Myself, Dion Gillard and others are interested in the proposal. Jakarta > has experienced rapid growth over the years and its felt some growing > pains. In order to rectify this new procedures are being put in place > and a "reorganization" of sorts is happening. Its my goal to work with > the project to gain acceptence within this environment, while insulating > Tapestry folks as much as possible from the issues surrounding it to > avoid any potential misunderstandings and frustration. Among things that > are on the table is the possibility of projects such as Tapestry > becoming top level ASF projects (meaning an equal level to Jakarta not a > subproject), but while you might want to keep a preference in the back > of your minds, I don't think it needs to be a key concern. I haven't been following this; I've always expected "Jakarta" to be the server-side Java projects and "xml.apache.org" to be XML projects (some in Java). I'm concerned that Tapestry at the top level will isolate Tapestry from the mindshare of Jakarta, leaving the project in not better situation than on SourceForge. > > I think Apache has a lot to offer Tapestry and vice versa. There are > however some issues to be addressed from the Tapestry side BEFORE any > move is possible. > > 1. Identify at least 3 committers (should be the principal active > contributers). These people will have CVS priviledges and voting > privilages over the project. I would suggest that we start with this group, and follow a nomination process to add additional committers. Or you can assume I'm nominating the others. This is a subset of the list of committers on SF. Sorry if I'm underplaying anyone's contributions. Howard Lewis Ship <[EMAIL PROTECTED]> I hear voices and do what they say. There's brocoli in my socks. Mind Bridge <[EMAIL PROTECTED]> Vocal proponent, contributor of components and bug fixes, mentors on the mailing list frequently. Malcolm Edgar <[EMAIL PROTECTED]> Contributes components and mentors, created Tapestry component reference. Richard Lewis-Shell <[EMAIL PROTECTED]> Very long-time user, contributes bug fixes, mentors on the mailing list. Ming Fang, Neil Swinton and perhaps David Solis are other possibilities. Neil has mostly been active on the documentation side. Ming Fang and David have not been visibily active in a bit, but still seem to be involved. > 2. Adopt Apache voting rules (http://httpd.apache.org/dev/guidelines.html) I think we've been pretty OK about discussing changes in advance, using a mixture of the Wiki and the mailing list. I'm holding off on some controversial changes (Tapestry Lite) until we go though the voting process for it, it looks like it'll require consensus approval since a few people are very negative on it. > 3. Vote on relicensing from LGPL to ASL > (http://www.apache.org/LICENSE.txt) which is an apache requirement. As > part of this process you need to contact any major contributors and ask > them if its okay. Keep that list handy. I don't think that'll be a problem. > > Implications: > > When you move to Apache the code becomes the property of the Apache > Software Foundation (for many reasons especially liability, etc). So > all major contributers must agree to that as well. (if they have not > assigned their copywright already as a condition of donating to the > project). All copyrights have been assigned to me (HLS), that's in the Contributor's Guide, and is a condition of donating code to Tapestry. So this should not be a problem. It does mean updating the copyright on ~500 source files! > > While our new process is evolving, these (http://jakarta.apache.org/site/newproject.html) general guidelines should help you get an idea on what the requirements for the project will be for acceptance regardless. I think this was covered pretty well in the initial proposal. Outside of what's discussed here, are you aware of any outstanding issues? > > Please let me know if there are any questions or concernes. If you're willing to move forward with this process, I'll work as a resource to help you through this process. > > Thanks, > > Andrew C. Oliver > Apache committer to Jakarta POI, Lucene > contributer to Apache XML Cocoon 2 and Jakarta JAMES > > > > > ------------------------------------------------------- > This SF.net email is sponsored by: ApacheCon, November 18-21 in > Las Vegas (supported by COMDEX), the only Apache event to be > fully supported by the ASF. http://www.apachecon.com > _______________________________________________ > Tapestry-developer mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/tapestry-developer > ------------------------------------------------------- This SF.net email is sponsored by: ApacheCon, November 18-21 in Las Vegas (supported by COMDEX), the only Apache event to be fully supported by the ASF. http://www.apachecon.com _______________________________________________ Tapestry-developer mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/tapestry-developer
