Re: [VOTE] Allowing write access to GitHub repositories (aka GitBox)

2017-12-21 Thread Guozhang Wang
Thanks Ismael,

I have setup the account and can verify that it works on kafka / kafka-site
PRs now!


Guozhang

On Thu, Dec 21, 2017 at 5:12 PM, Ismael Juma  wrote:

> The previous Apache git repos don't exist anymore. The new ones are at:
>
> https://gitbox.apache.org/repos/asf/?p=kafka.git
> https://gitbox.apache.org/repos/asf/?p=kafka-site.git
>
> In any case, we should merge to the GitHub repo now and the following PR
> updates the merge script to default to that:
>
> https://github.com/apache/kafka/pull/4352
>
> Ismael
>
> On Fri, Dec 22, 2017 at 1:02 AM, Ismael Juma  wrote:
>
> > It's done! Committers, please set up your account:
> >
> > https://gitbox.apache.org/setup/
> >
> > On Wed, Dec 20, 2017 at 12:30 AM, Ismael Juma  wrote:
> >
> >> Forgot the link to the relevant Infra JIRA: https://issues.apache.or
> >> g/jira/browse/INFRA-15676
> >>
> >> On Tue, Dec 19, 2017 at 11:59 PM, Ismael Juma 
> wrote:
> >>
> >>> 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 
> 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 
>  wrote:
> 
> > +1
> >
> > On 12 December 2017 at 20:38, Sriram Subramanian 
> > 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 
> > 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
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> 
> 
> >>>
> >>
> >
>



-- 
-- Guozhang


Re: [VOTE] Allowing write access to GitHub repositories (aka GitBox)

2017-12-21 Thread Ismael Juma
The previous Apache git repos don't exist anymore. The new ones are at:

https://gitbox.apache.org/repos/asf/?p=kafka.git
https://gitbox.apache.org/repos/asf/?p=kafka-site.git

In any case, we should merge to the GitHub repo now and the following PR
updates the merge script to default to that:

https://github.com/apache/kafka/pull/4352

Ismael

On Fri, Dec 22, 2017 at 1:02 AM, Ismael Juma  wrote:

> It's done! Committers, please set up your account:
>
> https://gitbox.apache.org/setup/
>
> On Wed, Dec 20, 2017 at 12:30 AM, Ismael Juma  wrote:
>
>> Forgot the link to the relevant Infra JIRA: https://issues.apache.or
>> g/jira/browse/INFRA-15676
>>
>> On Tue, Dec 19, 2017 at 11:59 PM, Ismael Juma  wrote:
>>
>>> 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  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 
 wrote:

> +1
>
> On 12 December 2017 at 20:38, Sriram Subramanian 
> 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 
> 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
> > > > > >
> > > > >
> > > >
> > >
> >
>


>>>
>>
>


Re: [VOTE] Allowing write access to GitHub repositories (aka GitBox)

2017-12-21 Thread Ismael Juma
It's done! Committers, please set up your account:

https://gitbox.apache.org/setup/

On Wed, Dec 20, 2017 at 12:30 AM, Ismael Juma  wrote:

> Forgot the link to the relevant Infra JIRA: https://issues.apache.
> org/jira/browse/INFRA-15676
>
> On Tue, Dec 19, 2017 at 11:59 PM, Ismael Juma  wrote:
>
>> 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  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 
>>> wrote:
>>>
 +1

 On 12 December 2017 at 20:38, Sriram Subramanian 
 wrote:

 > +1
 >
 > On Tue, Dec 12, 2017 at 8:22 AM, Manikumar >>> >
 > 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 >>> >
 > > wrote:
 > > >
 > > > > +1
 > > > >
 > > > > On Tue, 12 Dec 2017 at 15:47 Ismael Juma 
 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
 > > > > >
 > > > >
 > > >
 > >
 >

>>>
>>>
>>
>


Re: [VOTE] Allowing write access to GitHub repositories (aka GitBox)

2017-12-19 Thread Ismael Juma
Forgot the link to the relevant Infra JIRA:
https://issues.apache.org/jira/browse/INFRA-15676

On Tue, Dec 19, 2017 at 11:59 PM, Ismael Juma  wrote:

> 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  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 
>> wrote:
>>
>>> +1
>>>
>>> On 12 December 2017 at 20:38, Sriram Subramanian 
>>> wrote:
>>>
>>> > +1
>>> >
>>> > On Tue, Dec 12, 2017 at 8:22 AM, Manikumar 
>>> > 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 
>>> > > wrote:
>>> > > >
>>> > > > > +1
>>> > > > >
>>> > > > > On Tue, 12 Dec 2017 at 15:47 Ismael Juma 
>>> 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
>>> > > > > >
>>> > > > >
>>> > > >
>>> > >
>>> >
>>>
>>
>>
>


Re: [VOTE] Allowing write access to GitHub repositories (aka GitBox)

2017-12-19 Thread Ismael Juma
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  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 
> wrote:
>
>> +1
>>
>> On 12 December 2017 at 20:38, Sriram Subramanian 
>> wrote:
>>
>> > +1
>> >
>> > On Tue, Dec 12, 2017 at 8:22 AM, Manikumar 
>> > 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 
>> > > wrote:
>> > > >
>> > > > > +1
>> > > > >
>> > > > > On Tue, 12 Dec 2017 at 15:47 Ismael Juma 
>> 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
>> > > > > >
>> > > > >
>> > > >
>> > >
>> >
>>
>
>


Re: [VOTE] Allowing write access to GitHub repositories (aka GitBox)

2017-12-15 Thread Ismael Juma
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  wrote:

