Mailing-List: contact dev-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
MIME-Version: 1.0
In-Reply-To: 
 <CAGQtxvbGpws6vPn6ioD3GVxJX6sq6-rCOL=+p3n2e=42BtR5Kw@mail.gmail.com>
References: <56EC1E64.5010700@intertwingly.net>
	<CAC2panpGJicJwdMYT-aZaLQ9b1Wdq_GEEHyLpGmN77-Y9J9jGQ@mail.gmail.com>
	<CAFG6u8FCQSncifVuUC2WOduRwFDMuRg5Ca59OPhy=b5ya=k_zQ@mail.gmail.com>
	<A4AC3B0C-0619-4B05-A44A-13D3DE85EDB0@gmail.com>
	<CAFG6u8EtR=A-z-L4u5=SYU=_CqvBe=xS2VbYzOEx6dRmrjs7Xg@mail.gmail.com>
	<CAC2panrVwDjbTSVoRF_ff=U1e5bo3_Yog5i82g9Lr2qT78cjTg@mail.gmail.com>
	<D311D509.81170%chris.a.mattmann@jpl.nasa.gov>
	<CAC2pano7=iXZn8LMBQsTnF25Bax6-YyR8Vepksiz4OKi7RKCMg@mail.gmail.com>
	<CAGQtxvbGpws6vPn6ioD3GVxJX6sq6-rCOL=+p3n2e=42BtR5Kw@mail.gmail.com>
Date: Sat, 19 Mar 2016 09:54:08 -0400
Message-ID: 
 <CAC2panqFRuU5CAkYGxGS4oC5Yyw7OrYjLWEgX-Td-ANzMY+Bjg@mail.gmail.com>
Subject: Re: External fork of Cloudstack
From: Will Stevens <williamstevens@gmail.com>
To: dev@cloudstack.apache.org
Content-Type: multipart/alternative; boundary=001a11c2d760a26762052e673238

--001a11c2d760a26762052e673238
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

I see you found the vote thread. Thanks for voting. :)

For now I think it is best that we try to avoid using the cloudstack org
for anything in order to mitigate confusion and try to get everyone on the
same page. We are charting new territory here, so removing as many
unnecessary distractions and causes for cloudy perception of what we are
trying to achieve is paramount IMO.

I personally think we should remove the cloudstack/cloudstack repo at this
point as I think it is more of a liability in this process than anything.
On Mar 19, 2016 9:45 AM, "Daan Hoogland" <daan.hoogland@gmail.com> wrote:

> Hm, Will let's use a vote thread for voting. My brain is old and rigid an=
d
> needs the clarity of it. Just to be clear, are we keeping the cloudstack
> organisation for experimenting and we do the move to apache-cloudstack? I
> am not sure if github has a policy on naming of organisations so It would
> be wise to keep cloudstack around in our control.
>
> On Fri, Mar 18, 2016 at 11:58 PM, Will Stevens <williamstevens@gmail.com>
> wrote:
>
> > I already created a vote thread in the dev@ mailing list. I wanted to
> try
> > to get consensus in the community as well. Please feel free to comment
> and
> > such in that thread. Having ASF board members participating in that
> thread
> > will be valuable.
> >
> > Thanks. :)
> > On Mar 18, 2016 6:54 PM, "Chris Mattmann" <mattmann@apache.org> wrote:
> >
> > > Will all of your actions below sound like a sound plan to me.
> > > Consider this the discuss thread. Get feedback for 24-48 hours,
> > > then VOTE, then proceed :-)
> > >
> > > Cheers,
> > > Chris
> > >
> > >
> > >
> > > -----Original Message-----
> > > From: <williamstevens@gmail.com> on behalf of Will Stevens
> > > <wstevens@cloudops.com>
> > > Reply-To: "dev@cloudstack.apache.org" <dev@cloudstack.apache.org>
> > > Date: Friday, March 18, 2016 at 3:30 PM
> > > To: "dev@cloudstack.apache.org" <dev@cloudstack.apache.org>
> > > Subject: Re: External fork of Cloudstack
> > >
> > > >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 movin=
g
> > > >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 shoul=
d
> > 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 t=
o
> > > >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 websit=
e
> > 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 =E2=80=9CMirror of Apache CloudStack=E2=80=
=9D to =E2=80=9CApache
> > > >> CloudStack=E2=80=9D.
> > > >> >
> > > >> > 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: =E2=80=9CMirror of Apache CloudStack for testi=
ng
> purposes
> > > >> only=E2=80=9D.
> > > >>
> > > >> 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 a=
n
> > > >> 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 th=
e
> > > >> code could end up in a different place, like the apache-cloudstack
> > > >> organization I suggested previously.
> > > >>
> > > >> - Sam Ruby
> > > >>
> > >
> > >
> > >
> >
>
>
>
> --
> Daan
>

--001a11c2d760a26762052e673238--