Re: Discussion: Community Onboarding/Outreach and Advocacy SIGs

I would like to be a lead or if that is full, a volunteer > On Jan 14, 2019, at 2:24 PM, Liam Newman wrote: > > Marky, > > Are you saying you'd like to be one of the Leads for this SIG or just that > you want to be a member of it? > > -Liam > > On Tuesday, December 18, 2018 at 12:01:05

Re: Discussion: Community Onboarding/Outreach and Advocacy SIGs

Marky, Are you saying you'd like to be one of the Leads for this SIG or just that you want to be a member of it? -Liam On Tuesday, December 18, 2018 at 12:01:05 PM UTC-8, Marky Jackson wrote: > > I would like to volunteer > > On Dec 18, 2018, at 11:59 AM, Oleg Nenashev > wrote: > > I

Re: Discussion: Community Onboarding/Outreach and Advocacy SIGs

UPD: I managed to mess up the Gitter channel name. The new one is https://gitter.im/jenkinsci/advocacy-and-outreach-sig On Thursday, January 3, 2019 at 10:49:19 AM UTC+1, Oleg Nenashev wrote: > > We were unable to get more feedback regarding the SIG naming. In order to > unblock that, I change

Re: Discussion: Community Onboarding/Outreach and Advocacy SIGs

+1 from Rick On Thu, Jan 3, 2019 at 5:49 PM Oleg Nenashev wrote: > We were unable to get more feedback regarding the SIG naming. In order to > unblock that, I change my vote to "Advocacy and Outreach" which is a Top-1 > name in Liam's list. I believe we consider the name as decided then. > > I

Re: Discussion: Community Onboarding/Outreach and Advocacy SIGs

We were unable to get more feedback regarding the SIG naming. In order to unblock that, I change my vote to "Advocacy and Outreach" which is a Top-1 name in Liam's list. I believe we consider the name as decided then. I have created https://gitter.im/jenkinsci/community-and-outreach-sig so

Re: Discussion: Community Onboarding/Outreach and Advocacy SIGs

I would like to volunteer > On Dec 18, 2018, at 11:59 AM, Oleg Nenashev wrote: > > I noticed that I have forgot to respond to Liam's question about the SIG > leadership. > > As a separate question: Who are potential owners of the SIG(s)? > > Some candidates: > Oleg Nenashev > Tracy Miranda

Re: Discussion: Community Onboarding/Outreach and Advocacy SIGs

I noticed that I have forgot to respond to Liam's question about the SIG leadership. As a separate question: Who are potential owners of the SIG(s)? > > Some candidates: > >- Oleg Nenashev >- Tracy Miranda >- Liam Newman >- (your name here - any voluteers?) > > No volunteers

Re: Discussion: Community Onboarding/Outreach and Advocacy SIGs

Option 3 is my preference, but I am OK with options 1/2 as well On Tue, Dec 11, 2018 at 11:22 PM Liam Newman wrote: > Oleg, > I totally agree with how you described the SIG's relationship with > channels - there to help, not to specifically own/control the channels. > > As to naming: > >1.

Re: Discussion: Community Onboarding/Outreach and Advocacy SIGs

Oleg, I totally agree with how you described the SIG's relationship with channels - there to help, not to specifically own/control the channels. As to naming: 1. "Advocacy and Outreach" 2. "Outreach and Advocacy" 3. "Advocacy and Community Outreach" 4. "Community Outreach and

Re: Discussion: Community Onboarding/Outreach and Advocacy SIGs

In my opinion, anyone who wants to help advocacy the Jenkins could be part of the social media channels. Of course, the code of conduct is necessary. But how to running Twitter and WeChat or other social media channels. Maybe we could have a regular meeting to discuss. On Sun, Dec 9, 2018 at 3:16

Re: Discussion: Community Onboarding/Outreach and Advocacy SIGs

Hi, I do not think that such activity needs to be transferred unless Rick wants to do that. There are also many other outreach channels maintained my subprojects and other entities (e.g. Jenkins X, Evergreen, Jenkins RU, etc., etc.). My understanding is that: - The SIG is interested to help

Re: Discussion: Community Onboarding/Outreach and Advocacy SIGs

