On 05/20/2014 03:35 PM, Fabian Arrotin wrote: > On 20/05/14 16:33, Karanbir Singh wrote: >> On 05/20/2014 03:30 PM, Fabian Arrotin wrote: >>> On 20/05/14 16:11, Karanbir Singh wrote: >>>> On 05/20/2014 12:11 PM, Fabian Arrotin wrote: >>>>> Or do you want to create another git repo and we'd adopt the same >>>>> "merge" from one to the other (same as we do with gitorious -> internal >>>>> git repo) ? >>>> >>>> >>>> git.centos.org to be the public visible, but not commitable / forkable >>>> repo - for that we use the github.com/CentOS org, to match all the other >>>> repos that were working with at the moment. >>>> >>>> >>> >>> ok, so basically you meant gitorious -> github ... >> >> and making the production code public, it isnt really in .centos.org >> public at the moment. >> > > Yeah, so to recap : > * migrating gitorious -> github > * migrating "internal-and-not-public" git repo -> git.centos.org > > That works for me, but we'd need to then inform people about that change > and migrate current ACLs for people with rights to accepts "merge > requests" on gitorious to be able to do the same for "merge pull > requests" on github. > > When do we want to do that ? > lets do it now :) technically, anyone on the QA team should be able to push to git.c.o - so we can have a qateam setup as a 'team' there, and we can just add members. - KB -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc