+1 from Rick On Thu, Jan 3, 2019 at 5:49 PM Oleg Nenashev <[email protected]> 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 have created https://gitter.im/jenkinsci/community-and-outreach-sig so > that we can jump there and work on the details together. > > BR, Oleg > > > > On Tuesday, December 18, 2018 at 9:01:05 PM UTC+1, Marky Jackson wrote: >> >> I would like to volunteer >> >> On Dec 18, 2018, at 11:59 AM, Oleg Nenashev <[email protected]> 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 >>> - 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 <https://github.com/jenkinsci/jep/tree/master/jep/4#roles>). >> 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 >> >> >> On Wednesday, December 12, 2018 at 5:32:46 PM UTC+1, Oleg Nenashev wrote: >>> >>> 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 <[email protected]> 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. "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. >>>> >>>> On Sunday, December 9, 2018 at 1:41:28 AM UTC-8, Rick wrote: >>>>> >>>>> 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 PM Oleg Nenashev <[email protected]> >>>>> wrote: >>>>> >>>>>> 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 <[email protected]> >>>>>> 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 >>>>>>> [email protected]. >>>>>> >>>>>> >>>>>>> To view this discussion on the web visit >>>>>>> https://groups.google.com/d/msgid/jenkinsci-dev/4e219e41-f579-4316-a382-0c7cf72bd55c%40googlegroups.com >>>>>>> <https://groups.google.com/d/msgid/jenkinsci-dev/4e219e41-f579-4316-a382-0c7cf72bd55c%40googlegroups.com?utm_medium=email&utm_source=footer> >>>>>>> . >>>>>>> For more options, visit https://groups.google.com/d/optout. >>>>>>> >>>>>> >>>>>> -- >>>>>> 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/CAPfivLCz0oyDmsKcmSz%2Biq9Sw0B6UQ%3DLqEdSYizYR8k-Uh4NuA%40mail.gmail.com >>>>>> <https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLCz0oyDmsKcmSz%2Biq9Sw0B6UQ%3DLqEdSYizYR8k-Uh4NuA%40mail.gmail.com?utm_medium=email&utm_source=footer> >>>>>> . >>>>>> For more options, visit https://groups.google.com/d/optout. >>>>>> >>>>> >>>> -- >>>> 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 >>>> [email protected]. >>>> To view this discussion on the web visit >>>> https://groups.google.com/d/msgid/jenkinsci-dev/43bbbede-6538-482f-b49c-9ce207ab8cf3%40googlegroups.com >>>> <https://groups.google.com/d/msgid/jenkinsci-dev/43bbbede-6538-482f-b49c-9ce207ab8cf3%40googlegroups.com?utm_medium=email&utm_source=footer> >>>> . >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>> >> -- >> 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 >> [email protected]. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/jenkinsci-dev/28e6bac5-e5bf-4eef-95cf-1c72dae990f4%40googlegroups.com >> <https://groups.google.com/d/msgid/jenkinsci-dev/28e6bac5-e5bf-4eef-95cf-1c72dae990f4%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> >> >> -- > 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/7f993144-8f38-47d1-8735-f63ad65abc76%40googlegroups.com > <https://groups.google.com/d/msgid/jenkinsci-dev/7f993144-8f38-47d1-8735-f63ad65abc76%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- https://github.com/LinuxSuRen -- 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/CAMM7nTHSCwwee3O3SdvFqUzsGqVr7obzKbbY7C3tHeUXwKgScw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
