On Sat, 20 Mar 2004, Craig R. McClanahan wrote: > Miscellaneous comments intermixed. > > Quoting Martin Cooper <[EMAIL PROTECTED]>: > > > The following is a set of proposed changes to the Apache infrastructure to > > accommodate the Struts move to an Apache top level project. The idea is to > > come up with a single agreed-upon set of changes that we can submit to the > > infrastructure folks as a single request, rather than submitting each one > > piecemeal. Your feedback is appreciated. > > > > Mailing Lists > > New mail domain: struts.apache.org > > The following lists are standard for an Apache TLP: > > user@ > > dev@ > > cvs@ (usually forwarded to dev@) > > I would like to maintain our current practice that these are *always* forwarded > to dev, instead of it being a separate mailing list.
I think we agree. ;-) Currently, commit messages go to a separate list (jakarta-struts-cvs) which is forwarded to (or otherwise sent to the same people as on) struts-dev. My intent (poorly worded, I admit) was to retain that same mechanism. > > > pmc@ > > As noted in other messages in this thread, we need an announcements list too. > > Moderator: Ted Husted (same as today) > > Existing subscribers need to be migrated. > > Old list addresses should be forwarded for some period of time. > > > > Web Site > > New virtual host: struts.apache.org > > Redirect from jakarta.apache.org/struts for some period of time. > > Writeable by group: struts (see below) > > > > Wiki > > New wiki: wiki.apache.org/struts > > Migrate pages from: StrutsProjectPages on old wiki (nagoya) > > > > This would be on the Apache infrastructure, right? Yes, wiki.apache.org is the MoinMoin wiki that Leo set up to replace the UseModWiki installation on nagoya. > > > Unix Group > > New group: struts > > Members: (Struts PMC members) > > It would ultimately need to include all of the committers (not just PMC > members), in order for CVS commits to actually work. Um, yes, you're right, of course. > > > > > Source Control > > Old CVS repo: jakarta-struts > > New CVS repo: struts > > This can certainly be a starting point. We should consider whether it's worth > separating subprojects into their own repositories for ease of management > purposes (but I agree with your other comments that commit karma would still be > to all subprojects, no matter how this decision comes out). Yes. See my message on a separate thread regarding our options, and my preference, here. (In short: start with one repo, and split when we really know what we want.) > > > Optional: Move to Subversion (IMO, not now, but we can discuss.) > > > > Given the amount of work this would involve, and assuming we can import our CVS > log history somehow, this would be OK with me; but seems like something we > could also defer to later after the dust settles. My feeling on Subversion is that it's not quite ready for prime time yet. I've been watching other projects migrate, and I've seen problems crop up that have warranted new point versions of SVN. As David pointed out, client support is also somewhat lacking today, compared to CVS. Together with the fact that I can support just about any manipulation of CVS that we might decide to do, but I'm completely clueless about SVN, makes me want to stick with CVS for now. -- Martin Cooper > > > Bug Database > > Optional: Move to Jira (IMO, now's as good a time as any.) > > I'm OK with either Jira or Bugzilla. Note that other projects migrating to Jira > have been able to import their bug history, so we wouldn't lose that. > > > One other thing is that we'll want to get external mail archivers to > > switch to the new mailing lists once those are set up. I'm not clear on > > whether the infrastructure folks arrange that or we need to do it > > ourselves, but I'll ask when I submit the above. > > > > Anything else I missed? (There are a lot of internal changes we'll want to > > make as well, but I'm not trying to address those here.) > > > > -- > > Martin Cooper > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > Craig > > > --------------------------------------------------------------------- > 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]
