On Fri, Mar 18, 2016 at 4:37 AM, Will Stevens <wstev...@cloudops.com> wrote:
I may be thinking too far outside the box, but hear me out as this is
likely the best way to satisfy everyone's requirements.
Recap: The community needs additional github permissions in order to
integrate CI in order to maintain code quality. The ASF does not have
enough granular control via github to give permissions on the
apache/cloudstack repository without giving the permissions across the
entire github apache org, which they are presently not comfortable with.
What if we did the following:
- Setup the 'cloudstack' github org so both the ASF and the community have
'owner' role representation.
- The apache/cloudstack repo is transferred to the cloudstack/cloudstack
repo. This will move all of the PRs and everything over to the
cloudstack/cloudstack repo and will also setup redirection from
apache/cloudstack to cloudstack/cloudstack.
- This allows for the ASF and the community to work together to establish
the github permissions which make the most sense for the cloudstack project
without being bound by its implications on other projects.
- The official ASF repo would still be the source of truth and the
cloudstack/cloudstack repo would be a mirror of it. There are probably
some details in this that we will need to address to make sure everything
is consistent with the ASF requirements.
- There will only be one cloudstack repository on which to contribute as a
community member, so there will be no confusion introduced and there will
be no segmentation of the community.
- The cloudstack/cloudstack repo would still be an official ASF project, so
no need for rebranding or worrying about the unpleasant logistics of a
"fork".
I am sure I have not thought through all the details and I am sure there
are some gotchas that we have to sort out, but I think this is a real
viable stepping stone towards being able to satisfy both parties
requirements while keeping the community strong and headed in the same
direction.
What do you all think?
+1
I'm pleased to see this being discussed on the dev list; and I'm ashamed
that the board hasn't been more responsive. Suffice it to say that this
issue now has the board's attention.
On one hand, I'm a bit concerned that things are moving too quickly; and
on the other hand I feel that it is time to rip the bandage off. So I
would like to simultaneously encourage you (collectively) to think
further outside of the box, and yet not be too impatient despite the
previous lack of response. I'm the one that pushed through the approval
of the Whimsy experiment, and I'm willing to help here.
What would you be able to do if the git-dual experiment were expanded to
CloudStack that you couldn't do with the proposal above? I suggest that
you take full advantage of the fact that people are now listening.
Be aware that perception matters. If you go to
https://github.com/cloudstack/cloudstack, you will see in small print
"forked from apache/cloudstack" and then in slightly larger font "Mirror
of Apache Cloudstack". There should be an edit link on the latter for
the owners of the organization, I'd like to discuss what should be there.
I personally believe that the ASF has a demonstrable interest in being
able to establish provenance, but I don't believe that taking over
control of the ability of projects to set up Travis and other
integrations is a necessary consequence of that. But overall I agree
that if granularity of control for a single GitHub organization is an
issue, then having multiple GitHub organizations needs to be explored as
an option.
How can I help? I'd like to bring this proposal back to the board for
wider review so that nothing important is missed. If there are issues
that come up, I will help flatten them.
- Sam Ruby
