I think I will need to work a bit on the "Newcomer" idea, so let's park it for now.
Just to provide some heads-up, we will be establishing Gitter channels for EDA Plugins <https://jenkins.io/projects/gsoc/2018/eda-plugins/> and Remoting over Message Queue/Bus <https://jenkins.io/projects/gsoc/2018/remoting-over-message-bus/> GSoC projects. In both cases they could be SIGs according to the definition in the beginning: - Electronic Design Automation plugins are unlikely interesting to a significant part of Jenkins developers, so maybe it makes sense to call it a SIG (e.g. "Electronic Design Automation and Hardware") and to move some specific discussions there. - Me and Martin could be chairs, for example - Remoting is already listed as subproject <https://jenkins.io/projects/>, and it's more tricky. - Remoting is a part of the core, and IMHO it does not make sense to keep mailing lists separate. - Having a Remoting/Agent-specific **dev** chat could be useful so that Remoting maintainers can synchronize with agent plugin maintainers (e.g. adopting features like -workDir, etc.) - Not sure it qualifies as SIG, feedback would be appreciated BR, Oleg On Tuesday, April 17, 2018 at 11:58:14 PM UTC+2, R Tyler Croy wrote: > > (replies inline) > > On Tue, 17 Apr 2018, Oleg Nenashev wrote: > > > Hi, > > > > We are starting GSoC meetings next week. If you need somebody to dry-run > > the SIG infrastructure, sign us up :) > > > > Reasoning: Having recorded GSoC sessions would be definitely helpful so > > that we can share meetings with students/mentors who miss meetings. OTOH > I > > am not sure whether this content is useful for other community members. > > > > Actually I would propose to have 2 SIGs: > > > > - GSoC - special for GSoC. All infrastructure is ready > > - Newcomer onboarding - Another SIG for newcomers in Jenkins > community + > > Q&As + discussions about contributor experience > > - We could split generic GSoC meetings to there (e.g. plugin > > development intros & Co) > > > I'll add you as a manager to the Brand Account so you can use Hangouts on > Air > for the GSoC discussions. I agreed that a GSoC Special Interest Group > makes > sense, I don't think a "Newcomer" one does because I don't understand what > the > "regular business" of the SIG would be. For example, it's very clear to me > what the purpose and mission of a GSoC SIG would be, and why they would > meet > regularly. > > I don't think we need to carve up everything we do into SIGs for the > record, I > think there's a need for SIGs on specified "business" which requires a > group's > regular attention, but that doesn't mean everything fits into the model > IMHO. > > > If I'm misunderstanding or missing something about the mission for a > prospective Newcomer SIG, let me know. > > > > 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/95b47ce5-0965-4099-8fae-1cbc86d063a1%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
