-
-
Notifications
You must be signed in to change notification settings - Fork 103
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.
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
Maintainers Growth WG: Define OKRs #1221
Comments
My only thought so far is that I would love to see 1-2 new docs maintainers join us this year that are not from Postman. 🪄🐻 |
I don't have a strong opinion here, but I can say that to grow the maintainers, we need to identify regular contributors who can suit the role of triager or maintainers-in-training. We can start with achievable numbers, say 2-4, figure out what works and doesn't, and then grow from there. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The Maintainers Growth WG decided to focus its efforts on asyncapi/website#2992.
At this point, we know what we want to do regarding tasks, but the results we expect are just rough ideas.
In the past, we talked about increasing the number of non-Postman maintainers. And it seems, based on last conversations during our meetings, that we are still interested in such an objective.
However, I'm opening this issue so we all can discuss this or any other objective we think we should pursue, to end defining its key results along with the metrics we want to track.
I suggest the outcome of this issue should be a clear definition on the objective we pursue (even if its temporary), and a list of key results (we can follow OKR model or any other), ideally along metrics we should track in order to evaluate the success and achievement of such an objective.
I call all WG members and all interested people to share your ideas and opinions and suggestions.
cc @alequetzalli @thulieblack @AceTheCreator @Mayaleeeee @fmvilas @derberg
The text was updated successfully, but these errors were encountered: