Thanks Daniel,

Sharing admin account with ComDev PMC makes sense.

By "delegating read/write access to the new repos" do you mean the ComDev owned 
admin account will assign individual project admin rights to the relevant PMC 
upon request. If that's the case then the ComDev PMC as a whole can own this 
responsibility. We can manage it through JIRA, that way when Infra gets 
requests they can simply reassign to ComDev. It would be wonderful if the infra 
contractors could help with this workload, but I see no reason why ComDev 
volunteers (including me) can't help.

I've been meaning to go through the list but if my assumption above is correct 
I see an alternative and less labour intensive option. Accounts that are still 
owned by ComDev after x months (I suggest a minimum of 12 months) will be 
examined and if appropriate closed.

It would be great if you, as part of your migration process, will handle the 
notifications to PMCs to ensure they are aware of this. I'd suggest one email 
saying "we will do this, you will need to open a ComDev ticket to ensure you 
get admin access promptly". Followed by a, "we are doing it now" and a final 
"it's done, all further enquiries to ComDev".

Ross

-----Original Message-----
From: Daniel Gruno [mailto:humbed...@apache.org] 
Sent: Thursday, July 9, 2015 11:43 AM
To: dev@community.apache.org
Subject: Moving Apache Extras

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.

Reply via email to