Re: [VOTE] Convert to gitbox
I have the same problem; I cannot see the ticket so I have no clue what the current status is. Niels On Thu, Dec 7, 2017 at 3:29 AM, Suraj Acharya wrote: > Ryan had filed an Infra ticket to turn it on. > I am not sure what the status of that ticket is. > I don't have view privileges on that ticket. > > Suraj > > On Wed, Dec 6, 2017 at 3:09 AM, Niels Basjes wrote: > > > Hi, > > > > I see this transition was started but at this point it does not seem to > > work yet. > > What is the current status? > > > > Niels > > > > On Tue, Aug 29, 2017 at 9:14 PM, Suraj Acharya wrote: > > > > > +1 > > > > > > On Tue, Aug 29, 2017 at 11:49 AM, Sean Busbey > wrote: > > > > > > > +1 > > > > > > > > On 2017-08-29 11:29, "Sean Busbey" wrote: > > > > > Way back in May we had consensus[1] on using gitbox so that we > could > > > > start making use of pull requests. > > > > > > > > > > In the subsequent JIRAs to implement, it became clear that the > entry > > > bar > > > > to start is convert our repo to use gitbox. this means the writeable > > > > repository will be on github and some committer set up will be > > > needed[2]. I > > > > don't think this got adequately conveyed originally, so I wanted to > > call > > > it > > > > out here. > > > > > > > > > > Additionally, the infra process for converting to gitbox requires a > > > link > > > > to a community consensus thread. While I think we already had that > back > > > in > > > > [1], May was a long time ago and some folks might not be watching for > > > > [DISCUSS] threads. > > > > > > > > > > Please vote: > > > > > > > > > > +1: we should convert to gitbox and enable pull request merging > > > > > -1: we should not convert to gitbox because... > > > > > > > > > > Vote will be open for at least 72 hours and will be subject to > > Majority > > > > Approval (3 or more +1s and more +1s than -1s). > > > > > > > > > > [1]: https://s.apache.org/ieB0 > > > > > [2]: Committers will need to flag a github account as theirs via > the > > > > account linking utility: > > > > > https://gitbox.apache.org/setup/ > > > > > > > > > > The git-wip repository will also cease, so folks who currently use > it > > > > will need to update their remote url for existing git clones. We can > > call > > > > this out in our contribution docs. > > > > > > > > > > > > > > > > > > > > -- > > Best regards / Met vriendelijke groeten, > > > > Niels Basjes > > > -- Best regards / Met vriendelijke groeten, Niels Basjes
Re: [VOTE] Convert to gitbox
Ryan had filed an Infra ticket to turn it on. I am not sure what the status of that ticket is. I don't have view privileges on that ticket. Suraj On Wed, Dec 6, 2017 at 3:09 AM, Niels Basjes wrote: > Hi, > > I see this transition was started but at this point it does not seem to > work yet. > What is the current status? > > Niels > > On Tue, Aug 29, 2017 at 9:14 PM, Suraj Acharya wrote: > > > +1 > > > > On Tue, Aug 29, 2017 at 11:49 AM, Sean Busbey wrote: > > > > > +1 > > > > > > On 2017-08-29 11:29, "Sean Busbey" wrote: > > > > Way back in May we had consensus[1] on using gitbox so that we could > > > start making use of pull requests. > > > > > > > > In the subsequent JIRAs to implement, it became clear that the entry > > bar > > > to start is convert our repo to use gitbox. this means the writeable > > > repository will be on github and some committer set up will be > > needed[2]. I > > > don't think this got adequately conveyed originally, so I wanted to > call > > it > > > out here. > > > > > > > > Additionally, the infra process for converting to gitbox requires a > > link > > > to a community consensus thread. While I think we already had that back > > in > > > [1], May was a long time ago and some folks might not be watching for > > > [DISCUSS] threads. > > > > > > > > Please vote: > > > > > > > > +1: we should convert to gitbox and enable pull request merging > > > > -1: we should not convert to gitbox because... > > > > > > > > Vote will be open for at least 72 hours and will be subject to > Majority > > > Approval (3 or more +1s and more +1s than -1s). > > > > > > > > [1]: https://s.apache.org/ieB0 > > > > [2]: Committers will need to flag a github account as theirs via the > > > account linking utility: > > > > https://gitbox.apache.org/setup/ > > > > > > > > The git-wip repository will also cease, so folks who currently use it > > > will need to update their remote url for existing git clones. We can > call > > > this out in our contribution docs. > > > > > > > > > > > > > -- > Best regards / Met vriendelijke groeten, > > Niels Basjes >
Re: [VOTE] Convert to gitbox
Hi, I see this transition was started but at this point it does not seem to work yet. What is the current status? Niels On Tue, Aug 29, 2017 at 9:14 PM, Suraj Acharya wrote: > +1 > > On Tue, Aug 29, 2017 at 11:49 AM, Sean Busbey wrote: > > > +1 > > > > On 2017-08-29 11:29, "Sean Busbey" wrote: > > > Way back in May we had consensus[1] on using gitbox so that we could > > start making use of pull requests. > > > > > > In the subsequent JIRAs to implement, it became clear that the entry > bar > > to start is convert our repo to use gitbox. this means the writeable > > repository will be on github and some committer set up will be > needed[2]. I > > don't think this got adequately conveyed originally, so I wanted to call > it > > out here. > > > > > > Additionally, the infra process for converting to gitbox requires a > link > > to a community consensus thread. While I think we already had that back > in > > [1], May was a long time ago and some folks might not be watching for > > [DISCUSS] threads. > > > > > > Please vote: > > > > > > +1: we should convert to gitbox and enable pull request merging > > > -1: we should not convert to gitbox because... > > > > > > Vote will be open for at least 72 hours and will be subject to Majority > > Approval (3 or more +1s and more +1s than -1s). > > > > > > [1]: https://s.apache.org/ieB0 > > > [2]: Committers will need to flag a github account as theirs via the > > account linking utility: > > > https://gitbox.apache.org/setup/ > > > > > > The git-wip repository will also cease, so folks who currently use it > > will need to update their remote url for existing git clones. We can call > > this out in our contribution docs. > > > > > > -- Best regards / Met vriendelijke groeten, Niels Basjes
Re: [VOTE] Convert to gitbox
+1 On Tue, Aug 29, 2017 at 11:49 AM, Sean Busbey wrote: > +1 > > On 2017-08-29 11:29, "Sean Busbey" wrote: > > Way back in May we had consensus[1] on using gitbox so that we could > start making use of pull requests. > > > > In the subsequent JIRAs to implement, it became clear that the entry bar > to start is convert our repo to use gitbox. this means the writeable > repository will be on github and some committer set up will be needed[2]. I > don't think this got adequately conveyed originally, so I wanted to call it > out here. > > > > Additionally, the infra process for converting to gitbox requires a link > to a community consensus thread. While I think we already had that back in > [1], May was a long time ago and some folks might not be watching for > [DISCUSS] threads. > > > > Please vote: > > > > +1: we should convert to gitbox and enable pull request merging > > -1: we should not convert to gitbox because... > > > > Vote will be open for at least 72 hours and will be subject to Majority > Approval (3 or more +1s and more +1s than -1s). > > > > [1]: https://s.apache.org/ieB0 > > [2]: Committers will need to flag a github account as theirs via the > account linking utility: > > https://gitbox.apache.org/setup/ > > > > The git-wip repository will also cease, so folks who currently use it > will need to update their remote url for existing git clones. We can call > this out in our contribution docs. > > >
Re: [VOTE] Convert to gitbox
+1 On 2017-08-29 11:29, "Sean Busbey" wrote: > Way back in May we had consensus[1] on using gitbox so that we could start > making use of pull requests. > > In the subsequent JIRAs to implement, it became clear that the entry bar to > start is convert our repo to use gitbox. this means the writeable repository > will be on github and some committer set up will be needed[2]. I don't think > this got adequately conveyed originally, so I wanted to call it out here. > > Additionally, the infra process for converting to gitbox requires a link to a > community consensus thread. While I think we already had that back in [1], > May was a long time ago and some folks might not be watching for [DISCUSS] > threads. > > Please vote: > > +1: we should convert to gitbox and enable pull request merging > -1: we should not convert to gitbox because... > > Vote will be open for at least 72 hours and will be subject to Majority > Approval (3 or more +1s and more +1s than -1s). > > [1]: https://s.apache.org/ieB0 > [2]: Committers will need to flag a github account as theirs via the account > linking utility: > https://gitbox.apache.org/setup/ > > The git-wip repository will also cease, so folks who currently use it will > need to update their remote url for existing git clones. We can call this out > in our contribution docs. >
Re: [VOTE] Convert to gitbox
+1 On Aug 29, 2017 18:50, "Gabor Szadovszky" wrote: > +1 > > On Tue, Aug 29, 2017 at 6:43 PM, Ryan Blue > wrote: > > > +! > > > > On Tue, Aug 29, 2017 at 9:29 AM, Sean Busbey wrote: > > > > > Way back in May we had consensus[1] on using gitbox so that we could > > start > > > making use of pull requests. > > > > > > In the subsequent JIRAs to implement, it became clear that the entry > bar > > > to start is convert our repo to use gitbox. this means the writeable > > > repository will be on github and some committer set up will be > > needed[2]. I > > > don't think this got adequately conveyed originally, so I wanted to > call > > it > > > out here. > > > > > > Additionally, the infra process for converting to gitbox requires a > link > > > to a community consensus thread. While I think we already had that back > > in > > > [1], May was a long time ago and some folks might not be watching for > > > [DISCUSS] threads. > > > > > > Please vote: > > > > > > +1: we should convert to gitbox and enable pull request merging > > > -1: we should not convert to gitbox because... > > > > > > Vote will be open for at least 72 hours and will be subject to Majority > > > Approval (3 or more +1s and more +1s than -1s). > > > > > > [1]: https://s.apache.org/ieB0 > > > [2]: Committers will need to flag a github account as theirs via the > > > account linking utility: > > > https://gitbox.apache.org/setup/ > > > > > > The git-wip repository will also cease, so folks who currently use it > > will > > > need to update their remote url for existing git clones. We can call > this > > > out in our contribution docs. > > > > > > > > > > > -- > > Ryan Blue > > Software Engineer > > Netflix > > >
Re: [VOTE] Convert to gitbox
+1 On Tue, Aug 29, 2017 at 6:43 PM, Ryan Blue wrote: > +! > > On Tue, Aug 29, 2017 at 9:29 AM, Sean Busbey wrote: > > > Way back in May we had consensus[1] on using gitbox so that we could > start > > making use of pull requests. > > > > In the subsequent JIRAs to implement, it became clear that the entry bar > > to start is convert our repo to use gitbox. this means the writeable > > repository will be on github and some committer set up will be > needed[2]. I > > don't think this got adequately conveyed originally, so I wanted to call > it > > out here. > > > > Additionally, the infra process for converting to gitbox requires a link > > to a community consensus thread. While I think we already had that back > in > > [1], May was a long time ago and some folks might not be watching for > > [DISCUSS] threads. > > > > Please vote: > > > > +1: we should convert to gitbox and enable pull request merging > > -1: we should not convert to gitbox because... > > > > Vote will be open for at least 72 hours and will be subject to Majority > > Approval (3 or more +1s and more +1s than -1s). > > > > [1]: https://s.apache.org/ieB0 > > [2]: Committers will need to flag a github account as theirs via the > > account linking utility: > > https://gitbox.apache.org/setup/ > > > > The git-wip repository will also cease, so folks who currently use it > will > > need to update their remote url for existing git clones. We can call this > > out in our contribution docs. > > > > > > -- > Ryan Blue > Software Engineer > Netflix >
Re: [VOTE] Convert to gitbox
+! On Tue, Aug 29, 2017 at 9:29 AM, Sean Busbey wrote: > Way back in May we had consensus[1] on using gitbox so that we could start > making use of pull requests. > > In the subsequent JIRAs to implement, it became clear that the entry bar > to start is convert our repo to use gitbox. this means the writeable > repository will be on github and some committer set up will be needed[2]. I > don't think this got adequately conveyed originally, so I wanted to call it > out here. > > Additionally, the infra process for converting to gitbox requires a link > to a community consensus thread. While I think we already had that back in > [1], May was a long time ago and some folks might not be watching for > [DISCUSS] threads. > > Please vote: > > +1: we should convert to gitbox and enable pull request merging > -1: we should not convert to gitbox because... > > Vote will be open for at least 72 hours and will be subject to Majority > Approval (3 or more +1s and more +1s than -1s). > > [1]: https://s.apache.org/ieB0 > [2]: Committers will need to flag a github account as theirs via the > account linking utility: > https://gitbox.apache.org/setup/ > > The git-wip repository will also cease, so folks who currently use it will > need to update their remote url for existing git clones. We can call this > out in our contribution docs. > -- Ryan Blue Software Engineer Netflix
[VOTE] Convert to gitbox
Way back in May we had consensus[1] on using gitbox so that we could start making use of pull requests. In the subsequent JIRAs to implement, it became clear that the entry bar to start is convert our repo to use gitbox. this means the writeable repository will be on github and some committer set up will be needed[2]. I don't think this got adequately conveyed originally, so I wanted to call it out here. Additionally, the infra process for converting to gitbox requires a link to a community consensus thread. While I think we already had that back in [1], May was a long time ago and some folks might not be watching for [DISCUSS] threads. Please vote: +1: we should convert to gitbox and enable pull request merging -1: we should not convert to gitbox because... Vote will be open for at least 72 hours and will be subject to Majority Approval (3 or more +1s and more +1s than -1s). [1]: https://s.apache.org/ieB0 [2]: Committers will need to flag a github account as theirs via the account linking utility: https://gitbox.apache.org/setup/ The git-wip repository will also cease, so folks who currently use it will need to update their remote url for existing git clones. We can call this out in our contribution docs.
