+1 On Sat, Mar 19, 2016 at 9:37 AM, Daan Hoogland <daan.hoogl...@gmail.com> wrote:
> +1 (binding as I saw others mention that. I doubt this is of any concern in > such a technical decision) > > On Sat, Mar 19, 2016 at 12:40 PM, Will Stevens <williamstev...@gmail.com> > wrote: > > > Thank you for this information, this is very helpful. > > On Mar 19, 2016 5:29 AM, "Rene Moser" <m...@renemoser.net> wrote: > > > > > On 03/18/2016 11:44 PM, Will Stevens wrote: > > > > > > > *Proposal:* > > > > Transfer ownership of the 'apache/cloudstack' mirrored repository out > > of > > > > the 'apache' github organization into the 'apache-cloudstack' github > > > > organization (which I have already setup and started inviting users > > to). > > > > Both members of the ACS community and the ASF board will have 'owner' > > > > permissions on this new organization. This will allow for > permissions > > to > > > > be applied specifically to the 'apache-cloudstack' organization and > not > > > > have to be applied to the entire 'apache' organization. > > > > > > > > By transferring ownership, all of the PRs will be copied to the new > > > > repository and redirects will be created on github from > > > 'apache/cloudstack' > > > > to 'apache-cloudstack/cloudstack'. > > > > > > We might also have to involve github support here. > > > > > > The apache top level projects github projects have a special setting > > > made by github internals that these projects are mirrored from > > > git://git.apache.org/cloudstack.git. > > > > > > I am not sure how this will behave after the technical organization > move. > > > > > > Maybe they can disable this and before the organization move, they can > > > create a new mirrored repo in apache/cloudstack. That would also be > > > great for consistency. > > > > > > > > > > > > > > > > > > -- > Daan >
