GitBox migration will happen today. Committers, please make sure to associate your github ID with your apache.org account via id.apache.org, and make sure to enable 2 factor authentication in GitHub.
Ismael On Fri, Dec 15, 2017 at 3:40 PM, Ismael Juma <ism...@juma.me.uk> wrote: > Thanks to everyone who voted and contributed to the discussion. > > The vote passes with 7 binding votes (Damian, Rajini, Jason, Gwen, > Guozhang, Sriram, Ismael) and 2 non-binding votes (Manikumar and Tom). > > I will file a JIRA ticket in the Apache Infra project requesting the > migration to GitBox. > > Ismael > > On Thu, Dec 14, 2017 at 11:48 AM, Tom Bentley <t.j.bent...@gmail.com> > wrote: > >> +1 >> >> On 12 December 2017 at 20:38, Sriram Subramanian <r...@confluent.io> >> wrote: >> >> > +1 >> > >> > On Tue, Dec 12, 2017 at 8:22 AM, Manikumar <manikumar.re...@gmail.com> >> > wrote: >> > >> > > +1 >> > > >> > > On Tue, Dec 12, 2017 at 9:49 PM, Rajini Sivaram < >> rajinisiva...@gmail.com >> > > >> > > wrote: >> > > >> > > > +1 >> > > > >> > > > Thanks, Ismael! >> > > > >> > > > On Tue, Dec 12, 2017 at 4:18 PM, Damian Guy <damian....@gmail.com> >> > > wrote: >> > > > >> > > > > +1 >> > > > > >> > > > > On Tue, 12 Dec 2017 at 15:47 Ismael Juma <ism...@juma.me.uk> >> wrote: >> > > > > >> > > > > > Hi all, >> > > > > > >> > > > > > The Apache Infra team has started a new project earlier this >> year >> > > > called >> > > > > > GitBox that supports two-way synchronization between GitHub and >> > > > > > git-wip-us.apache.org and, most importantly, provides GitHub >> write >> > > > > access >> > > > > > to committers. GitBox is not generally available yet, but >> > individual >> > > > > > projects can ask to be migrated. >> > > > > > >> > > > > > I would like to start a vote on migrating kafka and kafka-site >> to >> > > > GitBox >> > > > > > and: >> > > > > > >> > > > > > 1. Providing GitHub write access to committers (this requires >> dual >> > > > factor >> > > > > > authentication) >> > > > > > 2. Allowing merges via the GitHub UI as well as the existing >> merge >> > > > script >> > > > > > 3. Enabling protected branches for trunk and release branches so >> > that >> > > > > > merges via the GitHub UI can only be done if the tests pass and >> the >> > > PR >> > > > > has >> > > > > > been approved by a committer >> > > > > > 4. Only allowing the "squash and merge" strategy for GitHub UI >> > merges >> > > > > > 5. Updating the merge script so that the GitHub git repo is the >> > > target >> > > > of >> > > > > > the merge >> > > > > > 6. Disallowing force pushes to trunk and release branches >> > > > > > >> > > > > > The discussion thread talks about some of the pros and cons >> (mostly >> > > > pros) >> > > > > > of this change: >> > > > > > >> > > > > > >> > > > > > https://lists.apache.org/thread.html/ >> > 7031168e7026222169c66fed29f520 >> > > > > 0fc4b561df28c242ccf706f326@%3Cdev.kafka.apache.org%3E >> > > > > > >> > > > > > The vote will run for 72 hours. >> > > > > > >> > > > > > Ismael >> > > > > > >> > > > > >> > > > >> > > >> > >> > >
