it could be done directly through GitHub.
[1]
http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/Closing-automatically-inactive-pull-requests-tt22248.html
[2]
http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/DISCUSS-GitBox-td18027.html
[3] https://gitbox.apache.org/setup/
ickly, if the commit message is appropriate, as
it could be done directly through GitHub.
[1]
http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/Closing-automatically-inactive-pull-requests-tt22248.html
[2]
http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/DISCUSS
t enable when creating PR?
>
> On Wed, May 16, 2018 at 2:08 PM, Ted Yu wrote:
>
> > +1
> > Original message From: Shuyi Chen
> > Date: 5/16/18 1:12 PM (GMT-08:00) To: dev@flink.apache.org Subject:
> Re:
> > [DISCUSS] GitBox
> > +1 :) A
1:12 PM (GMT-08:00) To: dev@flink.apache.org Subject: Re:
> [DISCUSS] GitBox
> +1 :) A lot of projects <https://gitbox.apache.org/repos/asf> are already
> using it.
>
> On Wed, May 16, 2018 at 3:40 AM, Chesnay Schepler
> wrote:
>
> > Hello,
> >
> > during
+1
Original message From: Shuyi Chen Date:
5/16/18 1:12 PM (GMT-08:00) To: dev@flink.apache.org Subject: Re: [DISCUSS]
GitBox
+1 :) A lot of projects <https://gitbox.apache.org/repos/asf> are already
using it.
On Wed, May 16, 2018 at 3:40 AM, Chesnay Schepler
ontributors. Small changes (like typos)
>may be merged more quickly, if the commit message is appropriate, as
>it could be done directly through GitHub.
>
> [1] http://apache-flink-mailing-list-archive.1008284.n3.nabble.
> com/Closing-automatically-inactive-pull-requests-tt
e to update the website build
> > scripts.
> > >>>The new URL would (probably) be
> > >>>/https://gitbox.apache.org/repos/asf/flink.git/.
> > >>>
> > >>>To make use of GitHub features you have to link your GitHub and
> > >>>Apache accounts. [3]
> > >>>This also requires setting up two-factor authentication on GitHub.
> > >>>
> > >>>Update the scm entry in the parent pom.xml.
> > >>>
> > >>> * What this means for contributors:
> > >>>
> > >>>Nothing should change for contributors. Small changes (like typos)
> > >>>may be merged more quickly, if the commit message is appropriate,
> as
> > >>>it could be done directly through GitHub.
> > >>>
> > >>> [1]
> > >>
> >
> http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/Closing-automatically-inactive-pull-requests-tt22248.html
> > >>> [2]
> > >>
> >
> http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/DISCUSS-GitBox-td18027.html
> > >>> [3] https://gitbox.apache.org/setup/
> > >>
> >
> >
>
apache.org/repos/asf/flink.git/.
> >>>
> >>>To make use of GitHub features you have to link your GitHub and
> >>>Apache accounts. [3]
> >>> This also requires setting up two-factor authentication on GitHub.
> >>>
> >>>Update the scm entry in the parent pom.xml.
> >>>
> >>> * What this means for contributors:
> >>>
> >>>Nothing should change for contributors. Small changes (like typos)
> >>>may be merged more quickly, if the commit message is appropriate, as
> >>>it could be done directly through GitHub.
> >>>
> >>> [1]
> >>
> http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/Closing-automatically-inactive-pull-requests-tt22248.html
> >>> [2]
> >>
> http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/DISCUSS-GitBox-td18027.html
> >>> [3] https://gitbox.apache.org/setup/
> >>
>
>
e-flink-mailing-list-archive.1008284.n3.nabble.com/DISCUSS-GitBox-td18027.html
[3] https://gitbox.apache.org/setup/
t; This also requires setting up two-factor authentication on GitHub.
> > >
> > > Update the scm entry in the parent pom.xml.
> > >
> > > * What this means for contributors:
> > >
> > > Nothing should change for contributors. Small changes (like typos)
> > > may be merged more quickly, if the commit message is appropriate, as
> > > it could be done directly through GitHub.
> > >
> > > [1] http://apache-flink-mailing-list-archive.1008284.n3.
> > nabble.com/Closing-automatically-inactive-pull-requests-tt22248.html
> > > [2] http://apache-flink-mailing-list-archive.1008284.n3.
> > nabble.com/DISCUSS-GitBox-td18027.html
> > > [3] https://gitbox.apache.org/setup/
> >
> >
>
wo-factor authentication on
>GitHub.
>> >
>> > Update the scm entry in the parent pom.xml.
>> >
>> > * What this means for contributors:
>> >
>> > Nothing should change for contributors. Small changes (like
>typos)
>> > may be merged more quickly, if the commit message is appropriate,
>as
>> > it could be done directly through GitHub.
>> >
>> > [1] http://apache-flink-mailing-list-archive.1008284.n3.
>> nabble.com/Closing-automatically-inactive-pull-requests-tt22248.html
>> > [2] http://apache-flink-mailing-list-archive.1008284.n3.
>> nabble.com/DISCUSS-GitBox-td18027.html
>> > [3] https://gitbox.apache.org/setup/
>>
>>
cation on GitHub.
> >
> > Update the scm entry in the parent pom.xml.
> >
> > * What this means for contributors:
> >
> > Nothing should change for contributors. Small changes (like typos)
> > may be merged more quickly, if the commit message is approp
> may be merged more quickly, if the commit message is appropriate, as
> > it could be done directly through GitHub.
> >
> > [1]
> http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/Closing-automatically-inactive-pull-requests-tt22248.html
> > [2]
> http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/DISCUSS-GitBox-td18027.html
> > [3] https://gitbox.apache.org/setup/
>
>
is appropriate, as
> it could be done directly through GitHub.
>
> [1]
> http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/Closing-automatically-inactive-pull-requests-tt22248.html
> [2]
> http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/DISCUSS-GitBox-td18027.html
> [3] https://gitbox.apache.org/setup/
eatures you have to link your GitHub and
>>> Apache accounts. [3]
>>> This also requires setting up two-factor authentication on GitHub.
>>>
>>> Update the scm entry in the parent pom.xml.
>>>
>>> * What this means for contributors:
>>>
>>> Nothing should change for contributors. Small changes (like typos)
>>> may be merged more quickly, if the commit message is appropriate, as
>>> it could be done directly through GitHub.
>>>
>>> [1]
>>> http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/Closing-automatically-inactive-pull-requests-tt22248.html
>>> [2]
>>> http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/DISCUSS-GitBox-td18027.html
>>> [3] https://gitbox.apache.org/setup/
>>>
>>
>
or contributors:
>>
>> Nothing should change for contributors. Small changes (like typos)
>> may be merged more quickly, if the commit message is appropriate, as
>> it could be done directly through GitHub.
>>
>> [1]
>> http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/Closing-automatically-inactive-pull-requests-tt22248.html
>> [2]
>> http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/DISCUSS-GitBox-td18027.html
>> [3] https://gitbox.apache.org/setup/
>>
>
g-automatically-inactive-pull-requests-tt22248.html
[2]
http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/DISCUSS-GitBox-td18027.html
[3] https://gitbox.apache.org/setup/
quickly, if the commit message is appropriate, as
it could be done directly through GitHub.
[1]
http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/Closing-automatically-inactive-pull-requests-tt22248.html
[2]
http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/DISCUSS
nabble.com/PROPOSAL-Apache-Karaf-
Slack-amp-discuss-about-GitBox-td4050669.html>
http://apache-accumulo.1065345.n5.nabble.com/DISCUSS-GitBox-td21160.html
<http://apache-accumulo.1065345.n5.nabble.com/DISCUSS-GitBox-td21160.html
On Jul 18, 2017, at 8:45 AM, Chesnay Schepler wrote:
According to
-about-GitBox-td4050669.html>
>> http://apache-accumulo.1065345.n5.nabble.com/DISCUSS-GitBox-td21160.html
>> <http://apache-accumulo.1065345.n5.nabble.com/DISCUSS-GitBox-td21160.html
>> >
>>
>>
>> On Jul 18, 2017, at 8:45 AM, Chesnay Schepler wrote:
>
ache-Karaf-Slack-amp-discuss-about-GitBox-td4050669.html
<http://karaf.922171.n3.nabble.com/PROPOSAL-Apache-Karaf-Slack-amp-discuss-about-GitBox-td4050669.html>
http://apache-accumulo.1065345.n5.nabble.com/DISCUSS-GitBox-td21160.html
<http://apache-accumulo.1065345.n5.nabble.com/DISCUSS-
uss-about-GitBox-td4050669.html>
http://apache-accumulo.1065345.n5.nabble.com/DISCUSS-GitBox-td21160.html
<http://apache-accumulo.1065345.n5.nabble.com/DISCUSS-GitBox-td21160.html>
> On Jul 18, 2017, at 8:45 AM, Chesnay Schepler wrote:
>
> According to the JIRA you linked,
https://gitbox.apache.org/
[1] https://github.com/apache/flink-web/pulls
[2]
http://apache-accumulo.1065345.n5.nabble.com/DISCUSS-
GitBox-tp21160p21497.html
Greg
t;>>>>>>>>>> links to talks or slides left open for months.
>>>>>>>>>>>
>>>>>>>>>>> I’d suggest Fluo is to Accumulo as flink-web is to the flink repo,
>>>>>>>>>>> and
>>>>>>>>>>> that migration looks to be satisfactory.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> On Jun 9, 2017, at 11:15 AM, Ted Yu wrote:
>>>>>>>>>>>>
>>>>>>>>>>>> bq. better track the oft-neglected contributions
>>>>>>>>>>>>
>>>>>>>>>>>> Do you have estimate on how many contributions were not paid
>>>>>>> attention in
>>>>>>>>>>>> the current infrastructure.
>>>>>>>>>>>>
>>>>>>>>>>>> Looking at #2, it seems Accumulo community hasn't reached consensus
>>>>>>> yet.
>>>>>>>>>>>> Cheers
>>>>>>>>>>>>
>>>>>>>>>>>> On Fri, Jun 9, 2017 at 7:54 AM, Greg Hogan
>>>>>>> wrote:
>>>>>>>>>>>>> All,
>>>>>>>>>>>>>
>>>>>>>>>>>>> ASF now has available (and maybe mandatory for new projects or
>>>>>>> repos)
>>>>>>>>>>>>> GitBox [0] which enables bi-directional sync to GitHub and links
>>>>>>>>>>>>> committers' accounts, allowing for greater use of GitHub
>>>>>>> functionality
>>>>>>>>>>>>> by
>>>>>>>>>>>>> contributors and for committers to perform many tasks otherwise
>>>>>>>>>>>>> requiring
>>>>>>>>>>>>> INFRA tickets.
>>>>>>>>>>>>>
>>>>>>>>>>>>> I'd like to propose moving flink-web [1] to GitBox, using GitHub
>>>>>>> issues,
>>>>>>>>>>>>> and enabling notifications to the mailing lists. Apache Accumulo
>>>>>>>>>>>>> has
>>>>>>>>>>>>> recently discussed [2] this topic with a list of benefits after
>>>>>>>>>>>>> migrating
>>>>>>>>>>>>> Fluo. By migrating flink-web we can better track the oft-neglected
>>>>>>>>>>>>> contributions and also test the waters for future migrations
>>>>>>> (perhaps
>>>>>>>>>>>>> for
>>>>>>>>>>>>> the future sub-projects).
>>>>>>>>>>>>>
>>>>>>>>>>>>> [0] https://gitbox.apache.org/
>>>>>>>>>>>>> [1] https://github.com/apache/flink-web/pulls
>>>>>>>>>>>>> [2]
>>>>>>>>>>>>> http://apache-accumulo.1065345.n5.nabble.com/DISCUSS-
>>>>>>>>>>>>> GitBox-tp21160p21497.html
>>>>>>>>>>>>>
>>>>>>>>>>>>> Greg
>>>>
>>>
>>
>>
>
igrating
Fluo. By migrating flink-web we can better track the
oft-neglected
contributions and also test the waters for future migrations
(perhaps
for
the future sub-projects).
[0] https://gitbox.apache.org/
[1] https://github.com/apache/flink-web/pulls
[2]
http://apache-accumulo.1065345.n5.nabble.com/DISCUSS-
GitBox-tp21160p21497.html
Greg
://gitbox.apache.org/
[1] https://github.com/apache/flink-web/pulls
[2]
http://apache-accumulo.1065345.n5.nabble.com/DISCUSS-
GitBox-tp21160p21497.html
Greg
com/apache/flink-web/pulls
[2]
http://apache-accumulo.1065345.n5.nabble.com/DISCUSS-
GitBox-tp21160p21497.html
Greg
n Fri, Jun 9, 2017 at 7:54 AM, Greg Hogan
>>> wrote:
>>>>>>>>> All,
>>>>>>>>>
>>>>>>>>> ASF now has available (and maybe mandatory for new projects or
>>> repos)
>>>>>>>>> GitBox [0] which enables bi-directional sync to GitHub and links
>>>>>>>>> committers' accounts, allowing for greater use of GitHub
>>> functionality
>>>>>>>>> by
>>>>>>>>> contributors and for committers to perform many tasks otherwise
>>>>>>>>> requiring
>>>>>>>>> INFRA tickets.
>>>>>>>>>
>>>>>>>>> I'd like to propose moving flink-web [1] to GitBox, using GitHub
>>> issues,
>>>>>>>>> and enabling notifications to the mailing lists. Apache Accumulo has
>>>>>>>>> recently discussed [2] this topic with a list of benefits after
>>>>>>>>> migrating
>>>>>>>>> Fluo. By migrating flink-web we can better track the oft-neglected
>>>>>>>>> contributions and also test the waters for future migrations
>>> (perhaps
>>>>>>>>> for
>>>>>>>>> the future sub-projects).
>>>>>>>>>
>>>>>>>>> [0] https://gitbox.apache.org/
>>>>>>>>> [1] https://github.com/apache/flink-web/pulls
>>>>>>>>> [2]
>>>>>>>>> http://apache-accumulo.1065345.n5.nabble.com/DISCUSS-
>>>>>>>>> GitBox-tp21160p21497.html
>>>>>>>>>
>>>>>>>>> Greg
>>>>>>
>>>
>
ing
Fluo. By migrating flink-web we can better track the oft-neglected
contributions and also test the waters for future migrations
(perhaps
for
the future sub-projects).
[0] https://gitbox.apache.org/
[1] https://github.com/apache/flink-web/pulls
[2]
http://apache-accumulo.1065345.n5.nabble.com/DISCUSS-
GitBox-tp21160p21497.html
Greg
f GitHub
> functionality
> >>>>>> by
> >>>>>> contributors and for committers to perform many tasks otherwise
> >>>>>> requiring
> >>>>>> INFRA tickets.
> >>>>>>
> >>>>>> I'd like to propose moving flink-web [1] to GitBox, using GitHub
> issues,
> >>>>>> and enabling notifications to the mailing lists. Apache Accumulo has
> >>>>>> recently discussed [2] this topic with a list of benefits after
> >>>>>> migrating
> >>>>>> Fluo. By migrating flink-web we can better track the oft-neglected
> >>>>>> contributions and also test the waters for future migrations
> (perhaps
> >>>>>> for
> >>>>>> the future sub-projects).
> >>>>>>
> >>>>>> [0] https://gitbox.apache.org/
> >>>>>> [1] https://github.com/apache/flink-web/pulls
> >>>>>> [2]
> >>>>>> http://apache-accumulo.1065345.n5.nabble.com/DISCUSS-
> >>>>>> GitBox-tp21160p21497.html
> >>>>>>
> >>>>>> Greg
> >>>
> >>>
> >
>
>
to perform many tasks otherwise
>>>>>> requiring
>>>>>> INFRA tickets.
>>>>>>
>>>>>> I'd like to propose moving flink-web [1] to GitBox, using GitHub issues,
>>>>>> and enabling notifications to the mailing lists. Apache Accumulo has
>>>>>> recently discussed [2] this topic with a list of benefits after
>>>>>> migrating
>>>>>> Fluo. By migrating flink-web we can better track the oft-neglected
>>>>>> contributions and also test the waters for future migrations (perhaps
>>>>>> for
>>>>>> the future sub-projects).
>>>>>>
>>>>>> [0] https://gitbox.apache.org/
>>>>>> [1] https://github.com/apache/flink-web/pulls
>>>>>> [2]
>>>>>> http://apache-accumulo.1065345.n5.nabble.com/DISCUSS-
>>>>>> GitBox-tp21160p21497.html
>>>>>>
>>>>>> Greg
>>>
>>>
>
/apache-accumulo.1065345.n5.nabble.com/DISCUSS-
GitBox-tp21160p21497.html
Greg
gt;>> INFRA tickets.
>>>>
>>>> I'd like to propose moving flink-web [1] to GitBox, using GitHub issues,
>>>> and enabling notifications to the mailing lists. Apache Accumulo has
>>>> recently discussed [2] this topic with a list of benefit
ed
contributions and also test the waters for future migrations (perhaps for
the future sub-projects).
[0] https://gitbox.apache.org/
[1] https://github.com/apache/flink-web/pulls
[2]
http://apache-accumulo.1065345.n5.nabble.com/DISCUSS-
GitBox-tp21160p21497.html
Greg
tly discussed [2] this topic with a list of benefits after migrating
>> Fluo. By migrating flink-web we can better track the oft-neglected
>> contributions and also test the waters for future migrations (perhaps for
>> the future sub-projects).
>>
>> [0] https://gitbo
ing flink-web we can better track the oft-neglected
> contributions and also test the waters for future migrations (perhaps for
> the future sub-projects).
>
> [0] https://gitbox.apache.org/
> [1] https://github.com/apache/flink-web/pulls
> [2]
> http://apache-accumulo.1065345.n5.nabble.com/DISCUSS-
> GitBox-tp21160p21497.html
>
> Greg
>
-neglected
contributions and also test the waters for future migrations (perhaps for
the future sub-projects).
[0] https://gitbox.apache.org/
[1] https://github.com/apache/flink-web/pulls
[2]
http://apache-accumulo.1065345.n5.nabble.com/DISCUSS-GitBox-tp21160p21497.html
Greg
37 matches
Mail list logo
