community-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ross Gardler <>
Subject RE: Moving Apache Extras
Date Mon, 13 Jul 2015 19:21:15 GMT
Most (if not all) are managed by members of the PMCs. Though you make a very good point. The
assumption that all of them are PMC managed is quite possibly flawed.

We still need to tell PMCs what is going on, but we should also ask them to communicate it
to their dev communities.

Does anyone have any ideas how we can reach out to others?


-----Original Message-----
From: Rich Bowen [] 
Sent: Monday, July 13, 2015 12:16 PM
Subject: Re: Moving Apache Extras

On 07/10/2015 12:05 AM, Ross Gardler wrote:
> Assigning admin rights to PMCs is part of the transition isn't it? You didn't actually
answer my question, so maybe my assumption was incorrect. If this is ongoing work then we
need to be clear on what ComDev is signing up to here.
> For PMC mails I was just thinking of a blanket mail to all PMCs not one to specific owners.

Perhaps I'm confused. Apache Extras is projects that aren't ASF projects, right? So they're
not controlled by a PMC. Am I missing something?

> Sent from my Windows Phone
> ________________________________
> From: David Nalley<>
> Sent: ‎7/‎9/‎2015 8:51 PM
> To:<>
> Subject: Re: Moving Apache Extras
> On Thu, Jul 9, 2015 at 3:18 PM, Ross Gardler <> wrote:
>> 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.
> Currently, Comdev owns Apache Extras. My preference is that it stays 
> that way, and that infra manages the transition only. This is 
> essentially the same number of git repos that we currently manage for 
> all of the ASF, but access management is pretty significantly 
> automated and largely managed by project chairs rather than Infra.
>> 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".
> Just to make sure we are talking about the same thing many of the 
> projects have more than one PMC listed. The average over a quick 
> sample of 10, was 3 PMCs listed per project. Is that expected? It 
> seems to be doing that via labels, but not all labels per project are 
> PMCs. (for instance, there are labels of NoSQL, cql, cms, Server, 
> java, esb, etc.)
> Daniel: Is there a way to script the above away? I assume there is, 
> but haven't delved into the google code api yet, nor figured out how 
> to translate some of the non-existent PMC labels away.
> --David

Rich Bowen - - @rbowen - @apachecon

View raw message