I must say I only briefly scanned the part with all the jenkinsci-foo and sig-foo :( it seemed like a lot indeed. I like the rest of the document though! but this part was almost verwhelming... that's why I asked about SIG Lead responsibility. If we want to do a good job we should make it as easy as possible - not that I'm lazy, but let's be realistic
We can see people being confused about Jenkins Developers and Jenkins Users mailing list - if we have too many groups to choose from I would probably spend so much time trying to figure out which one is the one I should post in On Wednesday, April 11, 2018 at 10:14:33 AM UTC+2, Baptiste Mathus wrote: > > I am fine and love the general idea of giving us progressively more useful > structure as we grow, to help make it easier for people to feel welcome to > contribute without feeling overwhelmed. > > Also fine by me the meetings part, recording it makes sense indeed, for > people interested, but unable to attend for whatever reason. Or offer a way > for newcomers to start lurking before they dare start interacting (I've > been there :)). > > Some comments : > > * I guess the "Report activity in the weekly community meeting at least > once every 6 weeks" could be rephrased like "Report activity in the > bi-weekly governance meeting at least once every 6 weeks"? > > * About > > "Name convention: > jenkinsci-foo (the discussion group) > jenkinsci-foo-leads (list for the leads, to be used with Zoom and > Calendars) > jenkinsci-foo-misc > jenkinsci-foo-test-failures > jenkinsci-foo-bugs > jenkinsci-foo-feature-requests > jenkinsci-foo-proposals > jenkinsci-foo-pr-reviews > jenkinsci-foo-api-reviews" > > > Eeek. Do we really want that? Is this really meant to be 9 mailing lists > to be created per SIG? > > If the answer is yes, I guess we'll have to start writing tooling around > this to make creating SIGs easier. Same for GitHub teams. > > Overall, I do not understand very clearly the intent and pros of that high > level of separation, both on MLs and GH side. But I might be missing > something. > > > Cheers! > > 2018-04-11 3:57 GMT+02:00 R. Tyler Croy <[email protected] <javascript:> > >: > >> (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] <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/jenkinsci-dev/20180411015642.GA1836%40grape.lasagna.io >> . >> 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/926797aa-ec8f-49d6-942c-4cb62911b50f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
