FYI. Now it looks like we will have to do the move of Pivot-Extras to SF 
ourselves. Waiting for instructions. 

~Roger Whitcomb

Sent from my iPhone

Begin forwarded message:

> From: jan i <j...@apache.org>
> Date: July 13, 2015 at 1:23:35 PM PDT
> To: "d...@community.apache.org" <d...@community.apache.org>
> Subject: Re: Moving Apache Extras
> Reply-To: d...@community.apache.org
> 
>> On Monday, July 13, 2015, Rich Bowen <rbo...@rcbowen.com> wrote:
>> 
>> 
>> 
>>> On 07/13/2015 04:00 PM, Ross Gardler wrote:
>>> 
>>> Apache-extras is a service managed by ComDev. Though we never provided
>>> any commitment to support it.
>>> 
>>> However, many extras (most?) are used by  ASF PMCs and they need a
>>> solution to the fact that Google Code is closing down. We are doing this
>>> with infra resources for that reason (as a director you've seen the
>>> repeated requests from some PMCs to find a resolution, you've also seen the
>>> responses to those requests).
>>> 
>>> It's easier for Infra to move all projects rather than some projects.
>>> Hence the current approach. Though you are correct, as noted on a different
>>> thread, that the assumption all projects on extras belong to PMCs is likely
>>> flawed. Unfortunately there is no easy way of identifying which are PMC
>>> owned and which are not.
>>> 
>>> So here's an alternative approach. We (ComDev) send out a mail to PMCs
>>> indicating that they need to great a ComDev issue if they want their
>>> project moving. If they don't sign up they don't get moved.
>>> 
>>> We (ComDev) provide infra with a reduced list of projects to move and
>>> they run the scripts for those projects.
>> 
>> I think I must have been watching all of these conversations (I know it's
>> been going for more than a year) with a certain understanding that we were
>> going to push everything onto volunteer labor rather than Infra. So, mea
>> culpa for not paying close enough attention. Yes, I know that this has been
>> discussed for *ages*.
>> 
>> I figured that what we, the ASF, were doing for these projects was
>> negotiating with SF for the service/resources/whatever, not doing the
>> actual migration. I figured either the projects themselves would do that
>> work, or Roberto and his team at SF would do it.
> 
> that was my understanding as well. AOO moved a while ago.
> 
> We should notify the PMCs how to move, and leave the rest to volunteer time.
> 
> rgds
> jan i
> 
>> 
>> --Rich
>> 
>> 
>> 
>>> 
>>> 
>>> Sent from my Windows Phone
>>> ________________________________
>>> From: Rich Bowen<mailto:rbo...@rcbowen.com>
>>> Sent: ‎7/‎13/‎2015 12:47 PM
>>> To: d...@community.apache.org<mailto:d...@community.apache.org>
>>> Subject: Re: Moving Apache Extras
>>> 
>>> 
>>> 
>>>> On 07/09/2015 02:42 PM, Daniel Gruno 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:
>>> 
>>> Wait what?
>>> 
>>> Are you doing this because you're a nice person, or because it's an
>>> Infra Assignment?
>>> 
>>> I ask because it seems a really iffy precedent giving paid infra support
>>> to non-ASF projects. Tell me you're doing this for scotch rather than
>>> for money, and I'll back off. I know you do wear many different hats.
>>> 
>>> --Rich
>>> 
>>> 
>>>> - 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.
>>> 
>>> 
>>> --
>>> Rich Bowen - rbo...@rcbowen.com - @rbowen
>>> http://apachecon.com/ - @apachecon
>> 
>> --
>> Rich Bowen - rbo...@rcbowen.com - @rbowen
>> http://apachecon.com/ - @apachecon
> 
> 
> -- 
> Sent from My iPad, sorry for any misspellings.

Reply via email to