So this topic has been very slow moving, so I will keep pushing this along.


@Chris, are you on the ASF Infra team?  From your perspective are we
missing anything to move forward?

@Sam & David, is there anything else I need to do from the ASF side other
than working out the logistics with the Infra team?

Thanks everyone...

On Thu, Mar 31, 2016 at 2:04 PM, Will Stevens <williamstev...@gmail.com>
wrote:

> No problem.  I will try to keep you CC'ed with this email so you can
> contribute.  :)
>
> On Thu, Mar 31, 2016 at 1:55 PM, Chris Mattmann <mattm...@apache.org>
> wrote:
>
>> thanks if possible if you could CC my apache email I’d appreciate it
>> on those threads so I can contribute.
>>
>>
>>
>> -----Original Message-----
>> From: Will Stevens <williamstev...@gmail.com>
>> Date: Thursday, March 31, 2016 at 10:47 AM
>> To: jpluser <mattm...@apache.org>
>> Cc: Sam Ruby <ru...@intertwingly.net>, David Nalley <da...@gnsa.us>,
>> "dev@cloudstack.apache.org" <dev@cloudstack.apache.org>
>> Subject: Re: [LOGISTICS] Move 'apache/cloudstack' to 'apache-cloudstack'
>> org
>>
>> >Conversation moved to dev@ so everyone has better visibility.  Thanks
>> for
>> >the feedback Chris...  :)
>> >
>> >
>> >On Thu, Mar 31, 2016 at 1:45 PM, Chris Mattmann
>> ><mattm...@apache.org> wrote:
>> >
>> >None here on my part, and thanks for direct CC. The cloudstack dev
>> >email was such that I had to unsubscribe, but I have been monitoring
>> >the conversation.
>> >
>> >I am OK with the below plan from my end.
>> >
>> >Thanks Will. BTW, I don’t see anything private in particular, so
>> >moving this to dev@ ASAP would be welcomed.
>> >
>> >Cheers,
>> >Chris
>> >
>> >
>> >
>> >-----Original Message-----
>> >From: Will Stevens <williamstev...@gmail.com>
>> >Date: Thursday, March 31, 2016 at 10:26 AM
>> >To: Sam Ruby <ru...@intertwingly.net>, David Nalley <da...@gnsa.us>,
>> >jpluser <mattm...@apache.org>, "priv...@cloudstack.apache.org"
>> ><priv...@cloudstack.apache.org>
>> >Subject: [LOGISTICS] Move 'apache/cloudstack' to 'apache-cloudstack' org
>> >
>> >>This could potentially happen on dev@, but since this thread is
>> >>specifically for the logistics of the move, I figure it makes the most
>> >>sense to do on the private@ thread to start with.  If we want to move
>> >>this conversation to dev@, I am ok with
>> >> that happening at any point.
>> >>
>> >>
>> >>We have had a vote on this move and we had unanimous support for the
>> move
>> >>inside the ACS community.  Now for the more delicate process of actually
>> >>making it happen.
>> >>
>> >>
>> >>Sam and David, I am going to defer to you guys quite a bit in this
>> >>conversation as you have the best understanding of how things work at
>> the
>> >>ASF, so you are in the best position to advise on the buttons to press
>> >>and the ones not to.
>> >>
>> >>
>> >>Please CC anyone into this conversation who you feel should be involved.
>> >>As more people get involved I will do my best to keep everyone up to
>> >>speed with the goal, our progress, and address people's concerns.
>> >>
>> >>
>> >>I believe we need to primarily work with the ASF Infra team, but there
>> >>may be other people that we need to bring in.  Please advise on this.
>> >>
>> >>
>> >>Our current progress:
>> >>- All parties are in agreement with the decision to make the move.
>> >>- I have talked to Github support about getting the 'mirror' setup after
>> >>the move.  They said that a user who has admin access to both
>> >>organizations can email after the transfer and they will setup the
>> mirror
>> >>for us.
>> >>- I have setup the 'apache-cloudstack' github organization.
>> >>- I have add Sam, Chris and David (as well as some PMC members) as
>> owners
>> >>of the 'apache-cloudstack' org.
>> >>
>> >>
>> >>Please advise if I should add others as owners of the
>> 'apache-cloudstack'
>> >>github organization.
>> >>
>> >>
>> >>I think that is it for this initial email.  Lets get the ball rolling
>> and
>> >>make this a reality.  :)
>> >>
>> >>
>> >>Please voice any questions or concerns so we can resolve them openly.
>> >>
>> >>
>> >>Cheers,
>> >>
>> >>
>> >>Will
>> >>
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>>
>>
>>
>

Reply via email to