> +1
>
> On 12 December 2017 at 20:38, Sriram Subramanian  wrote:
>
> > +1
> >
> > On Tue, Dec 12, 2017 at 8:22 AM, Manikumar 
> > 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 
> > > wrote:
> > > >
> > > > > +1
> > > > >
> > > > > On Tue, 12 Dec 2017 at 15:47 Ismael Juma 
> 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
> > > > > >
> > > > >
> > > >
> > >
> >
>


Re: [VOTE] Allowing write access to GitHub repositories (aka GitBox)

2017-12-14 Thread Tom Bentley
+1

On 12 December 2017 at 20:38, Sriram Subramanian  wrote:

> +1
>
> On Tue, Dec 12, 2017 at 8:22 AM, Manikumar 
> wrote:
>
> > +1
> >
> > On Tue, Dec 12, 2017 at 9:49 PM, Rajini Sivaram  >
> > wrote:
> >
> > > +1
> > >
> > > Thanks, Ismael!
> > >
> > > On Tue, Dec 12, 2017 at 4:18 PM, Damian Guy 
> > wrote:
> > >
> > > > +1
> > > >
> > > > On Tue, 12 Dec 2017 at 15:47 Ismael Juma  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
> > > > >
> > > >
> > >
> >
>


Re: [VOTE] Allowing write access to GitHub repositories (aka GitBox)

2017-12-12 Thread Sriram Subramanian
+1

On Tue, Dec 12, 2017 at 8:22 AM, Manikumar 
wrote:

> +1
>
> On Tue, Dec 12, 2017 at 9:49 PM, Rajini Sivaram 
> wrote:
>
> > +1
> >
> > Thanks, Ismael!
> >
> > On Tue, Dec 12, 2017 at 4:18 PM, Damian Guy 
> wrote:
> >
> > > +1
> > >
> > > On Tue, 12 Dec 2017 at 15:47 Ismael Juma  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
> > > >
> > >
> >
>


Re: [VOTE] Allowing write access to GitHub repositories (aka GitBox)

2017-12-12 Thread Guozhang Wang
+1

On Tue, Dec 12, 2017 at 9:24 AM, Gwen Shapira  wrote:

> +1
>
> On Tue, Dec 12, 2017 at 9:23 AM Jason Gustafson 
> wrote:
>
> > +1
> >
> > On Tue, Dec 12, 2017 at 8:22 AM, Manikumar 
> > 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 
> > > wrote:
> > > >
> > > > > +1
> > > > >
> > > > > On Tue, 12 Dec 2017 at 15:47 Ismael Juma 
> 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
> > > > > >
> > > > >
> > > >
> > >
> >
>



-- 
-- Guozhang


Re: [VOTE] Allowing write access to GitHub repositories (aka GitBox)

2017-12-12 Thread Gwen Shapira
+1

On Tue, Dec 12, 2017 at 9:23 AM Jason Gustafson  wrote:

> +1
>
> On Tue, Dec 12, 2017 at 8:22 AM, Manikumar 
> wrote:
>
> > +1
> >
> > On Tue, Dec 12, 2017 at 9:49 PM, Rajini Sivaram  >
> > wrote:
> >
> > > +1
> > >
> > > Thanks, Ismael!
> > >
> > > On Tue, Dec 12, 2017 at 4:18 PM, Damian Guy 
> > wrote:
> > >
> > > > +1
> > > >
> > > > On Tue, 12 Dec 2017 at 15:47 Ismael Juma  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
> > > > >
> > > >
> > >
> >
>


Re: [VOTE] Allowing write access to GitHub repositories (aka GitBox)

2017-12-12 Thread Jason Gustafson
+1

On Tue, Dec 12, 2017 at 8:22 AM, Manikumar 
wrote:

> +1
>
> On Tue, Dec 12, 2017 at 9:49 PM, Rajini Sivaram 
> wrote:
>
> > +1
> >
> > Thanks, Ismael!
> >
> > On Tue, Dec 12, 2017 at 4:18 PM, Damian Guy 
> wrote:
> >
> > > +1
> > >
> > > On Tue, 12 Dec 2017 at 15:47 Ismael Juma  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
> > > >
> > >
> >
>


Re: [VOTE] Allowing write access to GitHub repositories (aka GitBox)

2017-12-12 Thread Manikumar
+1

On Tue, Dec 12, 2017 at 9:49 PM, Rajini Sivaram 
wrote:

> +1
>
> Thanks, Ismael!
>
> On Tue, Dec 12, 2017 at 4:18 PM, Damian Guy  wrote:
>
> > +1
> >
> > On Tue, 12 Dec 2017 at 15:47 Ismael Juma  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
> > >
> >
>


Re: [VOTE] Allowing write access to GitHub repositories (aka GitBox)

2017-12-12 Thread Rajini Sivaram
+1

Thanks, Ismael!

On Tue, Dec 12, 2017 at 4:18 PM, Damian Guy  wrote:

> +1
>
> On Tue, 12 Dec 2017 at 15:47 Ismael Juma  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
> >
>


Re: [VOTE] Allowing write access to GitHub repositories (aka GitBox)

2017-12-12 Thread Damian Guy
+1

On Tue, 12 Dec 2017 at 15:47 Ismael Juma  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/7031168e7026222169c66fed29f5200fc4b561df28c242ccf706f326@%3Cdev.kafka.apache.org%3E
>
> The vote will run for 72 hours.
>
> Ismael
>


[VOTE] Allowing write access to GitHub repositories (aka GitBox)

2017-12-12 Thread Ismael Juma
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/7031168e7026222169c66fed29f5200fc4b561df28c242ccf706f326@%3Cdev.kafka.apache.org%3E

The vote will run for 72 hours.

Ismael