Pinging this back onto your todo list. 2 is the big one. The easy option is to just:
* move jakarta-cactus HEAD to jakarta/cactus/trunk * move all jakarta-cactus branches to jakarta/cactus/branches * move all jakarta-cactus tags to jakarta/cactus/tags Otherwise it'll take thought etc. Looking at the cactus module, it looks like you would probably take the easy option and worry about being clever later on. Hen On 1/4/05, Henri Yandell <[EMAIL PROTECTED]> wrote: > The Infrastructure guys take care of all the server-side stuff; it's > very easy from our point of view: > > 1) Convince community to migrate > 2) Decide on structure > 3) Send request to Infra (template to do this with) > 4) Organise community to test the repo they setup > 5) Announce go-ahead > > Also things like updating the site etc. > > Hen > > On Tue, 4 Jan 2005 08:16:53 +0100, Vincent Massol <[EMAIL PROTECTED]> wrote: > > > > > > > -----Original Message----- > > > From: Henri Yandell [mailto:[EMAIL PROTECTED] > > > Sent: mardi 4 janvier 2005 04:13 > > > To: Cactus Developers List > > > Subject: Re: Subversion migration > > > > > > Yep, Apache's on the https/http. Quite a nice setup too. > > > > > > For osjava; we have the http as anonymous and the https as secure; but > > > Apache has the https as anonymous too for most modules and it's only > > > when you commit that you have to enter a username/password. > > > > > > Nice part here is that a contributor can be checked out; become a > > > committer and not have to worry about rechecking out. > > > > > > As you've SVN experience, would you be willing to volunteer to manage > > > the migration Vincent? > > > > Why not, but I would need some help as I have never touched the server-side > > part of SVN (only the client part). > > > > Thanks > > -Vincent > > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