Curiously, would specific localization initiatives (e.g. Chinese Localization SIG's WeChat) be transferred to the broader umbrella of Outreach and Advocacy Mega-SIG? For example: I view Twitter and WeChat as comparable mechanisms for advocacy; both would have measurable metrics re: followers

Re: Discussion: Community Onboarding/Outreach and Advocacy SIGs

Hi Liam, I went through the docs few times, and yes there is no restrictions about creating nested SIGs. Then I am fine if we create a mega-SIG and then split it to sub-SIGs if/when needed. So the structures may be the following: - A SIG => subSIG (GSoC) - A SIG => subproject (e.g. if we

Re: Discussion: Community Onboarding/Outreach and Advocacy SIGs

"... related. I'd rather keep them together even with the scope being a bit broad." (don't know what happened there. CTRL-X misfire.) On Wednesday, December 5, 2018 at 10:55:41 AM UTC-8, Liam Newman wrote: > > Oleg, > I understand your point that Outreach and Advocacy feel like separate >

Re: Discussion: Community Onboarding/Outreach and Advocacy SIGs

Oleg, I understand your point that Outreach and Advocacy feel like separate areas, but they are closely related. However, I'd together even with the scope being a bit broad. I think that everyone in an Advocacy SIG would need to also be part of an Outreach SIG - IMO a core aspect of

Re: Discussion: Community Onboarding/Outreach and Advocacy SIGs

> > My preference for structure would be as 1 SIG (called Outreach or Outreach > & Advocacy) which is an umbrella for initiatives like GSoC, Outreachy, > Hacktoberfest. > I definitely agree with such scope if it is an "Outreach" SIG. But I do not see a lot of "Advocacy" in this scope TBH

Re: Discussion: Community Onboarding/Outreach and Advocacy SIGs

I'm also plus +1, Tracy. I'm a little concerned about over-broad scope. But was can always adjust it as we go along. On Monday, December 3, 2018 at 8:49:35 AM UTC-8, R Tyler Croy wrote: > > (replies inline) > > On Mon, 03 Dec 2018, Tracy Miranda wrote: > > > This sounds great. > > > > My

Re: Discussion: Community Onboarding/Outreach and Advocacy SIGs

(replies inline) On Mon, 03 Dec 2018, Tracy Miranda wrote: > This sounds great. > > My preference for structure would be as 1 SIG (called Outreach or Outreach > & Advocacy) which is an umbrella for initiatives like GSoC, Outreachy, > Hacktoberfest. > > GSoC, Outreachy should maintain their own

Re: Discussion: Community Onboarding/Outreach and Advocacy SIGs

This sounds great. My preference for structure would be as 1 SIG (called Outreach or Outreach & Advocacy) which is an umbrella for initiatives like GSoC, Outreachy, Hacktoberfest. GSoC, Outreachy should maintain their own channels i.e. gitter, etc so those who want to just focus on those can do

Re: Discussion: Community Onboarding/Outreach and Advocacy SIGs

I'd also be interested in this SIG. On Thu, Nov 29, 2018 at 8:26 PM arch wrote: > Collect the feedbacks from the contributors and users is important. Share > the questions and experience could let Jenkins community become stronger. > > On Fri, Nov 30, 2018 at 6:19 AM wrote: > >> I would very

Re: Discussion: Community Onboarding/Outreach and Advocacy SIGs

Collect the feedbacks from the contributors and users is important. Share the questions and experience could let Jenkins community become stronger. On Fri, Nov 30, 2018 at 6:19 AM wrote: > I would very much like to be a part of this and help in any way possible. > > > On Thursday, November 29,

Re: Discussion: Community Onboarding/Outreach and Advocacy SIGs

I would very much like to be a part of this and help in any way possible. On Thursday, November 29, 2018 at 2:12:56 PM UTC-8, Oleg Nenashev wrote: > > Hi all, > > I would like to follow-up on the discussion we had at the previous Jenkins > Governance meeting. There was a discussion >

Discussion: Community Onboarding/Outreach and Advocacy SIGs

Hi all, I would like to follow-up on the discussion we had at the previous Jenkins Governance meeting. There was a discussion about creating a new special interest group focused on the community