On Thu, Dec 6, 2018 at 6:27 PM Mark Thomas <ma...@apache.org> wrote:
>
> On 06/12/2018 08:36, Huxing Zhang wrote:
> > On Thu, Dec 6, 2018 at 4:23 PM yuhang xiu <carry...@gmail.com> wrote:
> >>
> >> Great, this robot is very interesting.
> >>
> >> Netty also has a similar robot[1] that can control whether or not to
> >> perform unit tests (some pr can be judged that we won't accept them during
> >> the review phase), I think we can also try this.
> >> Another feature. It will leave a comment said: 'Can one of the admins
> >> verify this patch?' in a pull request.
> >
> > see examples here: https://github.com/netty/netty/pull/8622
> > That makes things even more interesting.
> >
> > If a robot works as if a human, and make enough contribution, can we
> > vote them in as a committer or event PMC member?
> >
> > If we can do that, we can have robot to help us on the basic stuff,
> > once it has gained merit, the community can grant him/her write
> > access.
> >
> > Sound like a little crazy.. but why not?
>
> Because a bot can't sign an ICLA (it isn't a legal entity).

In fact, if can be someone who create an account, and use the account as robot.
In this way, you can't tell whether it is human or robot behind this account...

>
> To be a little more serious, this boils down to the ASF wanting to limit
> write access to code to committers (for reasons of code provenance) and
> the Github permissions not being granular enough to allow write access
> to issues but not code.

I see the problem here. Even with that limit, the robot can do many
helpful stuff with read-only access.
I am also expecting the robot to have further ability to collaborate
with the mailing list. I've created an issue [1] there.

[1] https://github.com/pouchcontainer/pouchrobot/issues/89

>
> Mark
>
>
> >
> >>
> >> It is very interesting. If we have one, I absolutely agree.
> >> But I don't know how it works. It seems that it is no different from a
> >> normal github user.
> >>
> >> :)
> >>
> >> [1] https://github.com/netty-bot
> >>
> >> Huxing Zhang <hux...@apache.org> 于2018年12月6日周四 下午4:10写道:
> >>
> >>> Hi,
> >>>
> >>> Recently I‘ve chatted with the maintainer of the pouch[1] project, one
> >>> of the interesting thing I learned is that they are using a robot[2]
> >>> to help the collaboration of the community. Typically it can:
> >>>
> >>> * issue/pull request triage (write access)
> >>> * weeklyreport auto generating via a filed issue (read access)
> >>> * some doc auto generation for project via pull request (read access)
> >>> * friendly notice for pull request's status change (read access)
> >>>
> >>> I especially like the idea of auto generate a weekly report, and
> >>> automatically remind the author of pull request that your it needs to
> >>> be rebased.
> >>>
> >>> The issue triage feature is looks great but unfortunately it need
> >>> write access, which is not allowed by ASF.
> >>>
> >>> However, I think it is worth to keep an eye on and maybe try it out.
> >>>
> >>> Thoughts?
> >>>
> >>> [1] https://github.com/alibaba/pouch/
> >>> [2] https://github.com/pouchcontainer/pouchrobot
> >>>
> >>> --
> >>> Best Regards!
> >>> Huxing
> >>>
> >
> >
> >



-- 
Best Regards!
Huxing

Reply via email to