Hi Sebastien,

Thanks for your reply and yes, I am a member of the ASF board.

The thing is, there was already some discussion of this at the
ASF board meeting that happened yesterday. I can tell you that
there were more than a few board members that were a bit concerned
at the prospect of Apache Cloudstack forking and starting a new
GitHub organization, so I’m here now to discuss.

I’m sorry that you are unhappy with the lack of access to GitHub
facilities, however I’m confused, the ASF does provide mirroring,
active GitHub issue, comment, etc, sync, the ability to close PRs,
etc. Is there something specific not in that list that the CloudStack
PMC desires and if so can you state that? I remember seeing a request
that you wanted the ability to close pull requests and to be part of
the experiment going on with the Whimsy PMC - is that what you are
talking about?

The other thing is - is the new Cloudstack GitHub organization the
result of a subset of the PMC going off and doing this - or was this
actually discussed by the PMC somewhere - apologies if I missed the
thread. I am now subscribed to dev@cloudstack.a.o and I can also go
back and search the archives.

The ASF builds communities. There is an Apache Cloudstack
community that has been approved by the board and that has been growing
here at the ASF. Also the ASF cares about names and trademarks and
branding, etc. If some set of the PMC don’t want to work on Apache
Cloudstack and then go off and start a fork etc., then the ASF Cloudstack
PMC and project still exist and go on, so that is something to think
about and also something for the board and trademarks@, etc., to think
about since the name will be in conflict and that can’t happen, etc.

Finally, as for the Apache Cloudstack PMC - for the PMC the policy of
the ASF is that the canonical repository at the moment is on ASF hardware.
There are not any approved policies for external forks being the canonical
repo, especially those in another GitHub organization not managed by the
ASF. There is an experiment in the Apache Whimsy PMC to experiment with
GitHub as the canonical repo for an apache/* org project. That is still an
experiment and not widely offered by ASF infra to all PMCs.

Given the above I’d like discussion from the Cloudstack PMC and more than
just one or two of you. Let’s figure this out.

Thanks,
Chris




-----Original Message-----
From: Sebastien Goasguen <run...@gmail.com>
Reply-To: "dev@cloudstack.apache.org" <dev@cloudstack.apache.org>
Date: Thursday, March 17, 2016 at 3:15 AM
To: "dev@cloudstack.apache.org" <dev@cloudstack.apache.org>
Subject: Re: External fork of Cloudstack (was Re: [GitHub] cloudstack pull
request: Is the project attempting a fork on Githu...)

>Hi Chris, 
>
>We have never met but i recognize your name from members only ASF threads.
>
>For the benefit of others on this list it is useful to mention that you
>are a member of the ASF board.
>
>The PMC has filed its quarterly report  for march, as well as an interim
>report about a month ago. The interim report was acknowledged by Sam Ruby
>couple days ago only.
>
>I am assuming that the board will discuss it at its monthly meeting and
>that we will hear from the board then.
>
>Other than that the discussions are active on dev@ , but roughly we feel
>that we are being hurt by lack of access to github facilities.
>
>Best,
>
>-Sebastien
>
>> On 17 Mar 2016, at 00:04, Chris Mattmann <mattm...@apache.org> wrote:
>> 
>> Hi,
>> 
>> Sorry about my crude way of filing a PR for this, but I heard
>> information about the Apache Cloudstack PMC actively
>> discussing managing the project with GitHub as the primary source
>> in a different organization than the github.com/apache/ org.
>> 
>> Can someone clarify this for me? Clearly wearing my board hat,
>> this is not something we allow for any of our ASF projects.
>> 
>> Cheers,
>> Chris “board hat on” Mattmann
>> 
>> 
>> 


Reply via email to