Good job! I'll just comment what I think could be clarified, really small things...
- "Record SIG meeting, such as via YouTube Live Streaming, and make it publicly available. Text-based meetings can use #jenkins-meeting on Freenode.." - So is it obligatory to record a meeting or not? should we user YouTube AND #jenkins-meeting or one of those? - "Submit a PR to add a row for the SIG to the table in the kubernetes/community README.md file, to create a kubernetes/community directory, and to add any SIG-related docs, schedules, roadmaps, etc. to your new kubernetes/community/SIG-foo directory." - maybe I'm missing something here but is 'kubernetes' here an example or what? What's the repository? sorry if it's a dumb question :) I'm simply disoriented Is SIG Lead one person responsible for all the administration - recording, maintaining communication channels, github accounts etc? Or can this role be shared? In general I like the document, easy to read, explain motivation behind the SIG idea in a nice way. And I do believe we can benefit from having those. Just want to make sure SIG Lead won't drown in an "office work" - maintaining all the accounts, documents etc :) Meeting every 3 weeks sound like a good balance. BR Ewelina On Wednesday, April 11, 2018 at 3:57:35 AM UTC+2, R Tyler Croy wrote: > > (replies inline) > > On Thu, 22 Mar 2018, R. Tyler Croy wrote: > > > > > I have been looking at some of the great things the Kubernetes community > has > > been doing for ideas we can borrow, and one idea which really sticks out > is: > > Special Interest Groups (SIGs) > > < > https://github.com/kubernetes/community/blob/master/governance.md#sigs> > > > > A full list of the Kubernetes community SIGs can be found here: > > <https://github.com/kubernetes/community/blob/master/sig-list.md> > > > > I think we already have some groups, which are almost informal SIGs, > such as > > Security, GSoC, Infra, etc. The aspects of SIGs which I really would > like to > > formalize, and support from a community infra standpoint are: > > > Here's an update, I've written out my first draft of what SIGs might look > like > for us here: https://github.com/jenkinsci/jep/pull/81 > > Please let me know what you all think, I'm especially curious for Daniel, > Oliver, Ewelina, and Carlos's thoughts as I am hoping this helps you all > get > more contribution and focus :) > > > > Cheers > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/8cb01ce8-6cbe-4452-b36e-0aa0b306fd17%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
