My understanding of the functions of the oss bot.

[morningman]

How it works

First, we can associate the oos bot to our git repo, or in other word, authorize some permissions of the git repo to the oos bot.

At the same time, the oos bot can be associated with a WeChat group(or mail list). This established a git repo-> oos bot-> WeChat group channel.

Afterwards, the oos bot will detect events on the git repo, such as new issue submissions, and the oos bot will sync these issues to the WeChat group or mail list.

Members of WeChat group (or mail group) should be committers or long-term contributors to open source projects.

Furthermore, the oos bot can detect which issues have not been responded to, or other custom monitoring conditions (such as the "issue is not classified", "there is no milestone", etc.). And based on these conditions, send reminder messages (separate or summary) to the WeChat group or mail list. This makes it easier for project maintainers to better handle these issues.

Mail List

I understand that one of the main purposes of the oos bot is to solve the mail list management issues related to open source projects (especially the apache project). Most apache projects (especially those in China), because of habit issues, do not pay much attention to the use of mail list.

I think oos bot can strengthen the management of mail list in the following aspects:

1. Sync issue content (in clear mail format) to dev mail list. Responses to issues can be sent to the same mail thread.
2. Send a reminder email (such as "an issue that has not been processed for a long time") to a private mail list.
3. Periodically summarize the issue processing situation for a period of time and send it to the private mail list. Such as "how many issues in a week".

[huan]

Thanks for your summarization!

I believe it's clear enough for us that that's exactly the direction that we are heading to.

[tedliu1]

It is ossbot, not oos bot.

Best regards,

Ted Liu,  Co-founder & chairman of the board, KAIYUANSHE | ASF Member, Sponsor Ambassador, Incubator PMC Member

2020 年 1 月 1 日周三 23:31，Mingyu Chen[email protected] 写道：
How it works

First, we can associate the oos bot to our git repo, or in other word, authorize some permissions of the git repo to the oos bot.

At the same time, the oos bot can be associated with a WeChat group(or mail list). This established a git repo-> oos bot-> WeChat group channel.

Afterwards, the oos bot will detect events on the git repo, such as new issue submissions, and the oos bot will sync these issues to the WeChat group or mail list.

Members of WeChat group (or mail group) should be committers or long-term contributors to open source projects.

Furthermore, the oos bot can detect which issues have not been responded to, or other custom monitoring conditions (such as the "issue is not classified", "there is no milestone", etc.). And based on these conditions, send reminder messages (separate or summary) to the WeChat group or mail list. This makes it easier for project maintainers to better handle these issues.

Mail List

I understand that one of the main purposes of the oos bot is to solve the mail list management issues related to open source projects (especially the apache project). Most apache projects (especially those in China), because of habit issues, do not pay much attention to the use of mail list.

I think oos bot can strengthen the management of mail list in the following aspects:

• Sync issue content (in clear mail format) to dev mail list. Responses to issues can be sent to the same mail thread.
• Send a reminder email (such as "an issue that has not been processed for a long time") to a private mail list.
• Periodically summarize the issue processing situation for a period of time and send it to the private mail list. Such as "how many issues in a week".

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or unsubscribe.

[dz85]

cool! focusing~