docs: added wg-annoucement draft #1213
Conversation
AceTheCreator
changed the title
docs/wg.md
Outdated
|
|
||
| Hey beautiful people, | ||
|
|
||
| I'm thrilled to share some exciting news with you. We've taken a significant leap forward in our journey towards fostering a vibrant and inclusive community by establishing the "Maintainers Growth Working Group." This initiative marks a pivotal moment in our collective effort to not only expand our horizons but also deepen our impact within the AsyncAPI organization. |
There was a problem hiding this comment.
I have the feeling this paragragh is not adding so much content. Please don't take me wrong 🤞, but perhaps using less ornaments and be more precise about what it happened: A new WG has been created.
docs/wg.md
Outdated
| 2. **Enhance the Onboarding Experience**: We recognize the importance of a smooth and welcoming onboarding process for new maintainers. We aim to enhance this experience, making it more intuitive, informative, and supportive, ensuring that new members feel valued and empowered from day one. | ||
| 3. **Embracing Diversity**: A crucial objective of ours is to increase the number of Non-Postman maintainers. We firmly believe that diversity is not just a buzzword, but a strength that can drive innovation and resilience in our community. We're eager to welcome maintainers from all backgrounds and experiences. | ||
| 4. **Building a Support System**: We're fully aware of the challenges and responsibilities that come with being a maintainer. That's why we're not just offering a support system, but we're committed to building a robust one. We'll be there to guide, provide resources, and lend a helping hand whenever needed, ensuring that you feel supported and empowered in your role. | ||
| 5. **Nurturing Talent**: Lastly, we're passionate about identifying and nurturing potential maintainers among our regular contributors. We see immense value in recognizing and encouraging the talents within our community and providing opportunities for growth and leadership. |
There was a problem hiding this comment.
I'm not sure I fully understand the following:
we're passionate about identifying
Do we mean we are able to recommend maintainers to projects? If so, once we did in the past but wasn't take positively by some maintainers because we were not considering their opinions (like "do them really want new maintainers?").
There was a problem hiding this comment.
No, I'm not talking about recommending maintainers for projects. Instead, I'm referring to nurturing contributors so they are prepared if the opportunity to become a maintainer arises. I hope this clarifies my point, @smoya.
docs/wg.md
Outdated
|
|
||
| We're excited to announce that our doors are now open to welcoming new maintainers! If your project could use our support, don't hesitate to reach out. As we're a relatively small team at the moment, we operate on a first-come, first-served basis. With one project already in the queue, it's wise not to delay getting in touch. We're keen to get started and help you as fast as possible. Whether you're an existing member of our community or considering joining us, we're eager to connect. Let's explore how we can support your journey as a maintainer. Your passion, skills, and unique perspective are precious to us. Together, we're confident that we can achieve something truly remarkable. | ||
|
|
||
| In conclusion, the "Maintainers Growth Working Group" is more than just a working group; it's a testament to our commitment to fostering a nurturing, inclusive, and dynamic community. We're on this journey together, and I'm incredibly excited about what we can achieve as a team. Let's roll up our sleeves and make a difference, one step at a time. |
There was a problem hiding this comment.
I would remove this sentence for the same reason I wrote in https://github.com/asyncapi/community/pull/1213/files#r1613532345
|
@AceTheCreator, I rewrote the doc content to make it more professional. Let me know what you think. ❤️ |
|
Soft deadline to review this: Monday 10 Jan. |
There was a problem hiding this comment.
I believe we should add:
- Link and/or handle to our Slack channel
- Link to our GH board https://github.com/orgs/asyncapi/projects/33/views/3
- Info about our bi-weekly meeting (+how to join, etc)
Ping @AceTheCreator |
|
Added the contact section as required. wyt @smoya? |
docs/wg.md
Outdated
|
|
||
| - Joining our [Slack workspace](https://www.asyncapi.com/slack-invite). Please follow our [Slack etiquette](https://github.com/asyncapi/.github/blob/master/slack-etiquette.md) and adhere to the [code of conduct](https://github.com/asyncapi/.github/blob/master/CODE_OF_CONDUCT.md). | ||
|
|
||
| - Joining the dedicated Working Group channel, `#wg-maintainers-growth`, where we discuss all aspects of maintainers' growth. You can find all existing members there. |
There was a problem hiding this comment.
You added two bullet points as if they were different but both are talking about the same. I would simplify into one and reduce the wording by just mentioning about the channel and a link to the slack invite.
Additionally I miss a sentence explaining we do bi-weekly meetings and how to join.
|
@smoya, i added suggested changes. I also wanted to include past recordings, and I thought the best way to do that is if we have a playlist for our meetings. Do you think I should push for that? |
As far as this gets automated on every new meeting it happens, I would +1. If we need to manually add each new meeting into the playlist every time, I would abstain (no permission on Youtube for making it happen so...) |
Okay, let me look into how we can automate it |
Co-authored-by: Sergio Moya <1083296+smoya@users.noreply.github.com>
Co-authored-by: Sergio Moya <1083296+smoya@users.noreply.github.com>
|
/dnm |
The draft of the WG group announcement, as promised in the last WG meeting
cc @smoya @thulieblack @alequetzalli @fmvilas