(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/20180417215803.GP1836%40grape.lasagna.io. For more options, visit https://groups.google.com/d/optout.
signature.asc
Description: PGP signature
