Thanks for your support!
But I have some questions about it. What is a Github bot????Github app??Github
action??or others????Could you please give me some information for reference??
Thanks
------------------ ???????? ------------------
??????:
"dev"
<[email protected]>;
????????: 2021??8??31??(??????) ????3:21
??????: "Dev"<[email protected]>;"Matteo
Merli"<[email protected]>;
????: "[email protected]"<[email protected]>;"[email protected]"<[email protected]>;
????: Re: [Workflow] Introduce Bot to Improve Efficiency
Il giorno mar 31 ago 2021 alle ore 08:28 Anonymitaet _ <
[email protected]> ha scritto:
> Hi Pulsar enthusiasts,
>
>
>
> Thanks for your support!
>
>
>
> Since we have reached a consensus, we are considering implementing Bot to
> Pulsar using GitHub Bot <https://github.com/xuexb/github-bot>. The
> general steps are as follows:
>
> 1. Start an HTTP server based on koajs on the server.
> 2. Establish some project specifications (such as pull
request format,
> configure some owners with specified labels, etc.).
> 3. Let the Bot (usually a separate account)
automatically handle some
> things based on GitHub webhooks and GitHub API.
>
>
>
> These procedures make us think about the following questions. Can anyone
> help answer? Thank you very much!
>
> 1. **Will the Pulsar community provide an email account
to the Bot? **
> So that we can register the bot with the email address.
>
>
We can create a dedicated mailing list for this, like [email protected]
.
But we need the PMC to agree on this, I am not sure about the procedure to
follow (@Matteo ?)
>
> 1.
> 2. As instructed by step a), **will the Pulsar community
assign some
> resources (for example, a Linux server) to run the Bot?
**
>
> Can this run as a GitHub bot ? Otherwise it will be something that is hard
to maintain, btw we can ask Apache INFRA for a simple VM,
I am not sure about Security risks, adding a new machine means adding
something to protect and to maintain.
Especially if this machine will have some special permission to act on the
repository.
If we could have something like a batch scheduled job that scans the PRs
and does the work it would be very easier.
It could run on GH actions or on ASF Jenkins
>
> 1.
> 2. As instructed by step c), the Bot needs some
permissions to manage
> the Pulsar project (for example, it needs access to use
??Manage access?? and
> ??Webhooks?? features in ??Settings??), **will the
Pulsar community grant
> those access to the Bot?**
>
>
We can do this
But the critical point is to decide where this bot should live.
Enrico
>
> 1.
>
>
>
> Tao & Anonymitaet
>
>
>
> *From: *Guangning E <[email protected]>
> *Reply-To: *"[email protected]" <[email protected]>
> *Date: *Monday, August 30, 2021 at 15:15
> *To: *"[email protected]" <[email protected]>
> *Cc: *Matteo Merli <[email protected]>, "[email protected]" <
> [email protected]>, "[email protected]"
<[email protected]>
> *Subject: *Re: [Workflow] Introduce Bot to Improve Efficiency
>
>
>
> +1
>
>
>
>
>
>
>
> Thanks,
>
> Guangning
>
>
>
> Enrico Olivelli <[email protected]> ??2021??8??30?????? ????3:07??????
>
> +1
>
> good idea to have a bot, otherwise I see much time wasted by you in always
> asking the same things.
>
> I appreciate very much your efforts
>
>
>
> Probably this document fits well to be listed in the PIPs page, it is not
> about code but about community/project management
>
> @Matteo Merli <[email protected]> what do you think?
>
>
>
>
>
>
>
> Enrico
>
>
>
> Il giorno lun 30 ago 2021 alle ore 02:55 Anonymitaet _ <
> [email protected]> ha scritto:
>
> Hi Pulsar enthusiasts,
>
>
>
> To improve doc workflow efficiency, we want to introduce Bot to Pulsar
> community.
>
>
>
> To make things clear, we??ve written a proposal and recorded a demo.
>
> - [Discussion] Introduce Bot to Improve Doc Workflow
Efficiency
>
<https://docs.google.com/document/d/1bQfZkSu5nG1tNycpmXXtUFn-Z5-h-uqHv6IXsCEySQ8/edit>
> - [Demo] How Bot Improves Doc Workflow Efficiency
>
<https://drive.google.com/drive/u/0/folders/1a0erKa2KN81LYR-a5EvBlsaoQA2t9i1Y>
>
>
>
> We??d love your feedback! Feel free to comment *before EOD Sep 2 GMT+8*.
Many
> thanks!
>
>
>
> Tao & Anonymitaet
>
>
>
>
>
>
