Improving TSC participation in the discussions and voting

[derberg]

Reason/Context

We want to be transparent - thus everything happens on GitHub.
We have a GitHub team with all TSC members that we can tag in GitHub issues/prs/discussions.

All good, right? well in theory yes. We could say that now it is TSC members' duty to know and participate in discussions. No way, we should also try as much as possible to notify TSC members on different channels that there is a discussion and they need to react.

Not all TSC members work on project full time, and counting only of GitHub native notifications is risky (there are 100s of them)

I interviewed different TSC members. Wanted to check what channel of communication would be the best:

• GitHub notification?
• Direct dedicated email?
• Dedicated slack channel?

Guess what 😄 we need all. Which is completely understandable. We offer 3 channels, and TSC members subscribe to those that are the best for them.

Here is the result of the discussions from those that responded:

Name	GitHub Notifications	Direct Email	Slack notifications
Aayush			🟢
Alejandra	🟢		🟢
Anand	🟢
Dale	🟢	🟢	🟢
Gerald		🟢	🟢
Jonas	🟢		🟢
Me	🟢		🟢
Ludovic			🟢
Semen	🟢	🟢
Ace		🟢
Maciej		🟢	🟢
Michael		🟢
Richard			🟢
Souvik			🟢
Tom			🟢
Lewis	🟢
Kieran		🟢	🟢
Dave			🟢
Dan			🟢
Arjun	🟢

The most popular is Slack notifications, but of course we should enable a kind of mailing list where we send notification too.

Description

Slack

• We need new GitHub Action workflow that uses learnings from this workflow and that workflow. It reacts to new comments in issues,PRs and discussions, and drops notifications to new slack channel (whoever picks it up, lemme know to configure that for you). Condition should be that we drop notification only if the comment contains @asyncapi/tsc_members.
• message in slack should use @channel and include link to place in GitHub where discussion happens

GitHub Notifications

We cannot do much here really. Unless somebody knows some magic tricks about GH Notifications that we could describe as a best practice guide for TSC members, like Set up your GH Notifications like a pro

Direct Email

This will be done in the same workflow that we will have for Slack. At the same time we will from Slack notification and email. Email should go to a mailing list, so we do not send it too all but only to those that subscribed to it (spam only those that want it!).

I'm still figuring out the topic of mailing lists with Linux Foundation

☝🏼 ☝🏼 ☝🏼 All of this needs to be documented, a guide for TSC member that we can easily share with anyone☝🏼 ☝🏼 ☝🏼

[derberg]

I don't see anyone picking on this one, so I will focus on Slack notification now on my own

[derberg]

basic notification system for slack is added. TSC members that want to rely on Slack notifications should join #95_bot-tsc-members-mentioned

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity 😴

It will be closed in 120 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation.

There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model.

Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here.

Thank you for your patience ❤️

[derberg]

we still need to enable email notifications

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity 😴

It will be closed in 120 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation.

There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model.

Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here.

Thank you for your patience ❤️

[derberg]

@fmvilas fyi this is the issue related to the TSC and having a mailing list where we can drop notifications, as not all folks are used to follow GH or Slack notifications

[fmvilas]

Yup, on my next cycle https://shapeup.franmendez.blog/cycles/59d8948b. I may even hack on it in the next two weeks. Will update here once it's done.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity 😴

It will be closed in 120 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation.

There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model.

Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here.

Thank you for your patience ❤️

[fmvilas]

Reopening to close it as done 😄