I like the idea! And I'd love to be involved I have no strong opinion regarding tools, I'm just finding myself drowning in couple of mail accounts, couple of slack accounts, gitter and IRC... and I find IRC complicated (I know... but really), probably because I have never used it before (I know... but really) and I was surprised to discover it is still alive :) I will adjust, just wondering about people EVEN YOUNGER than me :P
One comment regarding hangout - google has another tool: meet.google.com, which, as far as I understand, is a better hangout. We used it when we had first sessions with Kohsuke regarding JCasC and I was surprised by the quality of sound and video. Any chance we could have an official meet.google.com room instead of hangout? Has anyone else tried both and has the same observation? On Thursday, March 22, 2018 at 10:04:38 PM UTC+1, 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: > > * Clear problem domain/focus area. > * Regularly scheduled and published meetings. I can easily imagine > re-using > #jenkins-meeting or our public YouTube channel for regularly > scheduling > and hosting weekly meetings for these various groups. I run a weekly > infra team sync on jenkins.io/hangout for example, but that's not > recorded anywhere :( > * "Chairs" (i.e. team leads) > * Dedicated discussion channel/group (i.e. mailing list) > > > Some SIGs which I would love to see for starters, would be: > > * Security, lead by Daniel > * GSoC, lead by Oleg > * Infra, lead by Olivier and myself > * Cloud Native (Kubernetes, Jenkins X, CLOUD, etc), lead by Carlos > * Essentials, lead by myself > * LTS, lead by Oliver > * Automation/Configuration (config as code, puppet, chef, etc), lead by > Ewelina > > > From my part on the infrastructure side, I'm more than willing to do the > necessary work to support SIGs, as I really feel like they will help bring > more > folks to the table for focused contribution to the Jenkins project. > > > I'm curious how others feel about a SIG structure and whether you all > agree > that it will help channel/focus discussions and contributions? > > > > If there's strong interest, I'm happy to take point on writing a Process > JEP. > > > Cheers > - R. Tyler Croy > > ------------------------------------------------------ > Code: <https://github.com/rtyler> > Chatter: <https://twitter.com/agentdero> > xmpp: [email protected] <javascript:> > > % gpg --keyserver keys.gnupg.net --recv-key 1426C7DC3F51E16F > ------------------------------------------------------ > -- 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/15cce867-0f40-4de8-9c4a-f1a82c6a08f6%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
