feat: adding initial Community Growth WG proposal #1090
Conversation
Barbanio
requested review from
quetzalliwrites,
derberg,
asyncapi-bot-eve and
thulieblack
as code owners
|
Thank you @Barbanio for helping us broaden the WG scope! |
|
🎉 👏 PS: Please remind me to create the |
Barbanio
dismissed stale reviews from thulieblack and quetzalliwrites
via
29680c3
|
Reminder that this should be approved by the TSC and I somehow overlooked it 😓 Make sure you mention the TSC and ask for votes. Maybe someone else wants to join the WG too. |
|
/dnm |
Voting from @asyncapi/tsc_members happening now at https://github.com/orgs/asyncapi/discussions/1094 |
| - @alequetzalli | ||
| - @Mayaleeeee | ||
| - @smoya | ||
| - @thulieblack |
There was a problem hiding this comment.
@Shurtu-gal gave me feedback coming from #1072 regarding the fact there are no Slack handles in this file. That will complicate automation of Slack channels and aliases creation since we do not have a real database of GH User -> Slack Handle (or vice-versa).
Do you believe we should add somehow those Slack handles here as well? I do, but not sure how 🤔
Ideas? cc @derberg @fmvilas (who iirc were involved in the initial creation of the structure of this file)
There was a problem hiding this comment.
sure thing, if technically it makes sense then extend the yaml with proper info
There was a problem hiding this comment.
Hmm.. I can certainly see the value in adding our Slack handles, given the asynchronous nature of our work and Slack is our primary communication method. 😸
Is it as simple to add them manually to this file?
There was a problem hiding this comment.
Maybe something like this could be ok?
- name: Community Growth
description: The Community Working Group aims to ensure AsyncAPI community growth in a healthy and sustainable way.
chairperson:
name: Barbaño González
email: [email protected]
github: '@Barbanio'
slack: '@Barbaño González'
members:
- name: Elegbede Azeez
email: [email protected]
github: '@AceTheCreator'
slack: '@Ace'
- name: Alejandra Quetzalli
email: [email protected]
github: '@alequetzalli'
slack: '@Quetzalli'
- name: Aishat Muibudeen
email: [email protected]
github: '@Mayaleeeee'
slack: '@Maya'
- name: Sergio Moya
email: [email protected]
github: '@smoya'
slack: '@Sergio Moya'
- name: Thulisile Sibanda
email: [email protected]
github: '@thulieblack'
slack: '@Thulie'
slack_channel: community-growth-wg
roadmap_url: https://github.com/orgs/asyncapi/projects/33/views/8
okrs_url: https://github.com/orgs/asyncapi/projects/33/views/12
github_team: '@asyncapi/community_growth_wg'I noticed we need those single quotes I added because otherwise the YAML is invalid (strings can't start by @, another solution could be just removing the @ character as in https://github.com/asyncapi/community/blob/master/MAINTAINERS.yaml). BTW, emails are invented. Names are added exactly as in Slack profiles so feel free to change yours if you don't want to appear like that.
EDIT: Added the email but not sure if really required. I thought about adding it just in case we need to create meetings or email members at some point. But of course we can't create @asyncapi.com emails for everyone, so maybe just using personal email and make it optional? Nevermind, we can skip the email by now until we find is fully required (if happens).
There was a problem hiding this comment.
Shouldn't we add slack IDs instead of names similar to how we have it in https://github.com/asyncapi/community/blob/master/TSC_MEMBERS.json ?
There was a problem hiding this comment.
ooooh, good question by Thulie... I am curious if she is correct in suggesting we use slack IDs instead!
There was a problem hiding this comment.
Yeah good point. Ids are consistent. Using names will be fragile because what if you change your display name!
So yes, we should do change it and use IDs instead.
Nice catch!
There was a problem hiding this comment.
We only needed IDs ( these are local to the org workspace anyway ). Thanks @thulieblack .
There was a problem hiding this comment.
Cool. Once this is solved (deciding on the chairperson), I will update this PR (or create a new one, will see) with the changes
After incorporating the working groups as a possible working system in AsyncAPI, @AceTheCreator, @alequetzalli, @smoya, and myself, we propose the creation of the Community Growth working group.
The 4 of us initiated the group, but the group is open to anyone who wants to join.
The group members proposed to me as the initial chairperson (rotating role). Following the fantastic scheme proposed by the DX working group, the chairperson will be accountable and responsible for the following:
Responsibilities of the members
Requirement to join as a member