-
Notifications
You must be signed in to change notification settings - Fork 242
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
🔧 Repository: Expand governance on community-plugins maintainers #1766
Comments
One final criteria could be 'Additional member approved by existing community plugins maintainers' |
Being active in the Backstage repo itself as well as running a Backstage instance at an Organization would be really helpful to have. I would personally weigh these things higher than what is noted in this issue description. |
I agree with those as supporting contributions as they're useful for general context. But, I would imagine contributing to the |
We already have some docs here: https://github.com/backstage/community/blob/main/GOVERNANCE.md#project-area-maintainer |
📜 Description
As discussed in the SIG, we need explicit guidelines on how to transition from a plugin owner to a plugins maintainer within the community-plugins repository.
Here are some suggested criteria to include:
Thoughts?
👍 Expected behavior
We have explicit guidelines on how to transition from a plugin owner to a plugins maintainer within the community-plugins repository
👎 Current Behavior
We don't have explicit guidelines on how to transition from a plugin owner to a plugins maintainer within the community-plugins repository
👟 Reproduction steps
NA
📃 Provide the context for the Bug.
No response
👀 Have you spent some time to check if this bug has been raised before?
🏢 Have you read the Code of Conduct?
Are you willing to submit PR?
Yes I am willing to submit a PR!
The text was updated successfully, but these errors were encountered: