Discussion: Community Onboarding/Outreach and Advocacy SIGs

100 views
Skip to first unread message

Oleg Nenashev

unread,
Nov 29, 2018, 5:12:56 PM11/29/18
to JenkinsCI Developers

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 onboarding/outreach (or morphing the GSoC SIG into such SIG). There were comments from Liam, Kohsuke, Tracy, and other contributors. There was also a comment from Liam about creating an advocacy SIG. I would like to follow-up on my action item.


Background: Several months ago I have reached out to several contributors who are passionate about the community development. Originally my plan was to have a Community Health or Community Development SIG which would focus on the following topics:

  • Attracting and onboarding new individual and company contributors

  • Documentation for newbie contributors

  • Coordinating community outreach events: GSoC, Outreachy, Google Code-In, Hacktoberfest, Jenkins Online Meetups, JAMs, hackathons, etc.

  • Facilitating community activities (e.g. helping contributors with JEPs and SIGs)

  • Community Evangelism (Jenkins Ambassadors, etc.)

  • Infrastructure: Community metrics & Co, Hosting/Plugin adoption tooling


There was another discussion about creating a SIG for community outreach events only. We had a discussion of such plan at GSoC SIG meetings, and org admins and mentors said that such scope is too big for them, GSoC already consumes a lot of time. But they are fine with keeping GSoC as an independent sub-project (own meetings, mailing lists, etc.) which would be a part of a bigger interest group. This approach would be similar to the JCasC subproject which is a part of Cloud Native SIG.


Clearly there is interest in kicking-off a SIG (or SIGs) to focus on expanding and improving the Jenkins community. It could be a single SIG with multiple subprojects, or maybe a number of smaller SIGs focusing on different areas of the community work (e.g. Advocacy/Evangelism for involving experienced Jenkins contributors/users and Community Outreach for reaching out to new contributors). Or there could be other approaches.


I had a sync-up with Liam to discuss options, and we agreed to start a thread together so that we could get more feedback and agree on the approach going forward. Any feedback will be appreciated.


Thanks in advance,

Oleg


marky.r...@gmail.com

unread,
Nov 29, 2018, 5:19:37 PM11/29/18
to Jenkins Developers
I would very much like to be a part of this and help in any way possible.

arch

unread,
Nov 29, 2018, 9:26:24 PM11/29/18
to jenkin...@googlegroups.com
Collect the feedbacks from the contributors and users is important. Share the questions and experience could let Jenkins community become stronger.

--
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-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/cde7cad3-e6ed-491b-8dcf-1cae7316468b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Matt Sicker

unread,
Nov 30, 2018, 11:27:46 AM11/30/18
to jenkin...@googlegroups.com
I'd also be interested in this SIG.


For more options, visit https://groups.google.com/d/optout.


--
Matt Sicker
Software Engineer, CloudBees

Tracy Miranda

unread,
Dec 3, 2018, 9:31:54 AM12/3/18
to jenkin...@googlegroups.com
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 so. But then at the SIG level we cover more topics (as listed in the email) share best practices and foster wider collaboration across initiatives for those who would like to do so. 

Tracy

R. Tyler Croy

unread,
Dec 3, 2018, 11:49:35 AM12/3/18
to jenkin...@googlegroups.com
(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 channels i.e. gitter, etc so
> those who want to just focus on those can do so. But then at the SIG level
> we cover more topics (as listed in the email) share best practices and
> foster wider collaboration across initiatives for those who would like to
> do so.


This sounds good to me Tracy, +1


--
GitHub: https://github.com/rtyler

GPG Key ID: 0F2298A980EE31ACCA0A7825E5C92681BEF6CEA2
signature.asc

Liam Newman

unread,
Dec 3, 2018, 7:19:39 PM12/3/18
to Jenkins Developers
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. 

Oleg Nenashev

unread,
Dec 4, 2018, 2:03:16 AM12/4/18
to Jenkins Developers
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 (Wikipedia).
  1. We do not manage social media
  2. We do not work with Jenkins Ambassadors
  3. This SIG does not coordinate JAMs, JOMs and other similar events
  4. ... // whatever other stuff from the first message (scope is definitely bloated there)
Please correct me if I am wrong.

Liam, your proposal was to actually have an Advocacy SIG IIRC. If we go forward with the Outreach SIG, we still might create an Advocacy SIG. How do you see it?

Best regards,
Oleg

Liam Newman

unread,
Dec 5, 2018, 1:55:41 PM12/5/18
to Jenkins Developers
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 advocacy for Jenkins is outreach.  To some extent, I think calling the SIG "Advocacy and Outreach" is almost redundant - except that, for the sake of new user outreach it is important to specify "Outreach" in the name of the SIG. :) 

Reversing that, people that are interested in working on Outreach and new user experience will generally need to be involved in discussions around Advocacy. We have sub-channels (and SIGs) for some outreach projects already. 

Does anyone else have strong feeling either way? 

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

Thanks,
Liam N. 

Liam Newman

unread,
Dec 5, 2018, 1:58:49 PM12/5/18
to Jenkins Developers
"... related.  I'd rather keep them together even with the scope being a bit broad."  
(don't know what happened there. CTRL-X misfire.)

Oleg Nenashev

unread,
Dec 7, 2018, 7:08:54 PM12/7/18
to Jenkins Developers
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&O SIG => subSIG (GSoC)
  • A&O SIG => subproject (e.g. if we remove GSoC as a SIG)
  • A&O SIG => subSIG (GSoC) => subproject (GSoC)
My question then would be about the name. Would it be "Advocacy and Outreach"? I went through open-source project with SIGs, and there are not so many similar areas unfortunately (the most of projects have only technical SIGs). What I found:
Advocacy is not fully a part of that, but I have found many occurrences of "Advocacy and Community Outreach" and " Community Outreach and Advocacy" entries in the internet. If we are OK with the longer name, maybe it's a way to go.

Best regards,
Oleg



BR, Oleg

Lloyd Chang

unread,
Dec 8, 2018, 7:51:53 PM12/8/18
to Jenkins Developers
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 and impressions.

Oleg Nenashev

unread,
Dec 9, 2018, 2:16:25 AM12/9/18
to JenkinsCI Developers
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 others to create such channels (as a part of outreach effort). E.g. it can help to create accounts and to promote them in the community
  • The SIG does not claim ownership of the social media channels unless it is agreed on
Best regards,
Oleg

On Sun, Dec 9, 2018 at 1:52 AM Lloyd Chang <lloyd...@gmail.com> wrote:
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 and impressions.

--
You received this message because you are subscribed to a topic in the Google Groups "Jenkins Developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-dev/84vjWz_Ho1k/unsubscribe.
To unsubscribe from this group and all its topics, send an email to jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/4e219e41-f579-4316-a382-0c7cf72bd55c%40googlegroups.com.

arch

unread,
Dec 9, 2018, 4:41:28 AM12/9/18
to jenkin...@googlegroups.com
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.

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-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLCz0oyDmsKcmSz%2Biq9Sw0B6UQ%3DLqEdSYizYR8k-Uh4NuA%40mail.gmail.com.

Liam Newman

unread,
Dec 11, 2018, 5:22:36 PM12/11/18
to Jenkins Developers
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 Advocacy"

I've listed these in my order of preference, with my only -1 vote being #4.   Anyone else have an opinion? 

-L. 

Oleg Nenashev

unread,
Dec 12, 2018, 11:32:46 AM12/12/18
to JenkinsCI Developers
Option 3 is my preference, but I am OK with options 1/2 as well


Oleg Nenashev

unread,
Dec 18, 2018, 2:59:56 PM12/18/18
to Jenkins Developers
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 here so far (beyond the list by Liam). SIGs may actually multiple leaders to balance the workload and to have more capacity (see Roles in JEP-4). We did it for GSoC and Platform SIGs, and I believe it can work well here as well. My proposal would be to just start the SIG with multiple leaders (whomever is active in the Jenkins community && shows interest in it), and then we can adjust going forward.

P.S: Personally I am interested to participate in organizing this SIG, and I will be happy to commit some time to this effort. I will have a very limited availability over the next months due to personal reasons and GSoC, but I will try to help where I can.

Best regards,
Oleg
To unsubscribe from this group and all its topics, send an email to jenkinsci-dev+unsubscribe@googlegroups.com.

Marky Jackson

unread,
Dec 18, 2018, 3:01:05 PM12/18/18
to jenkin...@googlegroups.com
I would like to volunteer 

Oleg Nenashev

unread,
Jan 3, 2019, 4:49:19 AM1/3/19
to Jenkins Developers
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 that we can jump there and work on the details together.

BR, Oleg

Rick

unread,
Jan 3, 2019, 4:51:36 AM1/3/19
to Jenkins Developers

Oleg Nenashev

unread,
Jan 3, 2019, 4:54:25 AM1/3/19
to Jenkins Developers
UPD: I managed to mess up the Gitter channel name. The new one is https://gitter.im/jenkinsci/advocacy-and-outreach-sig

Liam Newman

unread,
Jan 14, 2019, 5:24:31 PM1/14/19
to Jenkins Developers
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 

Marky Jackson

unread,
Jan 14, 2019, 5:27:40 PM1/14/19
to jenkin...@googlegroups.com
I would like to be a lead or if that is full, a volunteer

Reply all
Reply to author
Forward
0 new messages