You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Over the past few weeks, the Maintainers Growth Working Group (MGWG), which aims to help grow the number of maintainers at AsyncAPI, has been meeting to establish clear objectives and desired outcomes.
We aim to start by focusing on a single project, enabling us to work together efficiently and address any challenges maintainers may face.
We believe it’s beneficial to set our goals dynamically, based on a single project, rather than having abstract, global goals.
More details about our mission and goals are a WIP here.
Proposed Project
During one of our recent meetings, @derberg suggested that we could contribute to the Automation/CI/CD project. As far as I know, this includes the work currently being done in:
Please let us know if there are any other repositories we should include.
Your Input
On behalf of the Maintainers Growth Working Group, we would like to:
Gather feedback on your current needs and challenges.
Understand how we can help scale the project sustainably.
Understanding your short, medium, and long-term growth expectations regarding maintainers.
Some examples of potential areas of contribution could be:
Creating documentation to help turn contributors into maintainers.
Reducing learning curves to attract more contributors (potential future maintainers).
Any other you consider
These are just initial ideas. We don’t want to limit your suggestions or influence your priorities. Our goal is to support you in the best way possible.
Contact
We are also available for further discussion on Slack in the #wg-maintainers-growth channel.
We are open to set up a call with the maintainers of your project. Also you can join our regular meetings as well.
Thank you very much for your time and consideration. We look forward to collaborating with you!
in short: for maintainers of https://github.com/asyncapi/saunter (and any other future maintainers) we need docs that describe how "global workflows" work and what are they. I already identified this need when I started onboarding 2 potential maintainers to generator repo. My first meeting was focused on explaining the workflows that we have for generator only, maintained in generator repo. Next session will be about the global workflows.
So I will record a video and I need someone who can turn it into structured docs, good maintainer guide that will be easily discoverable as it will be displayed in asyncapi.com
Introduction
Over the past few weeks, the Maintainers Growth Working Group (MGWG), which aims to help grow the number of maintainers at AsyncAPI, has been meeting to establish clear objectives and desired outcomes.
We aim to start by focusing on a single project, enabling us to work together efficiently and address any challenges maintainers may face.
We believe it’s beneficial to set our goals dynamically, based on a single project, rather than having abstract, global goals.
More details about our mission and goals are a WIP here.
Proposed Project
During one of our recent meetings, @derberg suggested that we could contribute to the Automation/CI/CD project. As far as I know, this includes the work currently being done in:
Please let us know if there are any other repositories we should include.
Your Input
On behalf of the Maintainers Growth Working Group, we would like to:
Some examples of potential areas of contribution could be:
These are just initial ideas. We don’t want to limit your suggestions or influence your priorities. Our goal is to support you in the best way possible.
Contact
We are also available for further discussion on Slack in the #wg-maintainers-growth channel.
We are open to set up a call with the maintainers of your project. Also you can join our regular meetings as well.
Thank you very much for your time and consideration. We look forward to collaborating with you!
cc @alequetzalli @thulieblack @Mayaleeeee @AceTheCreator @derberg @KhudaDad414
The text was updated successfully, but these errors were encountered: