2018-04-11 8:50 GMT+02:00 Ewelina Wilkosz <ewelin...@gmail.com>: > 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? >
My understanding, but so yes it should probably be clarified in any case to avoid having people have their own understanding :), is that it's an OR. So some SIGs could decide to have their meetings as text, or via hangout. For one, I definitely would welcome text-based ones depending on the hour of the day. It's easier when it's late, you're home and cannot easily speak out loud with family around. About, I think it would be more inclusive to (strongly?) recommend to try and have meetings at various hours to help interested people attend. For instance, the current Jenkins governance meeting time is very unfriendly for Aussies (it's roughly 4 AM IIRC). > - "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 > I commented in the PR. It seems like a copy-paste issue from the inspiration <https://github.com/kubernetes/community/blob/master/sig-governance.md> :). > > 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 jenkinsci-dev+unsubscr...@googlegroups.com. > To view this discussion on the web visit https://groups.google.com/d/ > msgid/jenkinsci-dev/8cb01ce8-6cbe-4452-b36e-0aa0b306fd17% > 40googlegroups.com > <https://groups.google.com/d/msgid/jenkinsci-dev/8cb01ce8-6cbe-4452-b36e-0aa0b306fd17%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- 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 jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANWgJS7DHfVroGkAAwdxzAoKcQ%2B-3W0VGEG-PODgEZFUecdr3g%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
