cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Will Stevens <wstev...@cloudops.com>
Subject Re: External fork of Cloudstack
Date Fri, 18 Mar 2016 22:30:34 GMT
Hey All,
I am going to try to keep moving this forward, and as such, I have created
the 'apache-cloudstack' organization in github.  I have invited everyone
who is in the current 'cloudstack' organization as owners as well as Sam
and Chris (also as owners).

I think using this github org is probably the right one to use moving
forward with this proposal since it better reflects what the org
represents.

Sam and Chris, I would like to get your suggestions for how we should plan
to move forward since I think there is probably going to be more logistics
and details to work through on your (ASF board) side of things.

To reiterate, I think the best and most seamless approach will be to
actually transfer ownership of the 'apache/cloudstack' repo to the
'apache-cloudstack' org to be represented as
'apache-cloudstack/cloudstack'.  This will move all of the PRs and will
also setup redirection of requests from 'apache/cloudstack' to
'apache-cloudstack/cloudstack' which is really important for all existing
links etc...

I also think we should also consider deleting the 'cloudstack/cloudstack'
repository unless anyone is actively using it for testing in order to
reduce confusion on the topic.

I will create a VOTE thread so the community, and the participating ASF
board members, can officially sign off on the proposal and give feedback.

Cheers,

*Will STEVENS*
Lead Developer

*CloudOps* *| *Cloud Solutions Experts
420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6
w cloudops.com *|* tw @CloudOps_

On Fri, Mar 18, 2016 at 2:48 PM, Sam Ruby <rubys@intertwingly.net> wrote:

> On Fri, Mar 18, 2016 at 2:39 PM, sebgoa <runseb@gmail.com> wrote:
> >
> >> On Mar 18, 2016, at 6:30 PM, Sam Ruby <rubys@intertwingly.net> wrote:
> >>
> >> I'm more concerned that the page is indistinguishable from a fork, and
> >> gives no indication of official status.  That may be OK for a work in
> >> progress, but isn't ideal as a final solution.  I'll share that I've
> >> heard (second and third hand) reports of people who only have heard of
> >> there being an "external fork", and have drawn incorrect conclusions
> >> from that.  I think we need to be careful about how this is explained,
> >> as perceptions matter.
> >
> > I have updated the organization description and added our website and
> dev@ address.
> >
> >> By contrast, if you go to:
> >>
> >> https://github.com/apache/whimsy
> >>
> >> What you will see in place of "Mirror of xxx" is "Apache Whimsy".  I
> >> grant you that it is a small thing,
> >
> > We can easily change “Mirror of Apache CloudStack” to “Apache
> CloudStack”.
> >
> > But I think lots of people will get upset as it will really mean that
> this is a move away from ASF infra.
> > Or maybe I missing your point.
>
> Suggestion for now: “Mirror of Apache CloudStack for testing purposes
> only”.
>
> While what is there now is technically correct, it is incomplete.  In
> particular it can, and has, caused confusion.  Based on Will's
> comments earlier in this thread, I believe that my suggestion is an
> accurate portrayal of the current status, otherwise please substitute
> a more accurate description.  (the subtext here: I am not an ASF
> Director stepping in and demanding change, so please don't take
> anything I say as an edict, I'm simply participating in the
> conversation).
>
> Longer term, this may very well be "Apache CloudStack" in the same
> sense that the github whimsy repository is "Apache Whimsy".  Or the
> code could end up in a different place, like the apache-cloudstack
> organization I suggested previously.
>
> - Sam Ruby
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message