You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@apisix.apache.org by Shuyang Wu <sh...@apache.org> on 2021/04/22 05:38:37 UTC
[Discuss] Add GitHub bot to improve community experience
These days, more and more Apache repositories are using GitHub Bot to
improve their community experience for both contributors and reviewers, for
example, by automatically adding labels and make interaction to PR.
(several bot status of apache repos listed in [1])
Due to Apache's rule, we could give our bot any access except directly
writing codes [2-3], so for example our bot could not do cherry-pick
itself. So from what I found, some features we could have with the bot
includes:
1.
Auto-labeling:
1.
PR size: to know the time would be spent on reviewing certain PR
2.
PR area: for example in the dashboard, we could label frontend and
backend, so reviewers could choose which one they'd like to review
3.
Review status: to know how many people have already reviewed or
approved this PR and if it's ready to be merged
4.
Contributor type: whether the PR is contributed by apisix member
2.
Interaction:
1.
Welcome line: for the first-time committer, to tell them what to do
and what to read before further contributions.
2.
Interaction: contributors could assign issues or add labels
themselves, without cc maintainers.
Welcome leave suggestions about the features you would like to have~
Best,
Shuyang
[1]
https://docs.google.com/document/d/1ahM-W_sp8Ajh-0C-uIoGYYi7Zz5tbGEftJY0FoIn9Kc/edit?usp=sharing
[2]
https://issues.apache.org/jira/browse/INFRA-16869 [3]
https://issues.apache.org/jira/browse/INFRA-21108
Re: [Discuss] Add GitHub bot to improve community experience
Posted by Sheng Wu <wu...@gmail.com>.
FYI to SkyWalking's committer team, if anyone of you wants to evaluate this
thing.
Sheng Wu 吴晟
Twitter, wusheng1108
Shuyang Wu <sh...@apache.org> 于2021年4月22日周四 下午1:38写道：
> These days, more and more Apache repositories are using GitHub Bot to
> improve their community experience for both contributors and reviewers, for
> example, by automatically adding labels and make interaction to PR.
> (several bot status of apache repos listed in [1])
>
>
> Due to Apache's rule, we could give our bot any access except directly
> writing codes [2-3], so for example our bot could not do cherry-pick
> itself. So from what I found, some features we could have with the bot
> includes:
>
>
>
> 1.
>
> Auto-labeling:
> 1.
>
> PR size: to know the time would be spent on reviewing certain PR
> 2.
>
> PR area: for example in the dashboard, we could label frontend and
> backend, so reviewers could choose which one they'd like to review
> 3.
>
> Review status: to know how many people have already reviewed or
> approved this PR and if it's ready to be merged
> 4.
>
> Contributor type: whether the PR is contributed by apisix member
> 2.
>
> Interaction:
> 1.
>
> Welcome line: for the first-time committer, to tell them what to do
> and what to read before further contributions.
> 2.
>
> Interaction: contributors could assign issues or add labels
> themselves, without cc maintainers.
>
>
> Welcome leave suggestions about the features you would like to have~
>
> Best,
>
> Shuyang
>
>
> [1]
>
> https://docs.google.com/document/d/1ahM-W_sp8Ajh-0C-uIoGYYi7Zz5tbGEftJY0FoIn9Kc/edit?usp=sharing
> [2]
> https://issues.apache.org/jira/browse/INFRA-16869 [3]
> https://issues.apache.org/jira/browse/INFRA-21108
>
Re: [Discuss] Add GitHub bot to improve community experience
Posted by Ayush das <ay...@gmail.com>.
Not sure about the “closing stale” for now, because many of our repo does
contain good issues and PRs which are idle without any action, we should
first look into those issues and PRs and resolve them. IMO
On Thu, 22 Apr 2021 at 11:13 AM, Ayush das <ay...@gmail.com> wrote:
> I think github bot integration good be a great step.
>
> On Thu, 22 Apr 2021 at 11:08 AM, Shuyang Wu <sh...@apache.org> wrote:
>
>> These days, more and more Apache repositories are using GitHub Bot to
>> improve their community experience for both contributors and reviewers,
>> for
>> example, by automatically adding labels and make interaction to PR.
>> (several bot status of apache repos listed in [1])
>>
>>
>> Due to Apache's rule, we could give our bot any access except directly
>> writing codes [2-3], so for example our bot could not do cherry-pick
>> itself. So from what I found, some features we could have with the bot
>> includes:
>>
>>
>>
>> 1.
>>
>> Auto-labeling:
>> 1.
>>
>> PR size: to know the time would be spent on reviewing certain PR
>> 2.
>>
>> PR area: for example in the dashboard, we could label frontend and
>> backend, so reviewers could choose which one they'd like to review
>> 3.
>>
>> Review status: to know how many people have already reviewed or
>> approved this PR and if it's ready to be merged
>> 4.
>>
>> Contributor type: whether the PR is contributed by apisix member
>> 2.
>>
>> Interaction:
>> 1.
>>
>> Welcome line: for the first-time committer, to tell them what to do
>> and what to read before further contributions.
>> 2.
>>
>> Interaction: contributors could assign issues or add labels
>> themselves, without cc maintainers.
>>
>>
>> Welcome leave suggestions about the features you would like to have~
>>
>> Best,
>>
>> Shuyang
>>
>>
>> [1]
>>
>> https://docs.google.com/document/d/1ahM-W_sp8Ajh-0C-uIoGYYi7Zz5tbGEftJY0FoIn9Kc/edit?usp=sharing
>> [2]
>> https://issues.apache.org/jira/browse/INFRA-16869 [3]
>> https://issues.apache.org/jira/browse/INFRA-21108
>>
>
Re: [Discuss] Add GitHub bot to improve community experience
Posted by Ayush das <ay...@gmail.com>.
I think github bot integration good be a great step.
On Thu, 22 Apr 2021 at 11:08 AM, Shuyang Wu <sh...@apache.org> wrote:
> These days, more and more Apache repositories are using GitHub Bot to
> improve their community experience for both contributors and reviewers, for
> example, by automatically adding labels and make interaction to PR.
> (several bot status of apache repos listed in [1])
>
>
> Due to Apache's rule, we could give our bot any access except directly
> writing codes [2-3], so for example our bot could not do cherry-pick
> itself. So from what I found, some features we could have with the bot
> includes:
>
>
>
> 1.
>
> Auto-labeling:
> 1.
>
> PR size: to know the time would be spent on reviewing certain PR
> 2.
>
> PR area: for example in the dashboard, we could label frontend and
> backend, so reviewers could choose which one they'd like to review
> 3.
>
> Review status: to know how many people have already reviewed or
> approved this PR and if it's ready to be merged
> 4.
>
> Contributor type: whether the PR is contributed by apisix member
> 2.
>
> Interaction:
> 1.
>
> Welcome line: for the first-time committer, to tell them what to do
> and what to read before further contributions.
> 2.
>
> Interaction: contributors could assign issues or add labels
> themselves, without cc maintainers.
>
>
> Welcome leave suggestions about the features you would like to have~
>
> Best,
>
> Shuyang
>
>
> [1]
>
> https://docs.google.com/document/d/1ahM-W_sp8Ajh-0C-uIoGYYi7Zz5tbGEftJY0FoIn9Kc/edit?usp=sharing
> [2]
> https://issues.apache.org/jira/browse/INFRA-16869 [3]
> https://issues.apache.org/jira/browse/INFRA-21108
>
Re: [Discuss] Add GitHub bot to improve community experience
Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,
> Thanks for your recommendation, then I think we may add the "stale"
> label for issues lacking interactions for more than a long while.
I would suggest you don’t do this, but I’ll leave it up to the PMC.
Justin
Re: [Discuss] Add GitHub bot to improve community experience
Posted by Zhiyuan Ju <ju...@apache.org>.
> Before adding the "stale" label, I prefer there is a comment from a real
person to ask the status of the issue first.
I agree with this opinion.
BTW, it seems that our Markdown Link Checker is coming back :)
Best Regards!
@ Zhiyuan Ju <https://github.com/juzhiyuan>
Willem Jiang <wi...@gmail.com> 于2021年4月22日周四 下午7:35写道：
> Before adding the "stale" label, I prefer there is a comment from a
> real person to ask the status of the issue first.
>
> Willem Jiang
>
> Twitter: willemjiang
> Weibo: 姜宁willem
>
> On Thu, Apr 22, 2021 at 3:29 PM Chao Zhang <zc...@gmail.com> wrote:
> >
> > Hi, Justin
> >
> > Thanks for your recommendation, then I think we may add the "stale"
> > label for issues lacking interactions for more than a long while.
> >
> > Best regards
> > Chao Zhang
> >
> > https://github.com/tokers
> >
> > On Thu, Apr 22, 2021 at 3:03 PM Justin Mclean <ju...@classsoftware.com>
> wrote:
> > >
> > > Hi,
> > >
> > > > What about adding the automatic closing stale issue?
> > >
> > > I would recommend against doing this. If you have stale issues it is
> most likely because you haven’t interacted with the contributor or a
> committer has not addressed it. And even if that’s no the case, auto
> closing an issue that someone may care about tells they they are not
> welcome on this project and are likely to stop contributing. Remember this
> is different to a corporate environment and your contributors are
> volunteers.
> > >
> > > Thanks,
> > > Justin
>
Re: [Discuss] Add GitHub bot to improve community experience
Posted by Willem Jiang <wi...@gmail.com>.
Before adding the "stale" label, I prefer there is a comment from a
real person to ask the status of the issue first.
Willem Jiang
Twitter: willemjiang
Weibo: 姜宁willem
On Thu, Apr 22, 2021 at 3:29 PM Chao Zhang <zc...@gmail.com> wrote:
>
> Hi, Justin
>
> Thanks for your recommendation, then I think we may add the "stale"
> label for issues lacking interactions for more than a long while.
>
> Best regards
> Chao Zhang
>
> https://github.com/tokers
>
> On Thu, Apr 22, 2021 at 3:03 PM Justin Mclean <ju...@classsoftware.com> wrote:
> >
> > Hi,
> >
> > > What about adding the automatic closing stale issue?
> >
> > I would recommend against doing this. If you have stale issues it is most likely because you haven’t interacted with the contributor or a committer has not addressed it. And even if that’s no the case, auto closing an issue that someone may care about tells they they are not welcome on this project and are likely to stop contributing. Remember this is different to a corporate environment and your contributors are volunteers.
> >
> > Thanks,
> > Justin
Re: [Discuss] Add GitHub bot to improve community experience
Posted by Chao Zhang <zc...@gmail.com>.
Hi, Justin
Thanks for your recommendation, then I think we may add the "stale"
label for issues lacking interactions for more than a long while.
Best regards
Chao Zhang
https://github.com/tokers
On Thu, Apr 22, 2021 at 3:03 PM Justin Mclean <ju...@classsoftware.com> wrote:
>
> Hi,
>
> > What about adding the automatic closing stale issue?
>
> I would recommend against doing this. If you have stale issues it is most likely because you haven’t interacted with the contributor or a committer has not addressed it. And even if that’s no the case, auto closing an issue that someone may care about tells they they are not welcome on this project and are likely to stop contributing. Remember this is different to a corporate environment and your contributors are volunteers.
>
> Thanks,
> Justin
Re: [Discuss] Add GitHub bot to improve community experience
Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,
> What about adding the automatic closing stale issue?
I would recommend against doing this. If you have stale issues it is most likely because you haven’t interacted with the contributor or a committer has not addressed it. And even if that’s no the case, auto closing an issue that someone may care about tells they they are not welcome on this project and are likely to stop contributing. Remember this is different to a corporate environment and your contributors are volunteers.
Thanks,
Justin
Re: [Discuss] Add GitHub bot to improve community experience
Posted by Chao Zhang <to...@apache.org>.
What about adding the automatic closing stale issue?
Best regards
Chao Zhang
https://github.com/tokers
On Thu, Apr 22, 2021 at 1:38 PM Shuyang Wu <sh...@apache.org> wrote:
>
> These days, more and more Apache repositories are using GitHub Bot to
> improve their community experience for both contributors and reviewers, for
> example, by automatically adding labels and make interaction to PR.
> (several bot status of apache repos listed in [1])
>
>
> Due to Apache's rule, we could give our bot any access except directly
> writing codes [2-3], so for example our bot could not do cherry-pick
> itself. So from what I found, some features we could have with the bot
> includes:
>
>
>
> 1.
>
> Auto-labeling:
> 1.
>
> PR size: to know the time would be spent on reviewing certain PR
> 2.
>
> PR area: for example in the dashboard, we could label frontend and
> backend, so reviewers could choose which one they'd like to review
> 3.
>
> Review status: to know how many people have already reviewed or
> approved this PR and if it's ready to be merged
> 4.
>
> Contributor type: whether the PR is contributed by apisix member
> 2.
>
> Interaction:
> 1.
>
> Welcome line: for the first-time committer, to tell them what to do
> and what to read before further contributions.
> 2.
>
> Interaction: contributors could assign issues or add labels
> themselves, without cc maintainers.
>
>
> Welcome leave suggestions about the features you would like to have~
>
> Best,
>
> Shuyang
>
>
> [1]
> https://docs.google.com/document/d/1ahM-W_sp8Ajh-0C-uIoGYYi7Zz5tbGEftJY0FoIn9Kc/edit?usp=sharing
> [2]
> https://issues.apache.org/jira/browse/INFRA-16869 [3]
> https://issues.apache.org/jira/browse/INFRA-21108