>
> 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 
<https://en.wikipedia.org/wiki/Advocacy>).

   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
 
On Tuesday, December 4, 2018 at 1:19:39 AM UTC+1, Liam Newman wrote:
>
> 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 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 
>>
>

-- 
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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/91747fb6-f227-4bdb-b60a-a5a4d7a565e5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to