-
Notifications
You must be signed in to change notification settings - Fork 79
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
Add SIGs for Docs and Community Engagement #180
Add SIGs for Docs and Community Engagement #180
Conversation
Signed-off-by: Jonas Rosland <jrosland@vmware.com>
I like 'SIG Community Management' |
@jonasrosland I section languages for translation would be a good point as well. |
@goharbor/all-maintainers can you please review and vote! |
I think this seems fine, but I wonder about @xaleeks's suggestion -- "SIG Community Engagement" vs "SIG Community Management" doesn't seem very different to me, but maybe Alex can elaborate on why the latter should be preferred? 🙏 |
I think it's just wording, in Contour we named it SIG Community and overall that sounds good :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM lets merge :)
@tianon @Vad1mo @jonasrosland @steven-zou please review and approve so we can finish this :) |
@tianon - are you ok with the proposed changes ? if So please approve :) |
Merged!!! Thank you all! |
We've previously discussed updating the governance doc to include more responsibilities under the "Maintainers" title.
After discussion with @caniszczyk the recommendation is to create something like "Doc Maintainers" or "SIG Docs" or "SIG Community Management" within our MAINTAINERS.md, that way the maintainers description can keep as is and we have more flexibility when we want to add more responsibility to awesome contributors.
This PR adds SIG Docs and SIG Community Engagement, with respective owners for each SIG.
Signed-off-by: Jonas Rosland jrosland@vmware.com