Robert Treat wrote:
> Ok folks,
>
> I've gotten in contact with some of the project admins and have some projects
> that are ready to move and want to come up with a game plan for moving people
> across. I'm not overly familiar with some of the parts of the system, so I
> am hoping that someone else can jump in for certain parts. Here's a recap of
> what I think needs to happen for moving a project:
>
> 1. create a new project on pgfoundry and assign that project to the proper
> owner. I can submit these requests and include the proper info, though
> someone will have to approve it.
Note that pgfoundry is about to move.
Yes someone will have to approve it.
> 2. Move CVS - I think this is a simple move from one machine to the other
> right? ISTM this has been done before for other projects, is this something
> I can just ask to have done and someone (Marc? Dave?) can make it happen? :-)
Yes it is as simple as moving the repo "once" the pgfoundry project is
setup.
>
> 3. Mailing lists - AIUI this is a bit tricker. Right now we don't have any
> way to quietly migrate mailing lists right? For a project to move it's list,
> we create a new one on the pgfoundry site, and then load in a list of current
> subscribers from gborg... does that sound right, or is there some other
> method? Again this is an area I'm not familiar with someone whom I can
> coordinate this through would be great.
Actually this isn't that tough:
1. Create duplicative prefix name for list (foo-general@gborg ==
foo-general@pgfoundry)
2. Subscribe all users from gborg to pgfoundry (also easy as command
utilities exist, both are running mailman)
3. Redirect aliases on gborg to aliases on pgfoundry so that old users
can use old list address for short time
4. Move mboxes to regenerate archives.
>
> 4. Moving bugs and tracker items - I know folks have talked about using
> scripts to do this in the past, do such scripts exists? If not I can look
Supposedly to some degree they do, I would note that this is where the
migration usually stops because no one has used the scripts and
obviously nobody is willing to do the work by hand.
Joshua D. Drake
