It seems to me that moving to GitHub would be easier, since Google put a "Export to GitHub" button on each project page, and I've used it and it works well. Perhaps I missed it, but was there a reason why SourceForge was chosen over GitHub? (Just curious... since I have no personal stake in this endeavor.)
-- Christopher L Tubbs II http://gravatar.com/ctubbsii On Thu, Jul 9, 2015 at 2:42 PM, Daniel Gruno <humbed...@apache.org> wrote: > Hiya folks, > > I'm the "lucky person" in charge of moving the some 350 projects from Google > Code to SourceForge. > This will happen over the course of next week, save some freak accident > occurs, however, SourceForge is not Google Code, and as such, there are a > few things we need to consider: > > - I will create an admin account that will initially own all the imported > projects. This can/will be shared with the ComDev PMC. > - Someone (not me!!) will have to step up and help out with delegating > read/write access to the new repos on SourceForge. > - Preferably, someone will have to go through the giant list of projects, > and select those we'll import. This is not strictly necessary, but if > someone volunteers for this, that'd be super duper. > > The most important thing is that we are able to delegate write access to the > devs (and do so!), so this does not simply become a big data dump that just > sits there. If any of you are interested in taking on that task (preferably > more than one person), please do speak up :) > > With regards, > Daniel.
