[tc][uc][meta-sig] How to help SIGs to have a better life? (Needs feedback for SIGs guideline)
Hi all,
The question I would like to ask is, what else we can do here to help SIGs to have a better life? What can we do from here? And is there any feedback regarding on experience of participate a SIG or chairing one?
For some work in progress (or completed) actions: I'm working on a guideline for SIGs ( https://etherpad.openstack.org/p/SIGs-guideline ) because I believe it might provide some value for SIGs, especially new-formed SIGs. Please kindly provide your feedback on it. Will send a patch to update current document under governance-sigs once we got good enough confident on it.
On the other hand, the reason I start this work is because we're thinking `How to help SIGs to have a better life?` There're some actions I can think of and the most easier answers are to get SIGs status, update guidelines and explain why we need SIG in general. So actions: I'm working on SIG guideline ( https://etherpad.openstack.org/p/SIGs-guideline ) and document `Comparison of Official Group Structures` ( https://review.opendev.org/#/c/668093/ ). Also, reach out to SIGs earlier this year to collect help most needed information for SIGs and WGs ( https://etherpad.openstack.org/p/DEN-help-most-needed-for-sigs-and-wgs ) Also, I know Belmiro Moreira (UC member) has reached out to SIGs too, so there are some up to date information. I will try to put all the above information together for share.
And now, back to the question, what can we do from here? Or is there any other feedback? Before I start to disturb everyone with crazy ideas in my mind, would like to hear feedback from all of you.
Finally, feedback on SIG guideline is desired. Thanks!
Rico Lin wrote:
The question I would like to ask is, what else we can do here to help SIGs to have a better life? What can we do from here? And is there any feedback regarding on experience of participate a SIG or chairing one?
I think the best thing we can do to help SIGs to have a better life is to make it as lightweight as possible to run one.
For some work in progress (or completed) actions: I'm working on a guideline for SIGs ( https://etherpad.openstack.org/p/SIGs-guideline%C2%A0)%C2%A0because I believe it might provide some value for SIGs, especially new-formed SIGs. Please kindly provide your feedback on it. Will send a patch to update current document under governance-sigs once we got good enough confident on it.
In the spirit of keeping things lightweight, I feel like this document is already overwhelming. I understand it's meant as a resource guide in case SIGs need guidance, but as it stands it looks a bit intimidating, with its 7 bullet points for "Creating a SIG". Actually the only thing needed to create a SIG is the first bullet point (patch to governance-sigs), everything else is VERY optional.
I wonder if this should not be made a SIG guide (under the model of the Project Team Guide), with:
1. When to create a SIG 1.1 What's a SIG 1.2 SIGs compared to other working groups in OpenStack
2. Process to create a SIG (file that patch, with name, lead(s) and scope)
3. Optional resources available to SIGs 3.1 Communications 3.2 Meetings (in person and online) 3.3 Documentation (wiki...) 3.4 Git Repositories 3.5 Task tracker
4. SIG lifecycle 4.1 Keeping SIG leads and URLs up to date 4.2 Marking SIGs inactive 4.3 Removing a SIG
While it would make a larger document overall, it would IMHO make it clearer what's necessary and what's guidance / optional.
I'm happy to help setting this up as a separate documentation repo, if that sounds like a good idea.
participants (2)
-
Rico Lin
-
Thierry Carrez