Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: adding initial Community Growth WG proposal #1090

Closed
wants to merge 7 commits into from
Closed

feat: adding initial Community Growth WG proposal #1090

Changes from 6 commits
Commits
Show all changes
7 commits
Select commit Hold shift + click to select a range
a90a491
adding initial the Community Growth WG proposal
Barbanio Mar 8, 2024
7150d9e
grammar fixes
quetzalliwrites Mar 8, 2024
6e46602
Merge branch 'master' into community_growth_wg
thulieblack Mar 11, 2024
29680c3
Merge remote-tracking branch 'asyncapi/master' into community_growth_wg
Barbanio Mar 12, 2024
211847d
Added to Thulie
Barbanio Mar 14, 2024
c8e5c0c
Adding to Maya
Barbanio Mar 22, 2024
ccf9919
Merge branch 'master' into community_growth_wg
quetzalliwrites Mar 29, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 13 additions & 0 deletions WORKING_GROUPS.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -26,3 +26,16 @@ working_groups:
roadmap_url: https://shapeit.app/projects/org/asyncapi/16
okrs_url: https://github.com/users/Amzani/projects/12/views/1
github_team: @asyncapi/developer_experience_wg
- name: Community Growth
description: The Community Working Group aims to ensure AsyncAPI community growth in a healthy and sustainable way.
chairperson: @Barbanio
members:
- @AceTheCreator
- @alequetzalli
- @Mayaleeeee
- @smoya
- @thulieblack
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@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)

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

sure thing, if technically it makes sense then extend the yaml with proper info

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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?

Copy link
Member

@smoya smoya Mar 26, 2024 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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).

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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 ?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ooooh, good question by Thulie... I am curious if she is correct in suggesting we use slack IDs instead!

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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!

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We only needed IDs ( these are local to the org workspace anyway ). Thanks @thulieblack .

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cool. Once this is solved (deciding on the chairperson), I will update this PR (or create a new one, will see) with the changes

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
Loading