I've nothing against all those suggestions. They're quite straightforward. Let's go for it!
>From Howard Lewis Ship <[EMAIL PROTECTED]>: > I've been thinking about the re-organization of the SVN repository now > that Tapestry is a PMC. > > Our current layout: > > https://svn.apache.org/repos/asf/ > /jakarta > /tapestry > /branches > /tags > /trunk > /annotations > /config > /contrib > /framework > (etc.) > > Here's the target layout: > > > https://svn.apache.org/repos/asf/ > /tapestry > /project > /branches > /tags > /trunk > /site > /branches /tags /trunk > /framework > /branches /tags /trunk > /contrib > /branches /tags /trunk > /annotations > /branches /tags /trunk > (etc.) > > With the goal that each sub-project (i.e. tapestry/framework or > tapestry/annotations) > be its own Maven2 module (tapestry-framework, tapestry-annotations). > > The tapestry/project folder will contain the master Tapestry project, > whose responsibility is to build all the sub-projects (again, a > Maven-ism). > > The tapestry/site folder will contain the Tapestry project web site. > This is where a lot of documentation will live, with pointers to the > web pages for the individual sub-projects. > > What I propose as the first step is to copy the existing tapestry > repository (.../jakarta/tapestry) out of jakarta and into tapestry, as > https://svn.apache.org/repos/asf/tapestry/tapestry4 > > As part of future work, as we "maven-ize" and subdivide Tapestry, we > can move or copy portions of tapestry4 up a level (and rename them as > appropriate). > > So, again. > > Phase 1: > > jakarta/tapestry --> tapestry/tapestry4 > > Phase 2: > > tapestry/tapestry4/trunk/foo --> tapestry/tapestry-foo/trunk > > Initially, all PMC members will have r/w access to the entire tapestry > repository. > > As we break Tapestry into sub-projects, we will need to come up with a > committer list for each sub-project. Part of the point of being a PMC > is to have more fine-grained control over which committers have access > to which projects. Thus, there will be people who have access to the > contrib library, but not the core framework, for example. > > I think we will need a process for moving stuff out from under > tapestry4. This includes: > 1) List of committers for the sub project > 2) Mailing lists for the sub project (though I think mostly we can > share the TLP mailing lists) > 3) Other? Not sure what else. > > I believe as Tapestry PMC chair, I'll have the rights to make all the > SVN related changes and handle authorization. If possible, I think we > should COPY (not MOVE) the jakarta/tapestry folders, and make the > jakarta/tapestry folders read-only. > > -- > 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]
