killing gborg - devision of labor - Mailing list pgsql-www

From Robert Treat
Subject killing gborg - devision of labor
Date
Msg-id 200706101308.22481.xzilla@users.sourceforge.net
Whole thread Raw
Responses Re: killing gborg - devision of labor  (Stefan Kaltenbrunner <stefan@kaltenbrunner.cc>)
Re: killing gborg - devision of labor  ("Marc G. Fournier" <scrappy@hub.org>)
Re: killing gborg - devision of labor  ("Joshua D. Drake" <jd@commandprompt.com>)
Re: killing gborg - devision of labor  (Chris Ryan <xgbe@yahoo.com>)
List pgsql-www
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.

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? :-)  

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. 

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 
into writing one up... though if someone knows that to be a dead-end we can 
probably brute force it by recreating at least the open items for each 
project (assuming the projects are willing to help on this)

5. documentation / downloads - For projects that have a release history, I am 
guessing there is no way to magically move these over; they are something 
that will have to be done manually? If that's not the case please lmk, 
otherwise I'll let project owners know thatsthe case. 

Please let me know if there are other items I am overlooking. Since I have a 
couple of projects ready to move, I'd like to start pushing these through 
sooner rather than later, since it will take some effort to coordinate 
things.  TIA. 

-- 
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL


pgsql-www by date:

Previous
From: "Ivan Zolotukhin"
Date:
Subject: Re: broken link on postgresql.org main page
Next
From: Stefan Kaltenbrunner
Date:
Subject: Re: killing gborg - devision of labor