Re: Request for comments: Special Interest Groups (SIGs) for the Jenkins project

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 and Remoting over Message Queue/Bus

Re: Request for comments: Special Interest Groups (SIGs) for the Jenkins project

(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

Re: Request for comments: Special Interest Groups (SIGs) for the Jenkins project

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

Re: Request for comments: Special Interest Groups (SIGs) for the Jenkins project

(replies inline) On Wed, 11 Apr 2018, Ewelina Wilkosz wrote: > 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

Re: Request for comments: Special Interest Groups (SIGs) for the Jenkins project

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

Re: Request for comments: Special Interest Groups (SIGs) for the Jenkins project

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

Re: Request for comments: Special Interest Groups (SIGs) for the Jenkins project

2018-04-11 8:50 GMT+02:00 Ewelina Wilkosz : > 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

Re: Request for comments: Special Interest Groups (SIGs) for the Jenkins project

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

Re: Request for comments: Special Interest Groups (SIGs) for the Jenkins project

(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) >

Re: Request for comments: Special Interest Groups (SIGs) for the Jenkins project

> On 26. Mar 2018, at 17:13, R. Tyler Croy wrote: > > I'm curious why you assume that the security SIG would be broader in scope > than > the present day CERT? Well, it _could_ be broader in scope. It certainly could be more open. Security isn't just finding and fixing

Re: Request for comments: Special Interest Groups (SIGs) for the Jenkins project

(replies inline) On Mon, 26 Mar 2018, Daniel Beck wrote: > > > On 22. Mar 2018, at 22:04, R. Tyler Croy wrote: > > > > 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

Re: Request for comments: Special Interest Groups (SIGs) for the Jenkins project

> On 22. Mar 2018, at 22:04, R. Tyler Croy wrote: > > 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:

Re: Request for comments: Special Interest Groups (SIGs) for the Jenkins project

+1 to that Baptiste, let's try to make it in a way that 1. will not isolate us, but "keep us together" 2. will make it easy for us to keep the track and easy to say without providing ideas, but for now I just wanted to highlight I believe those two are important things to keep in mind while

Re: Request for comments: Special Interest Groups (SIGs) for the Jenkins project

I think this is a good initiative to keep us moving forward. As the Jenkins Project keeps growing, we definitely have various people with various interests, and anything that can help people contribute without feeling they're getting spammed by dozens of "unrelated" emails seems a good idea. I'm

Re: Request for comments: Special Interest Groups (SIGs) for the Jenkins project

I think the materialization of SIGs would be a great addition to the community, thanks Tyler for the write up I am working on draft JEPs to be proposed regarding "cloud native": external storage, external logging,... you'll be reading more from me in the following weeks :) On Thu, Mar 22, 2018,

Re: Request for comments: Special Interest Groups (SIGs) for the Jenkins project

The proposal looks good to me though it overlaps with "teams" a bit. In GSoC we already use the channels and have regular meetings there. Regarding Youtube, it would be great to extend the number of participants beyond the current number (10) and to give "subject leaders" a permission to run

Re: Request for comments: Special Interest Groups (SIGs) for the Jenkins project

(replies inline) On Thu, 22 Mar 2018, Jesse Glick wrote: > On Thu, Mar 22, 2018 at 5:04 PM, R. Tyler Croy wrote: > > Regularly scheduled and published meetings. I can easily imagine re-using > > #jenkins-meeting or our public YouTube channel for regularly scheduling > > and

Re: Request for comments: Special Interest Groups (SIGs) for the Jenkins project

On Thu, Mar 22, 2018 at 5:04 PM, R. Tyler Croy wrote: > 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. gitter.im feels

Request for comments: Special Interest Groups (SIGs) for the Jenkins project

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) A full list of the Kubernetes