Re: Discussion: Community Onboarding/Outreach and Advocacy SIGs

[arch]

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  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  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-dev+unsubscr...@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
>> 
>> .
>> 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 jenkinsci-dev+unsubscr...@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
> 
> .
> 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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAMM7nTFBM%2BDojHe6Y9AvR-J95SuFqs1vJofQABZCg5tEva_LGg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: GSoC proposal about the Multi-branch for Gitlab

[arch]

Agree with this.

On Tue, Dec 4, 2018 at 8:19 PM Oleg Nenashev  wrote:

> Hi Rick,
>
> Thanks for starting this discussion! I think it is good to be published as
> a draft project idea on jenkins.io.
> I suggest to also bring up this topic in the Pipeline Authoring SIG (e.g.
> just adding it to CC).
>
> Best regards,
> Oleg
>
> On Tuesday, December 4, 2018 at 2:52:54 AM UTC+1, Rick wrote:
>>
>> hi:
>>
>> I made a proposal about the Multi-branch support for Gitlab.
>>
>> Here is the doc link.
>>
>> https://docs.google.com/document/d/1Gqz4LyU5sw6I50OdAVsQSW_WPNDlvXg4Ic9NdcYj4Ts/edit?usp=sharing
>>
>> Any comments are welcome.
>>
>> Thanks,
>> Rick
>>
> --
> 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-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/d922ea0c-b372-4da2-b85f-7616c8fd6d95%40googlegroups.com
> 
> .
> 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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAMM7nTEAqPePA29rcwzArnTKH4ndTrJhieNbabhX9yqhk_Sb5Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

GSoC proposal about the Multi-branch for Gitlab

[arch]

hi:

I made a proposal about the Multi-branch support for Gitlab.

Here is the doc link.
https://docs.google.com/document/d/1Gqz4LyU5sw6I50OdAVsQSW_WPNDlvXg4Ic9NdcYj4Ts/edit?usp=sharing

Any comments are welcome.

Thanks,
Rick

-- 
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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAMM7nTEkUq40xzVN3UudX0-nomwwVjWDeU0Kfz5dmz0K258d%3Dg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Discussion: Community Onboarding/Outreach and Advocacy SIGs

[arch]

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, 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
>> 
>> 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
>>
>>
>> --
> 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-dev+unsubscr...@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.
>

-- 
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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAMM7nTGAxP33vdJv9_fga%2Bi6%3DMuvvEC50B2dWzkq%3Di1xqcqJbA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Request cn.jenkins.io write permission

[arch]

No negative response, I'll send the invite.

On Fri, Nov 16, 2018 at 12:20 PM arch  wrote:

> +1
>
> On Fri, Nov 16, 2018 at 11:53 AM QIANG LAIN  wrote:
>
>> Hi
>> There are only one Chinese speaker has the write permission in the team,
>> so we need two person at least to review and merge the PR timely.
>>
>> As a member in Chinese-localization-sig, i would like to request the
>> write permission in this repo.
>>
>> Github: xuesea
>>
>> Thanks
>>
>> --
>> 您收到此邮件是因为您订阅了Google网上论坛上的“jenkins-chinese-localization-sig”群组。
>> 要退订此群组并停止接收此群组的电子邮件，请发送电子邮件到
>> jenkins-chinese-localization-sig+unsubscr...@googlegroups.com。
>> 要发帖到此群组，请发送电子邮件至jenkins-chinese-localization-...@googlegroups.com。
>> 要在网络上查看此讨论，请访问
>> https://groups.google.com/d/msgid/jenkins-chinese-localization-sig/CAKiPr%2BGr9LpYp5tdg6cJrLZ0pd4AvodrJFQqx3prLi%3D9L8KmHg%40mail.gmail.com
>> <https://groups.google.com/d/msgid/jenkins-chinese-localization-sig/CAKiPr%2BGr9LpYp5tdg6cJrLZ0pd4AvodrJFQqx3prLi%3D9L8KmHg%40mail.gmail.com?utm_medium=email_source=footer>
>> 。
>> 要查看更多选项，请访问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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAMM7nTGcEK33V%3DFvqJEv58gXw73%3DekZ8yyYNhuTUr_tcLf38aw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Request cn.jenkins.io write permission

[arch]

+1

On Fri, Nov 16, 2018 at 11:53 AM QIANG LAIN  wrote:

> Hi
> There are only one Chinese speaker has the write permission in the team,
> so we need two person at least to review and merge the PR timely.
>
> As a member in Chinese-localization-sig, i would like to request the write
> permission in this repo.
>
> Github: xuesea
>
> Thanks
>
> --
> 您收到此邮件是因为您订阅了Google网上论坛上的“jenkins-chinese-localization-sig”群组。
> 要退订此群组并停止接收此群组的电子邮件，请发送电子邮件到
> jenkins-chinese-localization-sig+unsubscr...@googlegroups.com。
> 要发帖到此群组，请发送电子邮件至jenkins-chinese-localization-...@googlegroups.com。
> 要在网络上查看此讨论，请访问
> https://groups.google.com/d/msgid/jenkins-chinese-localization-sig/CAKiPr%2BGr9LpYp5tdg6cJrLZ0pd4AvodrJFQqx3prLi%3D9L8KmHg%40mail.gmail.com
> 
> 。
> 要查看更多选项，请访问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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAMM7nTH6SXj6%3DjyA7poM4McJrqWRQ-7%3DhgABvM86zXg8iOpT4Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Localization plugins: Where do we go from here?

[arch]

How about adding a method to indicate target language
in LocalizationContributor. So we could get a list of all language plugins.

On Mon, Nov 12, 2018 at 5:42 AM Daniel Beck  wrote:

>
>
> > On 11. Nov 2018, at 11:41, arch  wrote:
> >
> > I prefer option C. I can try to do this.
>
> As I wrote in Gitter, I had something in progress locally already, and
> finished this up to a reasonable prototype state.
>
> It seems to work in local development, but has undergone minimal testing
> so far. If you have time, would be great if you could look into it and tell
> me what you think.
>
> https://github.com/kohsuke/localizer/pull/16
> https://github.com/jenkinsci/jenkins/pull/3729
> https://github.com/daniel-beck/localization-support-plugin
> https://github.com/jenkinsci/localization-zh-cn-plugin/pull/31
>
>

-- 
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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAMM7nTE35U79f_Bs-kndyECw1Gd-FOhurL7ReCLh8PqJO%2BNhJw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Localization plugins: Where do we go from here?

[arch]

I prefer option C. I can try to do this.

In order to supplement JPE-216. I hope to get more feedback about the
languages separation.

Thank Daniel for your efforts.

On Sun, Nov 11, 2018 at 6:23 PM Daniel Beck  wrote:

> Hi everyone,
>
> I looked at bit into the current state of separate localization plugins
> (JEP-216[1]) this weekend.
>
> Currently, there is one such plugin, localization-zh-cn[2]. It includes
> both Simplified Chinese translations, as well as supporting infrastructure
> to enable their use, IIUC partly/mostly based on how the Translation
> Assistance Plugin could be used to load local user-provided translations.
>
> The plugin supports two of the three major localization 'types' (views and
> Stapler resources) and I'm currently looking into adding support for the
> third[3], localizer/Messages.properties.
>
>
> AFAIUI, we have two options how to continue from here to support further
> externalized localizations, and I'm not sure these have been properly
> evaluated so far (corrections welcome).
>
> Option A:
> Rename the plugin from `localization-zh-cn` to `localization` and add
> other languages to this plugin. Some supporting infra code will need to be
> adapted to make this work; right now `_zh_CN` is partly hardcoded. Will
> require some additional governance to support many additional contributors
> to this one plugin. Might result in many more releases than are needed for
> a specific user group, or changes not being published in a timely manner.
>
> Option B:
> Duplicate all of the support infrastructure from localization-zh-cn into,
> for example, localization-de, and maintain it twice. I'm not even sure it'd
> work based on the code in localization-zh-cn that deals with identifying
> conflicting plugins[4].
>
> Option C:
> Move the supporting infrastructure from `localization-zh-cn` into a new
> `localization-support` plugin and generalize it to work for any locale. Add
> a dependency from localization-zh-cn to localization-support.
> `localization-support` is expected to remain fairly unchanging, while
> `localization-zh-cn` (and any other specific localization plugin) would be
> regularly updated to include new translations.
> It adds an additional (expected to be fairly stagnant) plugin, plus one
> plugin per locale, but these individual plugins would only receive updates
> when there's actually something relevant for their user group.
>
> Options B and C also make more sense for the 'Languages' category in the
> setup wizard (which would otherwise be exactly one plugin).
>
> IMO, Option C is preferable, but it requires some refactoring to pull out
> supporting infrastructure from `localization-zh-cn`, but it seems to be
> most consistent with how this has been set up.
>
> WDYT?
>
> Daniel
>
> 1: https://github.com/jenkinsci/jep/tree/master/jep/216 and
> https://github.com/jenkinsci/jep/pull/191
> 2: https://github.com/jenkinsci/localization-zh-cn-plugin
> 3: https://github.com/kohsuke/localizer/pull/16 and
> https://github.com/jenkinsci/jenkins/pull/3729
> 4:
> https://github.com/jenkinsci/localization-zh-cn-plugin/blob/master/src/main/java/jenkins/plugins/localization/LocalizationMonitor.java

-- 
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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAMM7nTFcdA4-yEhyJ_k99aOytGSOEq6%3Dbr%3D4orCtm1ru0%2BB5Vg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Trademark sublicense request: Jenkins WeChat Account in China

[arch]

Thanks for everyone. Once the email was created I'll continue this.

On Sat, Nov 10, 2018 at 7:17 AM Kohsuke Kawaguchi  wrote:

> The change was merged, so the content is accessible from
> http://jenkins.io/wechat.pdf
>
> On Fri, Nov 9, 2018 at 7:01 AM Kohsuke Kawaguchi  wrote:
>
>> Signed letter attached.
>>
>> I've also asked this be added under jenkins.io here,
>> https://github.com/jenkins-infra/jenkins.io/pull/1878 in the hope that
>> this helps reinforce the chain of trust.
>>
>>
>> On Fri, Nov 9, 2018 at 3:41 AM arch  wrote:
>>
>>> Hi, KK, Olivier
>>>
>>> I'll make a presentation about Jenkins X in KubeCon CloudNativeCon
>>> China. I wish I could introduce Jenkins WeChat to other people. So if you
>>> are free to help me register Jenkins WeChat subscription account. Here is
>>> the register link https://mp.weixin.qq.com/?lang=en_US.
>>>
>>> Thanks
>>> Rick (Zhao Xiaojie)
>>>
>>>
>>> On Thu, Nov 8, 2018 at 10:37 AM arch  wrote:
>>>
>>>> I agree with the ideas to use wechat-ad...@list.jenkins-ci.org. Please
>>>> let me in once you created it. And I think the letter is very important to
>>>> me and Jenkins Chinese Community. This could let our people know that the
>>>> Jenkins Community think the WeChat subscription account is valuable and
>>>> important.
>>>>
>>>> About your suggestion. I'm ok with that. I believe that we all want to
>>>> build a great Jenkins Chinese Community. It's no matter who will create the
>>>> account.
>>>>
>>>> In addition, I have another request. I wonder if you (KK, Olivier, Oleg)
>>>> could write a welcome or introduce text about the WeChat account. First,
>>>> it's good to let Chinese Jenkins fans know you. Second, I think it's good
>>>> for getting more focus from my people.
>>>>
>>>> Good wish.
>>>> Rick (Zhao Xiaojie)
>>>>
>>>> On Thu, Nov 8, 2018 at 3:17 AM Kohsuke Kawaguchi 
>>>> wrote:
>>>>
>>>>> This is just a thought, but alternatively, if it's easier, we can ask
>>>>> Olivier (or I) to create a WeChat subscription account, deal with whatever
>>>>> authorization process it needs, and add your personal WeChat account as 
>>>>> the
>>>>> operator of the Jenkins subscription account.
>>>>>
>>>>> That might reduce the roundtrips?
>>>>>
>>>>> On Wed, Nov 7, 2018 at 11:13 AM Kohsuke Kawaguchi 
>>>>> wrote:
>>>>>
>>>>>> So in the meeting today we reaffirmed that this isn't the case for
>>>>>> trademark sublicensing. I took the action to write a signed letter, as 
>>>>>> per
>>>>>> your request, explaining that you are acting on behalf of the rightful
>>>>>> owner of the trademark.
>>>>>>
>>>>>> I wrote a letter, but the printer at the office is acting out so I
>>>>>> can't provide you a signed PDF right now. I'll do that once I get back 
>>>>>> home
>>>>>> later today.
>>>>>>
>>>>>> Thanks Rick for clarifying that once created, the subscription
>>>>>> account can be operated by multiple personal accounts. It does help with
>>>>>> the bus factor <https://en.wikipedia.org/wiki/Bus_factor> problem,
>>>>>> we don't have to deal with a shared secret this way.
>>>>>>
>>>>>> But I still agree with Olivier, in that I think it's important that
>>>>>> the email address tied to the community be used to create an account:
>>>>>> wechat-ad...@list.jenkins-ci.org. This isn't meant to exclude you
>>>>>> from anything, slow you down, or distrust, but as I understand it, it's a
>>>>>> part of the hygiene to ensure the chain of control is connected all the 
>>>>>> way
>>>>>> up to SPI.
>>>>>>
>>>>>> On Tue, Nov 6, 2018 at 7:26 PM arch  wrote:
>>>>>>
>>>>>>> The service account must control by an organization or a company.
>>>>>>> So I'm going to register the subscription account.
>>>>>>>
>>>>>>> OK, allow me to introduce more details about the WeChat. There are 5
>>>>>>> people could running the subscription accoun

Re: Trademark sublicense request: Jenkins WeChat Account in China

[arch]

Hi, KK, Olivier

I'll make a presentation about Jenkins X in KubeCon CloudNativeCon China. I
wish I could introduce Jenkins WeChat to other people. So if you are free
to help me register Jenkins WeChat subscription account. Here is the
register link https://mp.weixin.qq.com/?lang=en_US.

Thanks
Rick (Zhao Xiaojie)

On Thu, Nov 8, 2018 at 10:37 AM arch  wrote:

> I agree with the ideas to use wechat-ad...@list.jenkins-ci.org. Please
> let me in once you created it. And I think the letter is very important to
> me and Jenkins Chinese Community. This could let our people know that the
> Jenkins Community think the WeChat subscription account is valuable and
> important.
>
> About your suggestion. I'm ok with that. I believe that we all want to
> build a great Jenkins Chinese Community. It's no matter who will create the
> account.
>
> In addition, I have another request. I wonder if you (KK, Olivier, Oleg)
> could write a welcome or introduce text about the WeChat account. First,
> it's good to let Chinese Jenkins fans know you. Second, I think it's good
> for getting more focus from my people.
>
> Good wish.
> Rick (Zhao Xiaojie)
>
> On Thu, Nov 8, 2018 at 3:17 AM Kohsuke Kawaguchi  wrote:
>
>> This is just a thought, but alternatively, if it's easier, we can ask
>> Olivier (or I) to create a WeChat subscription account, deal with whatever
>> authorization process it needs, and add your personal WeChat account as the
>> operator of the Jenkins subscription account.
>>
>> That might reduce the roundtrips?
>>
>> On Wed, Nov 7, 2018 at 11:13 AM Kohsuke Kawaguchi  wrote:
>>
>>> So in the meeting today we reaffirmed that this isn't the case for
>>> trademark sublicensing. I took the action to write a signed letter, as per
>>> your request, explaining that you are acting on behalf of the rightful
>>> owner of the trademark.
>>>
>>> I wrote a letter, but the printer at the office is acting out so I can't
>>> provide you a signed PDF right now. I'll do that once I get back home later
>>> today.
>>>
>>> Thanks Rick for clarifying that once created, the subscription account
>>> can be operated by multiple personal accounts. It does help with the bus
>>> factor <https://en.wikipedia.org/wiki/Bus_factor> problem, we don't
>>> have to deal with a shared secret this way.
>>>
>>> But I still agree with Olivier, in that I think it's important that the
>>> email address tied to the community be used to create an account: wechat
>>> -ad...@list.jenkins-ci.org. This isn't meant to exclude you from
>>> anything, slow you down, or distrust, but as I understand it, it's a part
>>> of the hygiene to ensure the chain of control is connected all the way up
>>> to SPI.
>>>
>>> On Tue, Nov 6, 2018 at 7:26 PM arch  wrote:
>>>
>>>> The service account must control by an organization or a company. So
>>>> I'm going to register the subscription account.
>>>>
>>>> OK, allow me to introduce more details about the WeChat. There are 5
>>>> people could running the subscription account by a long term. And there are
>>>> 20 people could running the account by a short-term (one month). So don't
>>>> be worry about one person could block.
>>>>
>>>> Another situation is that everyone just could have one WeChat
>>>> account(personal account). He must bind his bank card, phone number. And
>>>> I'll be the initial person to running this. We will create a process to
>>>> share this platform.
>>>>
>>>> Yes, my idea is that create a repository in jenkins-infra. Put all
>>>> articles on that. Every contributor could create a PR to publish the
>>>> article. And the good news is that WeChat supports web api. Finally, we
>>>> will develop a program to publish these articles.
>>>>
>>>>
>>>>> --
>>>>> 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-dev+unsubscr...@googlegroups.com.
>>>>> To view this discussion on the web visit
>>>>> https://groups.google.com/d/msgid/jenkinsci-dev/1541533813.954363.1567849448.586ABBE0%40webmail.messagingengine.com
>>>>> <https://groups.google.com/d/msgid/jenkinsci-dev/1541533813.954363.1567849448.586ABBE0%40webmail.messagingengine.com?utm_medium=email_source=footer>
>>>>&g

Re: Jenkins twitter performance for October

[arch]

Glad to hear this. I think if we could share some information or messages
between Twitter and WeChat that will be great!

On Fri, Nov 9, 2018 at 5:32 PM Tracy Miranda  wrote:

> Hi all,
>
> I'd like to share some highlights for *October* from the Jenkins Twitter
> accounts.
>
> @jenkinsci:
> - Upto 35K followers
> - The most popular tweet
>  was the one
> launching #Hacktoberfest , thanks for the retweets all!
>
> @jenkinsxio
> - Now has 1161 followers
> - Tweet impressions were up 275% (from 6k to 25k)
> - This was the most popular tweet.
> 
>
> There was also lots of good content out there to retweet, so thanks all!
>
> The aim is to continually improve our process as per JEP-10
> , so
> will keep taking steps in that direction. Additionally for tweet ideas/rt
> suggestions please let me know in the jenkins-community
>  gitter chat.
>
> Regards,
> Tracy
>
> --
> 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-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/CACTaz6rER6tKoicq4Kgw6dRN0SsqtVxpBTJxRiXp_qFL61k-cg%40mail.gmail.com
> 
> .
> 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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAMM7nTHDO24_Y-hmYOj3FGg0vJYK8Fr3Sbs6DsPfOHNFnkz%3Diw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Trademark sublicense request: Jenkins WeChat Account in China

[arch]

I agree with the ideas to use wechat-ad...@list.jenkins-ci.org. Please let
me in once you created it. And I think the letter is very important to me
and Jenkins Chinese Community. This could let our people know that the
Jenkins Community think the WeChat subscription account is valuable and
important.

About your suggestion. I'm ok with that. I believe that we all want to
build a great Jenkins Chinese Community. It's no matter who will create the
account.

In addition, I have another request. I wonder if you (KK, Olivier, Oleg)
could write a welcome or introduce text about the WeChat account. First,
it's good to let Chinese Jenkins fans know you. Second, I think it's good
for getting more focus from my people.

Good wish.
Rick (Zhao Xiaojie)

On Thu, Nov 8, 2018 at 3:17 AM Kohsuke Kawaguchi  wrote:

> This is just a thought, but alternatively, if it's easier, we can ask
> Olivier (or I) to create a WeChat subscription account, deal with whatever
> authorization process it needs, and add your personal WeChat account as the
> operator of the Jenkins subscription account.
>
> That might reduce the roundtrips?
>
> On Wed, Nov 7, 2018 at 11:13 AM Kohsuke Kawaguchi  wrote:
>
>> So in the meeting today we reaffirmed that this isn't the case for
>> trademark sublicensing. I took the action to write a signed letter, as per
>> your request, explaining that you are acting on behalf of the rightful
>> owner of the trademark.
>>
>> I wrote a letter, but the printer at the office is acting out so I can't
>> provide you a signed PDF right now. I'll do that once I get back home later
>> today.
>>
>> Thanks Rick for clarifying that once created, the subscription account
>> can be operated by multiple personal accounts. It does help with the bus
>> factor <https://en.wikipedia.org/wiki/Bus_factor> problem, we don't have
>> to deal with a shared secret this way.
>>
>> But I still agree with Olivier, in that I think it's important that the
>> email address tied to the community be used to create an account: wechat
>> -ad...@list.jenkins-ci.org. This isn't meant to exclude you from
>> anything, slow you down, or distrust, but as I understand it, it's a part
>> of the hygiene to ensure the chain of control is connected all the way up
>> to SPI.
>>
>> On Tue, Nov 6, 2018 at 7:26 PM arch  wrote:
>>
>>> The service account must control by an organization or a company. So
>>> I'm going to register the subscription account.
>>>
>>> OK, allow me to introduce more details about the WeChat. There are 5
>>> people could running the subscription account by a long term. And there are
>>> 20 people could running the account by a short-term (one month). So don't
>>> be worry about one person could block.
>>>
>>> Another situation is that everyone just could have one WeChat
>>> account(personal account). He must bind his bank card, phone number. And
>>> I'll be the initial person to running this. We will create a process to
>>> share this platform.
>>>
>>> Yes, my idea is that create a repository in jenkins-infra. Put all
>>> articles on that. Every contributor could create a PR to publish the
>>> article. And the good news is that WeChat supports web api. Finally, we
>>> will develop a program to publish these articles.
>>>
>>>
>>>> --
>>>> 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-dev+unsubscr...@googlegroups.com.
>>>> To view this discussion on the web visit
>>>> https://groups.google.com/d/msgid/jenkinsci-dev/1541533813.954363.1567849448.586ABBE0%40webmail.messagingengine.com
>>>> <https://groups.google.com/d/msgid/jenkinsci-dev/1541533813.954363.1567849448.586ABBE0%40webmail.messagingengine.com?utm_medium=email_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 jenkinsci-dev+unsubscr...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/jenkinsci-dev/CAMM7nTFfAF%3Ds8USwNSB-ncU4rCE98eNh%3D6sCZNH9MNeZcFjgCg%40mail.gmail.com
>>> <https://groups.google.com/d/msgid/jenkinsci-dev/CAMM7nTFfAF%3Ds8USwNSB-ncU4rCE98eN

Re: Trademark sublicense request: Jenkins WeChat Account in China

[arch]

The service account must control by an organization or a company. So I'm
going to register the subscription account.

OK, allow me to introduce more details about the WeChat. There are 5 people
could running the subscription account by a long term. And there are 20
people could running the account by a short-term (one month). So don't be
worry about one person could block.

Another situation is that everyone just could have one WeChat
account(personal account). He must bind his bank card, phone number. And
I'll be the initial person to running this. We will create a process to
share this platform.

Yes, my idea is that create a repository in jenkins-infra. Put all articles
on that. Every contributor could create a PR to publish the article. And
the good news is that WeChat supports web api. Finally, we will develop a
program to publish these articles.

>
> --
> 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-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/1541533813.954363.1567849448.586ABBE0%40webmail.messagingengine.com
> 
> .
> 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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAMM7nTFfAF%3Ds8USwNSB-ncU4rCE98eNh%3D6sCZNH9MNeZcFjgCg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Trademark sublicense request: Jenkins WeChat Account in China

[arch]

I would expect a confirmation letter. And It's better to record this in
wiki.

On Tue, Nov 6, 2018 at 6:33 PM Oleg Nenashev  wrote:

> WeChat platform said I need submit the permission of Jenkins trademark.
>>
>
> Then it would be better to get approval for it tomorrow. It is already in
> the agenda for the Governance meeting, so I do not expect it to be a
> problem to get approved.
> What is the form of approval you need to get? Would a link to
> https://wiki.jenkins.io/display/JENKINS/Approved+Trademark+Usage do the
> job? Or do you need a kind of confirmation letter?
>
> BR, Oleg
>
>
>
> On Tue, Nov 6, 2018 at 10:11 AM arch  wrote:
>
>> There is still have a problem with the trademark. I want to use Jenkins
>> as the name of WeChat subscription account name. Do I still need to request
>> the trademark? Actually, I already met the issue. WeChat platform said I
>> need submit the permission of Jenkins trademark.
>>
>> On Tue, Nov 6, 2018 at 10:26 AM arch  wrote:
>>
>>> Yes, I prefer the service account at first. But this kind of account
>>> must base on a company entity. For now, the subscription account is ok.
>>>
>>> On Mon, Nov 5, 2018 at 9:10 PM Oleg Nenashev 
>>> wrote:
>>>
>>>> That said, where I disagree with Oleg in the email thread linked is
>>>>> that I don't think it's right that Alauda is tied to this account, or any
>>>>> other participant for that matter... I think it's great that Xiaojie is
>>>>> stepping up to the plate. All the powers to him!!  IIUC, that's
>>>>> "subscription account" and not "service account."
>>>>
>>>>
>>>> My suggestion was based on Rick's preference towards a "service
>>>> account" in the thread.
>>>> Personally I do not have any preference.
>>>>
>>>> I want to register the account as an organization. But I need an
>>>>> organization name and code. Oleg told me that there is not a real entity
>>>>> for Jenkins. I also do some homework about this. So my advice is that we
>>>>> register this account as an individual
>>>>>
>>>> Perfectly fine with me
>>>>
>>>> Best regards,
>>>> Oleg
>>>>
>>>>
>>>> On Sunday, November 4, 2018 at 6:39:37 AM UTC+3, Rick wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> I totally agree with the idea that Jenkins WeChat running under the
>>>>> community organization. It's fair for every contributor. My dream is that
>>>>> let more and more people join Jenkins party. But I met some situations
>>>>> during the process.
>>>>>
>>>>> First, I probably must use a personal email to register. I need to
>>>>> receive a verification code to complete the form. But the contact email
>>>>> could be jenkins-chinese-localization-...@googlegroups.com.
>>>>>
>>>>> Second, the subscription account may be the best solution. There are
>>>>> five types of WeChat Account Entity. They are government, media, company,
>>>>> individual and other organizations. I want to register the account as an
>>>>> organization. But I need an organization name and code. Oleg told me that
>>>>> there is not a real entity for Jenkins. I also do some homework about 
>>>>> this.
>>>>> So my advice is that we register this account as an individual.  More
>>>>> detail page is here
>>>>> https://mp.weixin.qq.com/acct/contractorpage?action=showreg=3=zh_CN
>>>>> .
>>>>>
>>>>> It’s really great to get your support. I want to take the initiative.
>>>>> And I think the Chinese Localization SIG team members are happy to help 
>>>>> the
>>>>> Jenkins WeChat. We have a regular video meeting. Every contributor could
>>>>> get the meeting time in the calendar
>>>>> https://jenkins.io/event-calendar/. This’s open for everyone.
>>>>>
>>>>> BTW, if there is no other concerns or questions. Once you think ok
>>>>> with my solution and advice, then I will begin my job.
>>>>>
>>>>>
>>>>> Best,
>>>>>
>>>>> Rick (Zhao Xiaojie)
>>>>>
>>>> On Fri, Nov 2, 2018 at 3:22 AM Kohsuke Kawaguchi 
>>>>> wrote:
>>>>>
>>>> I'm really excited with the p

Re: Trademark sublicense request: Jenkins WeChat Account in China

[arch]

There is still have a problem with the trademark. I want to use Jenkins as
the name of WeChat subscription account name. Do I still need to request
the trademark? Actually, I already met the issue. WeChat platform said I
need submit the permission of Jenkins trademark.

On Tue, Nov 6, 2018 at 10:26 AM arch  wrote:

> Yes, I prefer the service account at first. But this kind of account must
> base on a company entity. For now, the subscription account is ok.
>
> On Mon, Nov 5, 2018 at 9:10 PM Oleg Nenashev 
> wrote:
>
>> That said, where I disagree with Oleg in the email thread linked is that
>>> I don't think it's right that Alauda is tied to this account, or any other
>>> participant for that matter... I think it's great that Xiaojie is stepping
>>> up to the plate. All the powers to him!!  IIUC, that's "subscription
>>> account" and not "service account."
>>
>>
>> My suggestion was based on Rick's preference towards a "service account"
>> in the thread.
>> Personally I do not have any preference.
>>
>> I want to register the account as an organization. But I need an
>>> organization name and code. Oleg told me that there is not a real entity
>>> for Jenkins. I also do some homework about this. So my advice is that we
>>> register this account as an individual
>>>
>> Perfectly fine with me
>>
>> Best regards,
>> Oleg
>>
>>
>> On Sunday, November 4, 2018 at 6:39:37 AM UTC+3, Rick wrote:
>>
>>> Hi,
>>>
>>> I totally agree with the idea that Jenkins WeChat running under the
>>> community organization. It's fair for every contributor. My dream is that
>>> let more and more people join Jenkins party. But I met some situations
>>> during the process.
>>>
>>> First, I probably must use a personal email to register. I need to
>>> receive a verification code to complete the form. But the contact email
>>> could be jenkins-chinese-localization-...@googlegroups.com.
>>>
>>> Second, the subscription account may be the best solution. There are
>>> five types of WeChat Account Entity. They are government, media, company,
>>> individual and other organizations. I want to register the account as an
>>> organization. But I need an organization name and code. Oleg told me that
>>> there is not a real entity for Jenkins. I also do some homework about this.
>>> So my advice is that we register this account as an individual.  More
>>> detail page is here
>>> https://mp.weixin.qq.com/acct/contractorpage?action=showreg=3=zh_CN
>>> .
>>>
>>> It’s really great to get your support. I want to take the initiative.
>>> And I think the Chinese Localization SIG team members are happy to help the
>>> Jenkins WeChat. We have a regular video meeting. Every contributor could
>>> get the meeting time in the calendar https://jenkins.io/event-calendar/.
>>> This’s open for everyone.
>>>
>>> BTW, if there is no other concerns or questions. Once you think ok with
>>> my solution and advice, then I will begin my job.
>>>
>>>
>>> Best,
>>>
>>> Rick (Zhao Xiaojie)
>>>
>> On Fri, Nov 2, 2018 at 3:22 AM Kohsuke Kawaguchi 
>>> wrote:
>>>
>> I'm really excited with the prospect of Jenkins project getting WeChat
>>>> presence. I've been to China a few times myself, I have my own WeChat
>>>> account, and I know how big and ubiquitous this is over there.
>>>>
>>>> That said, where I disagree with Oleg in the email thread linked is
>>>> that I don't think it's right that Alauda is tied to this account, or any
>>>> other participant for that matter. The idea of this WeChat account is for
>>>> it to be the "official" Jenkins account on WeChat. Trademark sublicensing
>>>> request is to allow the requester to use the name in question for their
>>>> purposes outside official community activity.
>>>>
>>>> From the community's perspective, where this manifests as a question is
>>>> how to share the access to this account with others. For example, what if
>>>> Alauda moves on and stops engaging the Jenkins community? What if it gets
>>>> acquired? I'm not assuming any malice or meaning to distrust anybody here,
>>>> but it's a part of the basic safe guards for shared community assets. This
>>>> asset is to be controlled by the community, not by Alauda --- I think
>>>> everyone agrees on that here, b

Re: Trademark sublicense request: Jenkins WeChat Account in China

[arch]

Yes, I prefer the service account at first. But this kind of account must
base on a company entity. For now, the subscription account is ok.

On Mon, Nov 5, 2018 at 9:10 PM Oleg Nenashev  wrote:

> That said, where I disagree with Oleg in the email thread linked is that I
>> don't think it's right that Alauda is tied to this account, or any other
>> participant for that matter... I think it's great that Xiaojie is stepping
>> up to the plate. All the powers to him!!  IIUC, that's "subscription
>> account" and not "service account."
>
>
> My suggestion was based on Rick's preference towards a "service account"
> in the thread.
> Personally I do not have any preference.
>
> I want to register the account as an organization. But I need an
>> organization name and code. Oleg told me that there is not a real entity
>> for Jenkins. I also do some homework about this. So my advice is that we
>> register this account as an individual
>>
> Perfectly fine with me
>
> Best regards,
> Oleg
>
>
> On Sunday, November 4, 2018 at 6:39:37 AM UTC+3, Rick wrote:
>
>> Hi,
>>
>> I totally agree with the idea that Jenkins WeChat running under the
>> community organization. It's fair for every contributor. My dream is that
>> let more and more people join Jenkins party. But I met some situations
>> during the process.
>>
>> First, I probably must use a personal email to register. I need to
>> receive a verification code to complete the form. But the contact email
>> could be jenkins-chinese-localization-...@googlegroups.com.
>>
>> Second, the subscription account may be the best solution. There are five
>> types of WeChat Account Entity. They are government, media, company,
>> individual and other organizations. I want to register the account as an
>> organization. But I need an organization name and code. Oleg told me that
>> there is not a real entity for Jenkins. I also do some homework about this.
>> So my advice is that we register this account as an individual.  More
>> detail page is here
>> https://mp.weixin.qq.com/acct/contractorpage?action=showreg=3=zh_CN
>> .
>>
>> It’s really great to get your support. I want to take the initiative. And
>> I think the Chinese Localization SIG team members are happy to help the
>> Jenkins WeChat. We have a regular video meeting. Every contributor could
>> get the meeting time in the calendar https://jenkins.io/event-calendar/.
>> This’s open for everyone.
>>
>> BTW, if there is no other concerns or questions. Once you think ok with
>> my solution and advice, then I will begin my job.
>>
>>
>> Best,
>>
>> Rick (Zhao Xiaojie)
>>
> On Fri, Nov 2, 2018 at 3:22 AM Kohsuke Kawaguchi  wrote:
>>
> I'm really excited with the prospect of Jenkins project getting WeChat
>>> presence. I've been to China a few times myself, I have my own WeChat
>>> account, and I know how big and ubiquitous this is over there.
>>>
>>> That said, where I disagree with Oleg in the email thread linked is that
>>> I don't think it's right that Alauda is tied to this account, or any other
>>> participant for that matter. The idea of this WeChat account is for it to
>>> be the "official" Jenkins account on WeChat. Trademark sublicensing request
>>> is to allow the requester to use the name in question for their purposes
>>> outside official community activity.
>>>
>>> From the community's perspective, where this manifests as a question is
>>> how to share the access to this account with others. For example, what if
>>> Alauda moves on and stops engaging the Jenkins community? What if it gets
>>> acquired? I'm not assuming any malice or meaning to distrust anybody here,
>>> but it's a part of the basic safe guards for shared community assets. This
>>> asset is to be controlled by the community, not by Alauda --- I think
>>> everyone agrees on that here, but let's be very clear about that!
>>>
>>> I think the right thing to do is to setup an account that does not
>>> require any company, Alauda or not, to proxy this. Then provided that this
>>> is reasonably easily possible, this account should be tied and owned by the
>>> email address of some community team, say infra team or Chinese
>>> Localization SIG. Then when it comes to the actual operation of this, I
>>> think it's great that Xiaojie is stepping up to the plate. All the powers
>>> to him!!  IIUC, that's "subscription account" and not "service account."
>>>

Re: Trademark sublicense request: Jenkins WeChat Account in China

[arch]

Hi,

I totally agree with the idea that Jenkins WeChat running under the
community organization. It's fair for every contributor. My dream is that
let more and more people join Jenkins party. But I met some situations
during the process.

First, I probably must use a personal email to register. I need to receive
a verification code to complete the form. But the contact email could be
jenkins-chinese-localization-...@googlegroups.com.

Second, the subscription account may be the best solution. There are five
types of WeChat Account Entity. They are government, media, company,
individual and other organizations. I want to register the account as an
organization. But I need an organization name and code. Oleg told me that
there is not a real entity for Jenkins. I also do some homework about this.
So my advice is that we register this account as an individual.  More
detail page is here
https://mp.weixin.qq.com/acct/contractorpage?action=showreg=3=zh_CN
.

It’s really great to get your support. I want to take the initiative. And I
think the Chinese Localization SIG team members are happy to help the
Jenkins WeChat. We have a regular video meeting. Every contributor could
get the meeting time in the calendar https://jenkins.io/event-calendar/.
This’s open for everyone.

BTW, if there is no other concerns or questions. Once you think ok with my
solution and advice, then I will begin my job.


Best,

Rick (Zhao Xiaojie)
On Fri, Nov 2, 2018 at 3:22 AM Kohsuke Kawaguchi  wrote:

> I'm really excited with the prospect of Jenkins project getting WeChat
> presence. I've been to China a few times myself, I have my own WeChat
> account, and I know how big and ubiquitous this is over there.
>
> That said, where I disagree with Oleg in the email thread linked is that I
> don't think it's right that Alauda is tied to this account, or any other
> participant for that matter. The idea of this WeChat account is for it to
> be the "official" Jenkins account on WeChat. Trademark sublicensing request
> is to allow the requester to use the name in question for their purposes
> outside official community activity.
>
> From the community's perspective, where this manifests as a question is
> how to share the access to this account with others. For example, what if
> Alauda moves on and stops engaging the Jenkins community? What if it gets
> acquired? I'm not assuming any malice or meaning to distrust anybody here,
> but it's a part of the basic safe guards for shared community assets. This
> asset is to be controlled by the community, not by Alauda --- I think
> everyone agrees on that here, but let's be very clear about that!
>
> I think the right thing to do is to setup an account that does not require
> any company, Alauda or not, to proxy this. Then provided that this is
> reasonably easily possible, this account should be tied and owned by the
> email address of some community team, say infra team or Chinese
> Localization SIG. Then when it comes to the actual operation of this, I
> think it's great that Xiaojie is stepping up to the plate. All the powers
> to him!!  IIUC, that's "subscription account" and not "service account."
>
> None of this should involve trademark sublicensing, because this IS the
> official community effort whose authority is chained to the existing
> governance structure.
>
> On Thu, Nov 1, 2018 at 12:22 AM arch  wrote:
>
>> On behalf on Alauda, I'd like to request the permission to use
>> the following name that uses 'Jenkins' in it: "Jenkins WeChat Account".
>>
>> WeChat is a very popular app in China. Most of the people have a WeChat
>> account in here. So I thought it's a great place to help grow the Jenkins
>> Community. We will post some events like JAM on it. And some articles
>> (original or translated from jenkins.io) is helpful for many Jenkins
>> users.
>>
>> You can find out more about discussing details in here:
>> https://groups.google.com/d/msgid/jenkinsci-dev/CAMM7nTGjLOg7m1uzXHxZaxTd4QFiRXjknBNOsegQ4JjTkkyH2g%40mail.gmail.com?utm_medium=email_source=footer
>>
>> Thank you.
>> Best!
>>
>> Rick (Zhao Xiaojie)
>>
>> --
>> 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-dev+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-dev/CAMM7nTFvfAKco%3DRxJ6jXCmwX39%2ByexfC1s8TZLwGSZ4dTLberQ%40mail.gmail.com
>> <https://groups.google.com/d/msgid/jenkinsci-dev/CAMM7nTFvfAKco%3DRxJ6jXCmwX39%2ByexfC1s8TZLwGSZ4dTLberQ%40mail.gmail.com?utm_medium=email_source=footer>
>> .
&g

Re: translation team in jenkins-x org

[arch]

The background is that we have a Chinese Localization SIG. So we have a
number of people could do the translation review work. I just suggest
creating a team instead of address someone.

On Sat, Nov 3, 2018 at 8:11 PM  wrote:

> BTW PRs should be made against the `jx-docs` git repository
> https://github.com/jenkins-x/jx-docs/ thats the source code which is used
> to generate the Jenkins X website and docs: https://jenkins-x.io/
>
> the https://github.com/jenkins-x/jenkins-x-website repository contains
> the output of the build from `jx-docs` only.
>
>
> On Friday, November 2, 2018 at 9:10:15 AM UTC, James Nord wrote:
>
>> Hi,
>> Where are they addressing you?
>> For pull request on the Jenkins-x website I think we just need to tweak
>> the owners, so the correct people can actually approve request and be added
>> as reviews the or flow (but also the team would need to be on the same org
>> as the repo if a team was needed).  You should be able to create a pr to
>> enable this yourself.
>> However my understanding could be completely wrong here
>> /James
>>
>> On Mon, 29 Oct 2018, 10:12 arch >
> Hi,
>>> Some contributors are doing contributing to 'jx-docs'. And we have a SIG
>>> to do the translation review work. More detail is here
>>> https://jenkins.io/sigs/chinese-localization/. But there isn't a team
>>> that people could address. So everyone addresses me for now. So I wonder if
>>> we could create a translation team or same with
>>> https://github.com/orgs/jenkinsci/teams/chinese-localization-sig.
>>> And I wish I could free to add members.
>>>
>>> Thanks.
>>> Zhao Xiaojie
>>>
>>> --
>>> 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/CAMM7nTEBQwbrMaNy28zekJdb3DjG0n4WoK2RHD0Lg0BSSCSwYA%40mail.gmail.com
>>> <https://groups.google.com/d/msgid/jenkinsci-dev/CAMM7nTEBQwbrMaNy28zekJdb3DjG0n4WoK2RHD0Lg0BSSCSwYA%40mail.gmail.com?utm_medium=email_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 jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/48fa151b-c030-4095-aac3-c4227548705d%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/48fa151b-c030-4095-aac3-c4227548705d%40googlegroups.com?utm_medium=email_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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAMM7nTFskVVh9d563TA3TAroExqjhzMOPQHiqus7Eum_HeBq8w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Hacktoberfest

[arch]

hi:

Hacktoberfest event drew down. Anyone know how to get the data of the
Jenkins community contributions.

-- 
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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAMM7nTG0n-OUA0sMm9kB-JpuD3EAT%2BXd3%2BKuoid1_d%2BmRwKduA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Trademark sublicense request: Jenkins WeChat Account in China

[arch]

On behalf on Alauda, I'd like to request the permission to use
the following name that uses 'Jenkins' in it: "Jenkins WeChat Account".

WeChat is a very popular app in China. Most of the people have a WeChat
account in here. So I thought it's a great place to help grow the Jenkins
Community. We will post some events like JAM on it. And some articles
(original or translated from jenkins.io) is helpful for many Jenkins users.

You can find out more about discussing details in here:
https://groups.google.com/d/msgid/jenkinsci-dev/CAMM7nTGjLOg7m1uzXHxZaxTd4QFiRXjknBNOsegQ4JjTkkyH2g%40mail.gmail.com?utm_medium=email_source=footer

Thank you.
Best!

Rick (Zhao Xiaojie)

-- 
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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAMM7nTFvfAKco%3DRxJ6jXCmwX39%2ByexfC1s8TZLwGSZ4dTLberQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Growing community via a stronger Twitter presence

[arch]

About trademark. Do I need to create an issue in JIRA or other places?

On Thu, Nov 1, 2018 at 2:55 PM arch  wrote:

> We all agree with this. I think it's good for Jenkins Community and
> Chinese users(developers). It could let more Chinese people get messages
> and information from Jenkins Community. So if there are no other concerns.
> I'll work on this.
> First of all, I going to make sure every contributor in China
> could involve it. I think that create a repo in jenkins-infra to store
> articles is a good way. So people could review the article.
>
>
> On Wed, Oct 31, 2018 at 5:06 PM arch  wrote:
>
>> We should think about the concerns. But maybe running WeChat Service
>> Account in a local company is a better solution for now. To make sure the
>> Jenkins Board members have the full control is necessary. So other people
>> could make a request to join the management team. I'll discuss about the
>> details with my company.
>>
>> On Wed, Oct 31, 2018 at 3:52 PM Oleg Nenashev 
>> wrote:
>>
>>> Yes, it was discussed above.
>>> Jenkins project cannot provide this data, because it has no legal entity.
>>>
>>> My suggestion would be to register a chat on a local company as you
>>> suggested above:
>>>
>>>1. Select a name for the chat, e.g. "Jenkins WeChat Channel" or
>>>whatever cool (I am bad at naming)
>>>2. Approve Trademark at the Jenkins Governance meeting:
>>>https://wiki.jenkins.io/display/JENKINS/Approved+Trademark+Usage
>>>3. Send WeChat registration request
>>>
>>> Such approach would allow to make the chat official and to prevent
>>> concerns from other community members about the chat being operated by a
>>> company.
>>> W.r.t the company to own the trademark, it may be your company as
>>> suggested above. Or maybe another company if we are able to find a partner
>>> interested in it.
>>>
>>> Best regards,
>>> Oleg
>>>
>>>
>>>
>>> On Wed, Oct 31, 2018 at 3:12 AM arch  wrote:
>>>
>>>> For WeChat Offical Accounts Platform, there are four account types. At
>>>> first, I prefer the Service Account. But I need Organization name and 
>>>> Organization
>>>> Code if I choose Service Account.
>>>> Maybe I should take the Subscription Account.
>>>> You can find more details in here
>>>> https://mp.weixin.qq.com/cgi-bin/registermidpage?action=index=en_US=
>>>> .
>>>>
>>>> On Tue, Oct 30, 2018 at 6:00 PM Baptiste Mathus  wrote:
>>>>
>>>>> Hey I think you'll need to treat us, at least me, as kids with regards
>>>>> to this.
>>>>> I've personally no idea what an 'organization number' means and how
>>>>> the Jenkins Project would ever get one.
>>>>>
>>>>> Le mar. 30 oct. 2018 à 03:25, arch  a écrit :
>>>>>
>>>>>> As we discussed before. It'll need an organization number for
>>>>>> creating WeChat.
>>>>>>
>>>>>> On Tue, Oct 30, 2018 at 4:58 AM Oleg Nenashev 
>>>>>> wrote:
>>>>>>
>>>>>>> Hi,
>>>>>>>
>>>>>>> I would like to get access to the Jenkins Twitter account so that I
>>>>>>> can help with tweets in the EU timezone and with GSoC-related stuff. 
>>>>>>> Would
>>>>>>> it be possible?
>>>>>>>
>>>>>>> W.R.T WeChat, just go forward IMO. It may require a trademark usage
>>>>>>> request, but I do not see blockers from our side.
>>>>>>>
>>>>>>> BR, Oleg
>>>>>>>
>>>>>>> On Sat, Oct 27, 2018, 04:06 arch >>>>>>
>>>>>>>> Hi racy Miranda, did I missed the meeting? I'd like to take the 
>>>>>>>> initiative
>>>>>>>> to work on Jenkins in Wechat.
>>>>>>>>
>>>>>>>> On Tue, Oct 2, 2018 at 9:15 PM arch  wrote:
>>>>>>>>
>>>>>>>>> OK, I have joined the room. I'd like to discuss this.
>>>>>>>>>
>>>>>>>>> On Tue, Oct 2, 2018 at 6:44 PM Tracy Miranda <
>>>>>>>>> tmira...@cloudbees.com> wrote:
>>>>>>>>>
>>>>>>>>>> Hi all,
>>>>>>

Re: Growing community via a stronger Twitter presence

[arch]

We all agree with this. I think it's good for Jenkins Community and Chinese
users(developers). It could let more Chinese people get messages and
information from Jenkins Community. So if there are no other concerns. I'll
work on this.
First of all, I going to make sure every contributor in China
could involve it. I think that create a repo in jenkins-infra to store
articles is a good way. So people could review the article.

On Wed, Oct 31, 2018 at 5:06 PM arch  wrote:

> We should think about the concerns. But maybe running WeChat Service
> Account in a local company is a better solution for now. To make sure the
> Jenkins Board members have the full control is necessary. So other people
> could make a request to join the management team. I'll discuss about the
> details with my company.
>
> On Wed, Oct 31, 2018 at 3:52 PM Oleg Nenashev 
> wrote:
>
>> Yes, it was discussed above.
>> Jenkins project cannot provide this data, because it has no legal entity.
>>
>> My suggestion would be to register a chat on a local company as you
>> suggested above:
>>
>>1. Select a name for the chat, e.g. "Jenkins WeChat Channel" or
>>whatever cool (I am bad at naming)
>>2. Approve Trademark at the Jenkins Governance meeting:
>>https://wiki.jenkins.io/display/JENKINS/Approved+Trademark+Usage
>>3. Send WeChat registration request
>>
>> Such approach would allow to make the chat official and to prevent
>> concerns from other community members about the chat being operated by a
>> company.
>> W.r.t the company to own the trademark, it may be your company as
>> suggested above. Or maybe another company if we are able to find a partner
>> interested in it.
>>
>> Best regards,
>> Oleg
>>
>>
>>
>> On Wed, Oct 31, 2018 at 3:12 AM arch  wrote:
>>
>>> For WeChat Offical Accounts Platform, there are four account types. At
>>> first, I prefer the Service Account. But I need Organization name and 
>>> Organization
>>> Code if I choose Service Account.
>>> Maybe I should take the Subscription Account.
>>> You can find more details in here
>>> https://mp.weixin.qq.com/cgi-bin/registermidpage?action=index=en_US=
>>> .
>>>
>>> On Tue, Oct 30, 2018 at 6:00 PM Baptiste Mathus  wrote:
>>>
>>>> Hey I think you'll need to treat us, at least me, as kids with regards
>>>> to this.
>>>> I've personally no idea what an 'organization number' means and how the
>>>> Jenkins Project would ever get one.
>>>>
>>>> Le mar. 30 oct. 2018 à 03:25, arch  a écrit :
>>>>
>>>>> As we discussed before. It'll need an organization number for creating
>>>>> WeChat.
>>>>>
>>>>> On Tue, Oct 30, 2018 at 4:58 AM Oleg Nenashev 
>>>>> wrote:
>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> I would like to get access to the Jenkins Twitter account so that I
>>>>>> can help with tweets in the EU timezone and with GSoC-related stuff. 
>>>>>> Would
>>>>>> it be possible?
>>>>>>
>>>>>> W.R.T WeChat, just go forward IMO. It may require a trademark usage
>>>>>> request, but I do not see blockers from our side.
>>>>>>
>>>>>> BR, Oleg
>>>>>>
>>>>>> On Sat, Oct 27, 2018, 04:06 arch >>>>>
>>>>>>> Hi racy Miranda, did I missed the meeting? I'd like to take the 
>>>>>>> initiative
>>>>>>> to work on Jenkins in Wechat.
>>>>>>>
>>>>>>> On Tue, Oct 2, 2018 at 9:15 PM arch  wrote:
>>>>>>>
>>>>>>>> OK, I have joined the room. I'd like to discuss this.
>>>>>>>>
>>>>>>>> On Tue, Oct 2, 2018 at 6:44 PM Tracy Miranda <
>>>>>>>> tmira...@cloudbees.com> wrote:
>>>>>>>>
>>>>>>>>> Hi all,
>>>>>>>>>
>>>>>>>>> As an update this is progressing.
>>>>>>>>>
>>>>>>>>> Thanks to all those who would like to be involved. For now I
>>>>>>>>> recommend you join https://gitter.im/jenkinsci/jenkins-community
>>>>>>>>> and tag me on tweet suggestions and I will schedule them out to go 
>>>>>>>>> out.
>>>>>>>>> Then we 

Re: Growing community via a stronger Twitter presence

[arch]

We should think about the concerns. But maybe running WeChat Service
Account in a local company is a better solution for now. To make sure the
Jenkins Board members have the full control is necessary. So other people
could make a request to join the management team. I'll discuss about the
details with my company.

On Wed, Oct 31, 2018 at 3:52 PM Oleg Nenashev 
wrote:

> Yes, it was discussed above.
> Jenkins project cannot provide this data, because it has no legal entity.
>
> My suggestion would be to register a chat on a local company as you
> suggested above:
>
>1. Select a name for the chat, e.g. "Jenkins WeChat Channel" or
>whatever cool (I am bad at naming)
>2. Approve Trademark at the Jenkins Governance meeting:
>https://wiki.jenkins.io/display/JENKINS/Approved+Trademark+Usage
>3. Send WeChat registration request
>
> Such approach would allow to make the chat official and to prevent
> concerns from other community members about the chat being operated by a
> company.
> W.r.t the company to own the trademark, it may be your company as
> suggested above. Or maybe another company if we are able to find a partner
> interested in it.
>
> Best regards,
> Oleg
>
>
>
> On Wed, Oct 31, 2018 at 3:12 AM arch  wrote:
>
>> For WeChat Offical Accounts Platform, there are four account types. At
>> first, I prefer the Service Account. But I need Organization name and 
>> Organization
>> Code if I choose Service Account.
>> Maybe I should take the Subscription Account.
>> You can find more details in here
>> https://mp.weixin.qq.com/cgi-bin/registermidpage?action=index=en_US=
>> .
>>
>> On Tue, Oct 30, 2018 at 6:00 PM Baptiste Mathus  wrote:
>>
>>> Hey I think you'll need to treat us, at least me, as kids with regards
>>> to this.
>>> I've personally no idea what an 'organization number' means and how the
>>> Jenkins Project would ever get one.
>>>
>>> Le mar. 30 oct. 2018 à 03:25, arch  a écrit :
>>>
>>>> As we discussed before. It'll need an organization number for creating
>>>> WeChat.
>>>>
>>>> On Tue, Oct 30, 2018 at 4:58 AM Oleg Nenashev 
>>>> wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> I would like to get access to the Jenkins Twitter account so that I
>>>>> can help with tweets in the EU timezone and with GSoC-related stuff. Would
>>>>> it be possible?
>>>>>
>>>>> W.R.T WeChat, just go forward IMO. It may require a trademark usage
>>>>> request, but I do not see blockers from our side.
>>>>>
>>>>> BR, Oleg
>>>>>
>>>>> On Sat, Oct 27, 2018, 04:06 arch >>>>
>>>>>> Hi racy Miranda, did I missed the meeting? I'd like to take the 
>>>>>> initiative
>>>>>> to work on Jenkins in Wechat.
>>>>>>
>>>>>> On Tue, Oct 2, 2018 at 9:15 PM arch  wrote:
>>>>>>
>>>>>>> OK, I have joined the room. I'd like to discuss this.
>>>>>>>
>>>>>>> On Tue, Oct 2, 2018 at 6:44 PM Tracy Miranda 
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Hi all,
>>>>>>>>
>>>>>>>> As an update this is progressing.
>>>>>>>>
>>>>>>>> Thanks to all those who would like to be involved. For now I
>>>>>>>> recommend you join https://gitter.im/jenkinsci/jenkins-community
>>>>>>>> and tag me on tweet suggestions and I will schedule them out to go out.
>>>>>>>> Then we can work on expanding the fold to make this easier.
>>>>>>>>
>>>>>>>> For WeChat, that would be good to do but looks like there are some
>>>>>>>> potential legal issues to sort out. Maybe we can schedule a call next 
>>>>>>>> week
>>>>>>>> to discuss?
>>>>>>>>
>>>>>>>> Tracy
>>>>>>>>
>>>>>>>> On Fri, Sep 28, 2018 at 12:21 PM, arch 
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> How is it going?
>>>>>>>>>
>>>>>>>>> On Thu, Aug 30, 2018 at 9:32 PM arch  wrote:
>>>>>>>>>
>>>>>>>>>> There isn't any description of this in WeChat website. It just

Re: Growing community via a stronger Twitter presence

[arch]

For WeChat Offical Accounts Platform, there are four account types. At
first, I prefer the Service Account. But I need Organization name and
Organization
Code if I choose Service Account.
Maybe I should take the Subscription Account.
You can find more details in here
https://mp.weixin.qq.com/cgi-bin/registermidpage?action=index=en_US=
.

On Tue, Oct 30, 2018 at 6:00 PM Baptiste Mathus  wrote:

> Hey I think you'll need to treat us, at least me, as kids with regards to
> this.
> I've personally no idea what an 'organization number' means and how the
> Jenkins Project would ever get one.
>
> Le mar. 30 oct. 2018 à 03:25, arch  a écrit :
>
>> As we discussed before. It'll need an organization number for creating
>> WeChat.
>>
>> On Tue, Oct 30, 2018 at 4:58 AM Oleg Nenashev 
>> wrote:
>>
>>> Hi,
>>>
>>> I would like to get access to the Jenkins Twitter account so that I can
>>> help with tweets in the EU timezone and with GSoC-related stuff. Would it
>>> be possible?
>>>
>>> W.R.T WeChat, just go forward IMO. It may require a trademark usage
>>> request, but I do not see blockers from our side.
>>>
>>> BR, Oleg
>>>
>>> On Sat, Oct 27, 2018, 04:06 arch >>
>>>> Hi racy Miranda, did I missed the meeting? I'd like to take the initiative
>>>> to work on Jenkins in Wechat.
>>>>
>>>> On Tue, Oct 2, 2018 at 9:15 PM arch  wrote:
>>>>
>>>>> OK, I have joined the room. I'd like to discuss this.
>>>>>
>>>>> On Tue, Oct 2, 2018 at 6:44 PM Tracy Miranda 
>>>>> wrote:
>>>>>
>>>>>> Hi all,
>>>>>>
>>>>>> As an update this is progressing.
>>>>>>
>>>>>> Thanks to all those who would like to be involved. For now I
>>>>>> recommend you join https://gitter.im/jenkinsci/jenkins-community and
>>>>>> tag me on tweet suggestions and I will schedule them out to go out.
>>>>>> Then we can work on expanding the fold to make this easier.
>>>>>>
>>>>>> For WeChat, that would be good to do but looks like there are some
>>>>>> potential legal issues to sort out. Maybe we can schedule a call next 
>>>>>> week
>>>>>> to discuss?
>>>>>>
>>>>>> Tracy
>>>>>>
>>>>>> On Fri, Sep 28, 2018 at 12:21 PM, arch  wrote:
>>>>>>
>>>>>>> How is it going?
>>>>>>>
>>>>>>> On Thu, Aug 30, 2018 at 9:32 PM arch  wrote:
>>>>>>>
>>>>>>>> There isn't any description of this in WeChat website. It just
>>>>>>>> requires an organization number. We can try it. Or if you think it's ok
>>>>>>>> then I can apply the account as the name of my company.
>>>>>>>> Yes, we can't talk about policy in China.
>>>>>>>>
>>>>>>>> On Mon, Aug 20, 2018 at 7:43 AM Oleg Nenashev <
>>>>>>>> o.v.nenas...@gmail.com> wrote:
>>>>>>>>
>>>>>>>>> But there is one problem, only enterprise or organization can
>>>>>>>>>> register. If we want to do this, we need Jenkins support.
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Jenkins has no legal entity, it leaves under umbrella of SPI
>>>>>>>>> <https://www.spi-inc.org/>. I am not sure that Jenkins qualifies
>>>>>>>>> from the legal PoV, even if such registration agreement is acceptable 
>>>>>>>>> from
>>>>>>>>> the project,s PoV (e.g. whether we can accept WeChat censorship
>>>>>>>>> <https://qz.com/960948/what-happens-when-you-try-to-send-politically-sensitive-messages-on-wechat/>,
>>>>>>>>> etc.). Could you provide a list of requirements to such organizations?
>>>>>>>>>
>>>>>>>>> BR, Oleg
>>>>>>>>>
>>>>>>>>> On Mon, Aug 20, 2018 at 12:40 AM arch 
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>> I can handle this. Yeah, WeChat is the Chinese version Twitter.
>>>>>>>>>> Everyone loves WeChat. Gitter is awesome. But just a few people to 
>>

Re: Request to join security team

[arch]

My pleasure!

On Tue, Oct 30, 2018 at 8:49 PM Daniel Beck  wrote:

> Welcome aboard!
>
> I've sent you a separate email about the various services.
>
> > On 27. Sep 2018, at 16:58, arch  wrote:
> >
> > I'm interested in joining the security team. I've got 2FA enabled on
> Github(username LinuxSuRen), signed the CLA. My Jenkins community username
> is surenpi.
>
> --
> 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-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/E203661F-3136-4D4B-9A0F-6EA42F787EBA%40beckweb.net
> .
> 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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAMM7nTFyhCcZ9ryLM2bfg0KAnYX1%3DKHdMg49Yx0Nxi1B9pfe6A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Growing community via a stronger Twitter presence

[arch]

As we discussed before. It'll need an organization number for creating
WeChat.

On Tue, Oct 30, 2018 at 4:58 AM Oleg Nenashev 
wrote:

> Hi,
>
> I would like to get access to the Jenkins Twitter account so that I can
> help with tweets in the EU timezone and with GSoC-related stuff. Would it
> be possible?
>
> W.R.T WeChat, just go forward IMO. It may require a trademark usage
> request, but I do not see blockers from our side.
>
> BR, Oleg
>
> On Sat, Oct 27, 2018, 04:06 arch 
>> Hi racy Miranda, did I missed the meeting? I'd like to take the initiative
>> to work on Jenkins in Wechat.
>>
>> On Tue, Oct 2, 2018 at 9:15 PM arch  wrote:
>>
>>> OK, I have joined the room. I'd like to discuss this.
>>>
>>> On Tue, Oct 2, 2018 at 6:44 PM Tracy Miranda 
>>> wrote:
>>>
>>>> Hi all,
>>>>
>>>> As an update this is progressing.
>>>>
>>>> Thanks to all those who would like to be involved. For now I recommend
>>>> you join https://gitter.im/jenkinsci/jenkins-community and tag me on
>>>> tweet suggestions and I will schedule them out to go out.
>>>> Then we can work on expanding the fold to make this easier.
>>>>
>>>> For WeChat, that would be good to do but looks like there are some
>>>> potential legal issues to sort out. Maybe we can schedule a call next week
>>>> to discuss?
>>>>
>>>> Tracy
>>>>
>>>> On Fri, Sep 28, 2018 at 12:21 PM, arch  wrote:
>>>>
>>>>> How is it going?
>>>>>
>>>>> On Thu, Aug 30, 2018 at 9:32 PM arch  wrote:
>>>>>
>>>>>> There isn't any description of this in WeChat website. It just
>>>>>> requires an organization number. We can try it. Or if you think it's ok
>>>>>> then I can apply the account as the name of my company.
>>>>>> Yes, we can't talk about policy in China.
>>>>>>
>>>>>> On Mon, Aug 20, 2018 at 7:43 AM Oleg Nenashev 
>>>>>> wrote:
>>>>>>
>>>>>>> But there is one problem, only enterprise or organization can
>>>>>>>> register. If we want to do this, we need Jenkins support.
>>>>>>>>
>>>>>>>
>>>>>>> Jenkins has no legal entity, it leaves under umbrella of SPI
>>>>>>> <https://www.spi-inc.org/>. I am not sure that Jenkins qualifies
>>>>>>> from the legal PoV, even if such registration agreement is acceptable 
>>>>>>> from
>>>>>>> the project,s PoV (e.g. whether we can accept WeChat censorship
>>>>>>> <https://qz.com/960948/what-happens-when-you-try-to-send-politically-sensitive-messages-on-wechat/>,
>>>>>>> etc.). Could you provide a list of requirements to such organizations?
>>>>>>>
>>>>>>> BR, Oleg
>>>>>>>
>>>>>>> On Mon, Aug 20, 2018 at 12:40 AM arch  wrote:
>>>>>>>
>>>>>>>> I can handle this. Yeah, WeChat is the Chinese version Twitter.
>>>>>>>> Everyone loves WeChat. Gitter is awesome. But just a few people to use 
>>>>>>>> it,
>>>>>>>> we prefer WeChat. And the Enterprise WeChat is more official.
>>>>>>>> But there is one problem, only enterprise or organization can
>>>>>>>> register. If we want to do this, we need Jenkins support.
>>>>>>>>
>>>>>>>> On Mon, Aug 20, 2018 at 6:13 AM Oleg Nenashev <
>>>>>>>> o.v.nenas...@gmail.com> wrote:
>>>>>>>>
>>>>>>>>> Yes, having such resources would be a great help to promote the
>>>>>>>>> local Jenkins communities and events. If you are interested to create 
>>>>>>>>> them,
>>>>>>>>> thumbs up! Just be sure you can dedicate enough time to maintain this
>>>>>>>>> resources in the active state.
>>>>>>>>>
>>>>>>>>> Personal experience: In Jenkins RU we use Twitter (@jenkins_ru
>>>>>>>>> <https://twitter.com/jenkins_ru>) but it is not that effective,
>>>>>>>>> because it is just time consuming to track and repost content (tip: I 
>>>>>>>>> will
>>>>>>

translation team in jenkins-x org

[arch]

Hi,
Some contributors are doing contributing to 'jx-docs'. And we have a SIG to
do the translation review work. More detail is here
https://jenkins.io/sigs/chinese-localization/. But there isn't a team that
people could address. So everyone addresses me for now. So I wonder if we
could create a translation team or same with
https://github.com/orgs/jenkinsci/teams/chinese-localization-sig.
And I wish I could free to add members.

Thanks.
Zhao Xiaojie

-- 
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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAMM7nTEBQwbrMaNy28zekJdb3DjG0n4WoK2RHD0Lg0BSSCSwYA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Growing community via a stronger Twitter presence

[arch]

Hi racy Miranda, did I missed the meeting? I'd like to take the initiative
to work on Jenkins in Wechat.

On Tue, Oct 2, 2018 at 9:15 PM arch  wrote:

> OK, I have joined the room. I'd like to discuss this.
>
> On Tue, Oct 2, 2018 at 6:44 PM Tracy Miranda 
> wrote:
>
>> Hi all,
>>
>> As an update this is progressing.
>>
>> Thanks to all those who would like to be involved. For now I recommend
>> you join https://gitter.im/jenkinsci/jenkins-community and tag me on
>> tweet suggestions and I will schedule them out to go out.
>> Then we can work on expanding the fold to make this easier.
>>
>> For WeChat, that would be good to do but looks like there are some
>> potential legal issues to sort out. Maybe we can schedule a call next week
>> to discuss?
>>
>> Tracy
>>
>> On Fri, Sep 28, 2018 at 12:21 PM, arch  wrote:
>>
>>> How is it going?
>>>
>>> On Thu, Aug 30, 2018 at 9:32 PM arch  wrote:
>>>
>>>> There isn't any description of this in WeChat website. It just requires
>>>> an organization number. We can try it. Or if you think it's ok then I can
>>>> apply the account as the name of my company.
>>>> Yes, we can't talk about policy in China.
>>>>
>>>> On Mon, Aug 20, 2018 at 7:43 AM Oleg Nenashev 
>>>> wrote:
>>>>
>>>>> But there is one problem, only enterprise or organization can
>>>>>> register. If we want to do this, we need Jenkins support.
>>>>>>
>>>>>
>>>>> Jenkins has no legal entity, it leaves under umbrella of SPI
>>>>> <https://www.spi-inc.org/>. I am not sure that Jenkins qualifies from
>>>>> the legal PoV, even if such registration agreement is acceptable from the
>>>>> project,s PoV (e.g. whether we can accept WeChat censorship
>>>>> <https://qz.com/960948/what-happens-when-you-try-to-send-politically-sensitive-messages-on-wechat/>,
>>>>> etc.). Could you provide a list of requirements to such organizations?
>>>>>
>>>>> BR, Oleg
>>>>>
>>>>> On Mon, Aug 20, 2018 at 12:40 AM arch  wrote:
>>>>>
>>>>>> I can handle this. Yeah, WeChat is the Chinese version Twitter.
>>>>>> Everyone loves WeChat. Gitter is awesome. But just a few people to use 
>>>>>> it,
>>>>>> we prefer WeChat. And the Enterprise WeChat is more official.
>>>>>> But there is one problem, only enterprise or organization can
>>>>>> register. If we want to do this, we need Jenkins support.
>>>>>>
>>>>>> On Mon, Aug 20, 2018 at 6:13 AM Oleg Nenashev 
>>>>>> wrote:
>>>>>>
>>>>>>> Yes, having such resources would be a great help to promote the
>>>>>>> local Jenkins communities and events. If you are interested to create 
>>>>>>> them,
>>>>>>> thumbs up! Just be sure you can dedicate enough time to maintain this
>>>>>>> resources in the active state.
>>>>>>>
>>>>>>> Personal experience: In Jenkins RU we use Twitter (@jenkins_ru
>>>>>>> <https://twitter.com/jenkins_ru>) but it is not that effective,
>>>>>>> because it is just time consuming to track and repost content (tip: I 
>>>>>>> will
>>>>>>> appreciate contributions!). We also have a localized Gitter channel
>>>>>>> <https://gitter.im/jenkinsci-ru/public> which is pretty active. But
>>>>>>> I believe that we could have had more discussions if we were using a 
>>>>>>> chat
>>>>>>> popular Russia (Telegram is blocked there, but apparently it is the most
>>>>>>> popular chat AFAICT). I'd guess WeChat would be a way to go in your 
>>>>>>> case.
>>>>>>>
>>>>>>> Best regards,
>>>>>>> Oleg
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Sun, Aug 19, 2018 at 11:58 PM arch  wrote:
>>>>>>>
>>>>>>>> Good to see Jenkins community is growing quickly, Twitter is also a
>>>>>>>> great and very popular platform.
>>>>>>>> And I hope more and more Chinese people could involve into the
>>>>>>>> Jenkins community, know

Re: juseppe - Jenkins Update Site Embedded for Plugin Publishing Easily - support

[arch]

Welcome.

On Thu, Oct 18, 2018 at 3:53 AM Oleg Nenashev 
wrote:

> Hello, transfer has been completed: https://github.com/jenkinsci/juseppe
> Welcome Juseppe to the Jenkins organization!
>
> Best regards,
> Oleg
>
>
> On Tuesday, October 16, 2018 at 9:20:07 PM UTC+2, Oleg Nenashev wrote:
>>
>> Yes, we would need to give you permissions first.
>>
>> BR, Oleg
>>
>> On Tue, Oct 16, 2018, 21:18 Kirill Merkushev  wrote:
>>
>>> Cool, tried to do a transfer, but it complains about insufficient rights
>>> to create a repo
>>>
>>> On Monday, 15 October 2018 22:15:55 UTC+2, Oleg Nenashev wrote:

 Hi Kirill,

 Yes, the project can be moved. I would even say it is a preference in
 this case. Usually we move repositories through the
 https://github.com/jenkinsci-transfer organization. If you are ready
 to do the migration, I am ready to assist.

 Let's give others some time to provide feedback before the migration.

 +1 from me

 BR, Oleg




 On Mon, Oct 15, 2018 at 12:54 PM Kirill Merkushev 
 wrote:

> I'm ready to move it to jenkinsci with no problem if it cat keep
> original naming and I will have admin rights on that repo.
>
> The process describes fork/or push model, but can it just be moved to
> just have a redirect from old place?
>
> What
>
> On Monday, 15 October 2018 01:15:35 UTC+2, Shaun Thompson wrote:
>>
>> As I need to publish plugins internally at my organization, I've been
>> using the this project  to
>> do so.
>>
>> The author no longer has time to maintain it and was inquiring if
>> this could come under the jenkinsci umbrella for long term support and
>> maintenance.
>>
>> Thanks
>>
> --
> 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/Blt0x6rWA0w/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/cc3175c5-e1de-4f38-a996-259fda011914%40googlegroups.com
> 
> .
> 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/Blt0x6rWA0w/unsubscribe.
>>> To unsubscribe from this group and all its topics, send an email to
>>> jenkinsci-dev+unsubscr...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/jenkinsci-dev/1f662cbf-cf47-47d9-ab04-ac9a899e755a%40googlegroups.com
>>> 
>>> .
>>> 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 jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/2fa6bd2d-d353-449d-b377-9309f1dcb963%40googlegroups.com
> 
> .
> 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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAMM7nTEkg0i-EV8Je6iPK1VrKOkUUcu8e_itjapPHFn4Od3LVQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Proposal: Pipeline Authoring SIG

[arch]

I could provide Chinese Pipeline documents or translation.

On Tue, Oct 16, 2018 at 3:39 PM Andrew Bayer  wrote:

> Definitely! Both Liam and myself will be at Nice.
>
> A.
>
> On Mon, Oct 15, 2018 at 9:03 PM Jon Brohauge 
> wrote:
>
>> Andrew,
>>
>> Very interesting idea. Been desperately trying to test my vars/ groovy
>> scripts with varying degrees of success. I'd love to contribute where I
>> can. Maybe we can meet up at Jenkins World in Nice?
>>
>> Regards
>> Jon Brohauge
>>
>> --
>> 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-dev+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-dev/61a94328-5957-4ba6-a148-1c8c7b545009%40googlegroups.com
>> 
>> .
>> 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 jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/CAPbPdOY2eX-Q7_E2%2B1bsZ2oxbp9ujKgS6xV4vqW79TAkvYAGEA%40mail.gmail.com
> 
> .
> 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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAMM7nTF6B3NCTRc22mq4KdLmXjvt4e7PYM2hyQaEydwAteUpgw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Proposal: Pipeline Authoring SIG

[arch]

Great idea.

On Tue, Oct 16, 2018 at 4:32 AM  wrote:

> I'm definitely interested in being part of this as well.
>
>
> On Monday, October 15, 2018 at 2:12:13 AM UTC-7, Andrew Bayer wrote:
>>
>> I’d like to propose the creation of a “Pipeline Authoring” SIG, with
>> myself as the lead. The focus of this SIG would be on improving all aspects
>> of the user experience around authoring Jenkins Pipeline. This includes:
>> * Syntax and structure
>> * Extensibility, code reuse, and code sharing
>> * Testability
>> * Documentation
>> * Tooling for Pipeline authors (like Snippet Generator, Directive
>> Generator, IDE integration, etc)
>> * Best practices (including tooling for gentle nudges in the direction of
>> best practices)
>> * Examples/"starter Jenkinsfiles" for various scenarios, etc
>>
>> While at Jenkins World I was able to discuss this idea with a number of
>> people.  Response was universally positive. Here are a few examples:
>>
>> * Steven Terrana (from Booz Allen) has done work on code sharing and
>> reuse in (https://github.com/boozallen/sdp-pipeline-framework) and is
>> interested in making some form of that available to the Jenkins community.
>> * Austin Witt (from HomeAway) has created on a groovy testing framework
>> for Jenkins Pipeline (https://github.com/homeaway/jenkins-spock/)
>> * Liam Newman (from CloudBees) has written and edited quite a bit of
>> documentation for  Jenkins Pipeline and provided feedback on the design on
>> a number of Pipeline feature.  He expressed a desire to continue expanding
>> and improving on that documentation.
>> * And Kohsuke basically demanded that we do this. =)
>>
>> While this is not a large group, it was enough to convince me that this
>> is an area that deserve a SIG. There is strong interest from a number of
>> people  number and the area is also not covered by existing SIGs.
>>
>> If you’d like to be part of the initial group of participants, please
>> respond on this thread. Other feedback and suggestion are also welcome. I
>> will create the appropriate SIG pages and channels in a few days.  We can
>> start figuring out where to focus our efforts first and can schedule the
>> group’s regular meetings to start some time after DevOps World - Jenkins
>> World in Nice .
>>
>> A.
>>
>> --
> 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-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/5e9e96e9-2960-4e6c-b11c-71f3a31e8146%40googlegroups.com
> 
> .
> 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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAMM7nTEHqr%3DKvngujjEvgYnLRjeT0PNCmMmsj-_Dfgni0XOteg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Growing community via a stronger Twitter presence

[arch]

OK, I have joined the room. I'd like to discuss this.

On Tue, Oct 2, 2018 at 6:44 PM Tracy Miranda  wrote:

> Hi all,
>
> As an update this is progressing.
>
> Thanks to all those who would like to be involved. For now I recommend you
> join https://gitter.im/jenkinsci/jenkins-community and tag me on tweet
> suggestions and I will schedule them out to go out.
> Then we can work on expanding the fold to make this easier.
>
> For WeChat, that would be good to do but looks like there are some
> potential legal issues to sort out. Maybe we can schedule a call next week
> to discuss?
>
> Tracy
>
> On Fri, Sep 28, 2018 at 12:21 PM, arch  wrote:
>
>> How is it going?
>>
>> On Thu, Aug 30, 2018 at 9:32 PM arch  wrote:
>>
>>> There isn't any description of this in WeChat website. It just requires
>>> an organization number. We can try it. Or if you think it's ok then I can
>>> apply the account as the name of my company.
>>> Yes, we can't talk about policy in China.
>>>
>>> On Mon, Aug 20, 2018 at 7:43 AM Oleg Nenashev 
>>> wrote:
>>>
>>>> But there is one problem, only enterprise or organization can register.
>>>>> If we want to do this, we need Jenkins support.
>>>>>
>>>>
>>>> Jenkins has no legal entity, it leaves under umbrella of SPI
>>>> <https://www.spi-inc.org/>. I am not sure that Jenkins qualifies from
>>>> the legal PoV, even if such registration agreement is acceptable from the
>>>> project,s PoV (e.g. whether we can accept WeChat censorship
>>>> <https://qz.com/960948/what-happens-when-you-try-to-send-politically-sensitive-messages-on-wechat/>,
>>>> etc.). Could you provide a list of requirements to such organizations?
>>>>
>>>> BR, Oleg
>>>>
>>>> On Mon, Aug 20, 2018 at 12:40 AM arch  wrote:
>>>>
>>>>> I can handle this. Yeah, WeChat is the Chinese version Twitter.
>>>>> Everyone loves WeChat. Gitter is awesome. But just a few people to use it,
>>>>> we prefer WeChat. And the Enterprise WeChat is more official.
>>>>> But there is one problem, only enterprise or organization can
>>>>> register. If we want to do this, we need Jenkins support.
>>>>>
>>>>> On Mon, Aug 20, 2018 at 6:13 AM Oleg Nenashev 
>>>>> wrote:
>>>>>
>>>>>> Yes, having such resources would be a great help to promote the local
>>>>>> Jenkins communities and events. If you are interested to create them,
>>>>>> thumbs up! Just be sure you can dedicate enough time to maintain this
>>>>>> resources in the active state.
>>>>>>
>>>>>> Personal experience: In Jenkins RU we use Twitter (@jenkins_ru
>>>>>> <https://twitter.com/jenkins_ru>) but it is not that effective,
>>>>>> because it is just time consuming to track and repost content (tip: I 
>>>>>> will
>>>>>> appreciate contributions!). We also have a localized Gitter channel
>>>>>> <https://gitter.im/jenkinsci-ru/public> which is pretty active. But
>>>>>> I believe that we could have had more discussions if we were using a chat
>>>>>> popular Russia (Telegram is blocked there, but apparently it is the most
>>>>>> popular chat AFAICT). I'd guess WeChat would be a way to go in your case.
>>>>>>
>>>>>> Best regards,
>>>>>> Oleg
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Sun, Aug 19, 2018 at 11:58 PM arch  wrote:
>>>>>>
>>>>>>> Good to see Jenkins community is growing quickly, Twitter is also a
>>>>>>> great and very popular platform.
>>>>>>> And I hope more and more Chinese people could involve into the
>>>>>>> Jenkins community, know what happened in the Jenkins community, clear 
>>>>>>> the
>>>>>>> way how to contribute. WeChat <https://en.wikipedia.org/wiki/WeChat> is
>>>>>>> very popular in China, almost every Chinese people are using WeChat, 
>>>>>>> maybe
>>>>>>> for personal life or work. I think maybe we can publish some messages or
>>>>>>> news into Enterprise WeChat
>>>>>>> <https://en.wikipedia.org/wiki/WeChat#Enterprise_WeChat>. We can
>>>>>>> think about syn

Re: Jenkins Localization Separation discuss

[arch]

Yes, once we get more localization plugins then add such page.

On Tue, Oct 2, 2018 at 7:52 PM Oleg Nenashev  wrote:

> I am fine with the proposed approach.
> There are some edge cases, but it should work well.
>
> At some point we could add "Localizations" page to the installation
> Wizard, if there are many such plugins created.
>
> BR, Oleg
>
> On Monday, October 1, 2018 at 3:26:46 PM UTC+2, Jesse Glick wrote:
>
>> On Sat, Sep 29, 2018 at 10:38 PM Rick  wrote:
>> > detect browse user-agent setting
>>
>> As far as I know this is how locale is normally taken into account in
>> Jenkins, so this proposal makes sense to me.
>>
> --
> 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-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/ae053767-73b1-4dba-b0e0-73d05c158de6%40googlegroups.com
> 
> .
> 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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAMM7nTFRdFyFDfAhKgT0O_-XCrb92dhrGpTNQwKpjT5Q24MeRA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins in Hacktoberfest 2018?

[arch]

I can help review Chinese localization pr. Thanks Oleg.

On Tue, Oct 2, 2018 at 8:27 AM R. Tyler Croy  wrote:

> (replies inline)
>
> On Mon, 01 Oct 2018, Oleg Nenashev wrote:
>
> > Hi all,
> >
> > We are live: https://jenkins.io/blog/2018/10/01/hacktoberfest/
> > Let the hacking commence!
>
>
> Excellent  work! Thanks for leading the charge Oleg, I'm looking forward to
> some fun hacking from everybody this month :)
>
>
>
> --
> GitHub:  https://github.com/rtyler
> Twitter: https://twitter.com/agentdero
>
> --
> 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-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/20181002002727.GJ28434%40grape.brokenco.de
> .
> 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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAMM7nTF_5B7KA-3OC3KdqeZAsqgWUCXQPJBcZBcYrQoPzAH_zA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Bad release

[arch]

Just release a new version?

On Mon, Oct 1, 2018 at 10:19 PM Jesse Glick  wrote:

> On Mon, Oct 1, 2018 at 8:20 AM pallen  wrote:
> > How do I remove a bad release from the Update Centre!
>
> If it is already in the hands of users, I think you need to “fix forward”.
>
> --
> 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-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr1GBjWNdseRVkXqieqrSBCYN0kk9FjKeFuWkHonuL-ddQ%40mail.gmail.com
> .
> 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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAMM7nTGULj_Rnf70E34HV05asq7B0CiO3_SwzAWzu12ZbanDUw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Bad release

[arch]

You could add an item into here
https://github.com/jenkins-infra/update-center2/blob/master/src/main/resources/artifact-ignores.properties
if
you are the owner of the plugin.

On Mon, Oct 1, 2018 at 8:20 PM pallen  wrote:

> Hi Guys,
>
> How do I remove a bad release from the Update Centre!
>
> p4-plugin 1.9.0
>
> Looks like a case-sensitivity Class Name refactor has messed up the
> Jenkins XML configuration.  Any tips on that too? or just reinstate the old
> class name?
>
> Kind regards,
> Paul
>
> --
> 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-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/685e0a06-e103-4cd6-9ae3-ee6e89659836%40googlegroups.com
> 
> .
> 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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAMM7nTGhzkYz0mRjH_nXpjz5DDXRVZQwm-JxSLt0TQSqXDEUcg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Growing community via a stronger Twitter presence

[arch]

How is it going?

On Thu, Aug 30, 2018 at 9:32 PM arch  wrote:

> There isn't any description of this in WeChat website. It just requires an
> organization number. We can try it. Or if you think it's ok then I can
> apply the account as the name of my company.
> Yes, we can't talk about policy in China.
>
> On Mon, Aug 20, 2018 at 7:43 AM Oleg Nenashev 
> wrote:
>
>> But there is one problem, only enterprise or organization can register.
>>> If we want to do this, we need Jenkins support.
>>>
>>
>> Jenkins has no legal entity, it leaves under umbrella of SPI
>> <https://www.spi-inc.org/>. I am not sure that Jenkins qualifies from
>> the legal PoV, even if such registration agreement is acceptable from the
>> project,s PoV (e.g. whether we can accept WeChat censorship
>> <https://qz.com/960948/what-happens-when-you-try-to-send-politically-sensitive-messages-on-wechat/>,
>> etc.). Could you provide a list of requirements to such organizations?
>>
>> BR, Oleg
>>
>> On Mon, Aug 20, 2018 at 12:40 AM arch  wrote:
>>
>>> I can handle this. Yeah, WeChat is the Chinese version Twitter. Everyone
>>> loves WeChat. Gitter is awesome. But just a few people to use it, we prefer
>>> WeChat. And the Enterprise WeChat is more official.
>>> But there is one problem, only enterprise or organization can register.
>>> If we want to do this, we need Jenkins support.
>>>
>>> On Mon, Aug 20, 2018 at 6:13 AM Oleg Nenashev 
>>> wrote:
>>>
>>>> Yes, having such resources would be a great help to promote the local
>>>> Jenkins communities and events. If you are interested to create them,
>>>> thumbs up! Just be sure you can dedicate enough time to maintain this
>>>> resources in the active state.
>>>>
>>>> Personal experience: In Jenkins RU we use Twitter (@jenkins_ru
>>>> <https://twitter.com/jenkins_ru>) but it is not that effective,
>>>> because it is just time consuming to track and repost content (tip: I will
>>>> appreciate contributions!). We also have a localized Gitter channel
>>>> <https://gitter.im/jenkinsci-ru/public> which is pretty active. But I
>>>> believe that we could have had more discussions if we were using a chat
>>>> popular Russia (Telegram is blocked there, but apparently it is the most
>>>> popular chat AFAICT). I'd guess WeChat would be a way to go in your case.
>>>>
>>>> Best regards,
>>>> Oleg
>>>>
>>>>
>>>>
>>>> On Sun, Aug 19, 2018 at 11:58 PM arch  wrote:
>>>>
>>>>> Good to see Jenkins community is growing quickly, Twitter is also a
>>>>> great and very popular platform.
>>>>> And I hope more and more Chinese people could involve into the Jenkins
>>>>> community, know what happened in the Jenkins community, clear the way how
>>>>> to contribute. WeChat <https://en.wikipedia.org/wiki/WeChat> is very
>>>>> popular in China, almost every Chinese people are using WeChat, maybe for
>>>>> personal life or work. I think maybe we can publish some messages or news
>>>>> into Enterprise WeChat
>>>>> <https://en.wikipedia.org/wiki/WeChat#Enterprise_WeChat>. We can
>>>>> think about sync with Twitter or addition from *Chinese Localization
>>>>> SIG <https://jenkins.io/sigs/chinese-localization/>. If anyone is
>>>>> interested in this proposal, please let me know. Thanks.*
>>>>>
>>>>> On Mon, Aug 20, 2018 at 2:52 AM Oleg Nenashev 
>>>>> wrote:
>>>>>
>>>>>> These two already exist.
>>>>>>>
>>>>>> Nice 2 know
>>>>>> Once Tweetdeck gets documented somewhere on Jenkins infra pages (e.g.
>>>>>> just a link to the JEP), I think it's fully ready to go.
>>>>>>
>>>>>> P.S: Maybe it's a bit off-topic, but probably we should change avatar
>>>>>> of the Twitter account. It still has a Jenkins 2.0 announcement image.
>>>>>>
>>>>>> On Friday, August 17, 2018 at 6:42:23 PM UTC+2, R Tyler Croy wrote:
>>>>>>>
>>>>>>> (replies inline)
>>>>>>>
>>>>>>> On Fri, 17 Aug 2018, Oleg Nenashev wrote:
>>>>>>>
>>>>>>> > I like the JEP draft in the current state.
>>>>>>> >
>>>&

Request to join security team

[arch]

Hi folks,
I'm interested in joining the security team. I've got 2FA enabled on
Github(username LinuxSuRen), signed the CLA. My Jenkins community username
is surenpi.

-- 
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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAMM7nTGjw5MHtkCxb5%3DHeYKx7R5vg4fEVGsUnuPBotSe1-i5_g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins in Hacktoberfest 2018?

[arch]

I'm planning a Beijing Jenkins Meetup.

On Thu, Sep 27, 2018 at 1:23 AM Matt Sicker  wrote:

> I like the idea. I've submitted it to the Chicago JAM to see if there's
> interest there.
>
> On Wed, Sep 26, 2018 at 4:53 AM Oleg Nenashev 
> wrote:
>
>> Hi all,
>>
>> There will be a Hacktoberfest this year. We participated in 2017, and we
>> have got around 20 unique contributors. I propose the following:
>>
>>- Announce the event, process is similar to 2017
>>   - Announcement: https://jenkins.io/blog/2017/10/06/hacktoberfest/
>>   - Introduce a better way to report changes
>>   - Hacktoberfest requires labels
>>   - Last year we were using a @hacktoberfest group mention, but it
>>   requires a person to be a member of the org (Jenkins or Jenkins Infra).
>>   Last year we ended up running GitHub queries
>>   - I would propose to use jenkins/jenkins Gitter as a backup channel
>>   - Invite meetup organizers to run local hackfest events
>>   - I am planning a Swiss Jenkins Meetup
>>   - Day of Jenkins [as code] also has a hackathon within the
>>   timeframe
>>   - We could do something during DevOps World | Jenkins World on Oct
>>   22. Ready to run it if somebody is interested
>>
>> WDYT? No budget required, but we could send some Jenkins swag to top
>> contributors
>>
>> Best regards, Oleg
>>
>> --
>> 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-dev+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-dev/84d2edd1-dccb-4de5-831a-668c99290abf%40googlegroups.com
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
> --
> Matt Sicker
> Software Engineer, CloudBees
>
> --
> 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-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/CAEot4oyu0mbqHjmONwH%2BWsj%2BgzRjDXhWx-qD39zAr7k3rw%3D%2Bhw%40mail.gmail.com
> 
> .
> 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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAMM7nTHRW4NUbUaS3Tb3QugomQSqYCqsEgSfy04yizGmdk5ocA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins participation in Outreachy

[arch]

I'd love to participate.

On Wed, Sep 26, 2018 at 4:55 AM R. Tyler Croy  wrote:

> (replies inline)
>
> On Tue, 25 Sep 2018, Tracy Miranda wrote:
>
> > Hi all,
> >
> > Not sure if folks have come across the Outreachy
> >  programme but it is one of the leading
> > initiatives around for getting more marginalised folks involved with open
> > source projects. It is similar overall to Google Summer of Code, except
> > relies on external contributions i.e. not funded by Google.
>
>
> Thanks for taking this on Tracy, Outreachy is a good organization for us to
> work with for sure!
>
> With the bugdet request for $6500, does that cover one intern or what
> multiple
> of interns?
>
>
> Either way, I think this is a great idea and will be crossing my fingers
> that
> we'll be able to fund some talented new contributors to the project.
>
>
> --
> 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-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/20180925205500.GA15160%40grape.brokenco.de
> .
> 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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAMM7nTFt8D7SEPRSkO9Jok-dfxXj6prE4d27Uf-Se5AnXUsP9g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Request permission for plugins

[arch]

Got it. I will add more details to it. And Thank for Liam Newman and all
people's efforts.

On Wed, Sep 26, 2018 at 8:47 AM Liam Newman  wrote:

> I've made this JEP-216 Draft so that it can be referenced in discussions
> and form the prototype, but as noted it needs quite a bit of work.
>
> On Tuesday, August 28, 2018 at 7:01:57 AM UTC-7, Daniel Beck wrote:
>
>>
>>
>> > On 28. Aug 2018, at 15:10, Oleg Nenashev  wrote:
>> >
>> > I can imagine a local company which installs a single localization
>> plugin
>> > That's why I lean towards having separate plugins for each locale.
>>
>> … and an aggregator. It's free. Only needs updates whenever a locale
>> plugin is added or removed. I really don't understand the resistance here.
>>
>> > Depends on the installation logic implementation, but generally "yes".
>>
>> Which installation logic would you consider to be supported (i.e. we
>> wouldn't close a related Jira issue immediately) and does not install
>> whatever is available on your chosen update site? CLI command, UI, even
>> install-plugins.sh and configuration-as-code plugin install the newest
>> available release of dependencies.
>>
>> --
> 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-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/8a4cc4fa-0eb6-43d3-8571-77b4dac2805c%40googlegroups.com
> 
> .
> 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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAMM7nTFKzfMqdVN3JzNX74AEbp9N-6ts6jy6fdV_hL0ObZ3d7A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: JEP for Enhanced Travel Grant Proposal

[arch]

+1

On Sat, Sep 15, 2018 at 12:02 AM Tracy Miranda 
wrote:

> Hi all,
>
> Following on from discussions at a past Governance meeting[1] I have
> created a JEP that proposes enhancements to the Travel Grant program.
> Please take a look at the PR here
> https://github.com/jenkinsci/jep/pull/202 and any feedback will be
> welcome.
>
> Regards,
> Tracy
>
>
>
> http://meetings.jenkins-ci.org/jenkins-meeting/2018/jenkins-meeting.2018-08-01-18.00.log.html
>
> --
> 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-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/CACTaz6p_q65nUX9iYvtoZk7FTGpJdFMe%2BDWxd1Y7cegWKy3shw%40mail.gmail.com
> 
> .
> 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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAMM7nTHaNsU4t2nuErw03%3D6%2B9TERQynFUkOuH7TEffq2vY83bw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Growing community via a stronger Twitter presence

[arch]

There isn't any description of this in WeChat website. It just requires an
organization number. We can try it. Or if you think it's ok then I can
apply the account as the name of my company.
Yes, we can't talk about policy in China.

On Mon, Aug 20, 2018 at 7:43 AM Oleg Nenashev 
wrote:

> But there is one problem, only enterprise or organization can register. If
>> we want to do this, we need Jenkins support.
>>
>
> Jenkins has no legal entity, it leaves under umbrella of SPI
> <https://www.spi-inc.org/>. I am not sure that Jenkins qualifies from the
> legal PoV, even if such registration agreement is acceptable from the
> project,s PoV (e.g. whether we can accept WeChat censorship
> <https://qz.com/960948/what-happens-when-you-try-to-send-politically-sensitive-messages-on-wechat/>,
> etc.). Could you provide a list of requirements to such organizations?
>
> BR, Oleg
>
> On Mon, Aug 20, 2018 at 12:40 AM arch  wrote:
>
>> I can handle this. Yeah, WeChat is the Chinese version Twitter. Everyone
>> loves WeChat. Gitter is awesome. But just a few people to use it, we prefer
>> WeChat. And the Enterprise WeChat is more official.
>> But there is one problem, only enterprise or organization can register.
>> If we want to do this, we need Jenkins support.
>>
>> On Mon, Aug 20, 2018 at 6:13 AM Oleg Nenashev 
>> wrote:
>>
>>> Yes, having such resources would be a great help to promote the local
>>> Jenkins communities and events. If you are interested to create them,
>>> thumbs up! Just be sure you can dedicate enough time to maintain this
>>> resources in the active state.
>>>
>>> Personal experience: In Jenkins RU we use Twitter (@jenkins_ru
>>> <https://twitter.com/jenkins_ru>) but it is not that effective, because
>>> it is just time consuming to track and repost content (tip: I will
>>> appreciate contributions!). We also have a localized Gitter channel
>>> <https://gitter.im/jenkinsci-ru/public> which is pretty active. But I
>>> believe that we could have had more discussions if we were using a chat
>>> popular Russia (Telegram is blocked there, but apparently it is the most
>>> popular chat AFAICT). I'd guess WeChat would be a way to go in your case.
>>>
>>> Best regards,
>>> Oleg
>>>
>>>
>>>
>>> On Sun, Aug 19, 2018 at 11:58 PM arch  wrote:
>>>
>>>> Good to see Jenkins community is growing quickly, Twitter is also a
>>>> great and very popular platform.
>>>> And I hope more and more Chinese people could involve into the Jenkins
>>>> community, know what happened in the Jenkins community, clear the way how
>>>> to contribute. WeChat <https://en.wikipedia.org/wiki/WeChat> is very
>>>> popular in China, almost every Chinese people are using WeChat, maybe for
>>>> personal life or work. I think maybe we can publish some messages or news
>>>> into Enterprise WeChat
>>>> <https://en.wikipedia.org/wiki/WeChat#Enterprise_WeChat>. We can think
>>>> about sync with Twitter or addition from *Chinese Localization SIG
>>>> <https://jenkins.io/sigs/chinese-localization/>. If anyone is interested in
>>>> this proposal, please let me know. Thanks.*
>>>>
>>>> On Mon, Aug 20, 2018 at 2:52 AM Oleg Nenashev 
>>>> wrote:
>>>>
>>>>> These two already exist.
>>>>>>
>>>>> Nice 2 know
>>>>> Once Tweetdeck gets documented somewhere on Jenkins infra pages (e.g.
>>>>> just a link to the JEP), I think it's fully ready to go.
>>>>>
>>>>> P.S: Maybe it's a bit off-topic, but probably we should change avatar
>>>>> of the Twitter account. It still has a Jenkins 2.0 announcement image.
>>>>>
>>>>> On Friday, August 17, 2018 at 6:42:23 PM UTC+2, R Tyler Croy wrote:
>>>>>>
>>>>>> (replies inline)
>>>>>>
>>>>>> On Fri, 17 Aug 2018, Oleg Nenashev wrote:
>>>>>>
>>>>>> > I like the JEP draft in the current state.
>>>>>> >
>>>>>> > IMHO it would be great to extend Infrastructure Requirements a bit:
>>>>>> >
>>>>>> >- A new Tweetdeck account is created
>>>>>> >- Jenkins INFRA team has access to Tweetdeck so it can handle
>>>>>> the
>>>>>> >requests if needed
>>>>>>
>>>>>>
>>

Re: Request permission for plugins

[arch]

I wonder how many people plan to separate their localization resource
files. If there is not so much, I suggest that keep other languages files
in current place.

On Tue, Aug 28, 2018 at 9:17 PM Jesse Glick  wrote:

> On Tue, Aug 28, 2018 at 9:10 AM Oleg Nenashev 
> wrote:
> > I would expect Incremental Tools to eventually simplify managing of
> aggregator plugins.
>
> How…? `incrementals-tools` does not seem related to me.
>
> I tend to agree that a single localization plugin would be simpler to
> manage in most respects. The release cycle could be weekly, monthly,
> on demand, whatever; and as I noted, GitHub has features that make it
> easy enough to request particular people review PRs touching
> particular subdirectories or other filename patterns. A single
> repository also provides the natural home for related tooling, such as
> scripts to check for missing or stale localizations.
>
> --
> 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-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr1PUoC2Jk3H0zntkAtHCLruHUHUS%3DT-55uDOF_Z-p7nUw%40mail.gmail.com
> .
> 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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAMM7nTE5hSEumE0ZLp-rVjR3L2s2ov0jhRagLq%2BJKYPLsD3opg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Request permission for plugins

[arch]

Thanks for your checklist and suggestion. That's really great.

On Tue, Aug 28, 2018 at 6:57 PM Jesse Glick  wrote:

> On Tue, Aug 28, 2018 at 2:34 AM arch  wrote:
> > Agree with this solution. And I give a prototype plugin.
> https://github.com/LinuxSuRen/localization-plugin
>
> Nice, did you get this to work already? There are a few things to check:
>
> · core vs. plugin localization
> · `Messages_zh_CN.properties` (so `Messages.some_key()` Java calls)
> · `*_zh_CN.properties` (localization from Jelly views like `index`)
> · `help*_zh_CN.html` if these are even supported (I cannot remember
> offhand)
> · `mvn hpi:run` incl. live reloading after saving a resource in the source
> tree
> · effectiveness in a `$JENKINS_HOME/plugins/*.jpi` (this is a
> different class loading mode)
>
> > Do I need to create a ticket on JIRA or just everyone take a look at
> this project?
>
> I think this would make a good JEP describing what you propose to do
> and making sure other localizers are ready to coöperate, since this
> clearly goes beyond a usual plugin HOSTING request: it would involve
> _removing_ localization resources from lots of existing repositories,
> adjusting the default plugin list in the Setup wizard, and maybe some
> infrastructure tasks. And there are some details that need to be
> settled such as the plugin code names (which cannot be changed after
> publishing): rather than, say, `chinese-localization` I might suggest
> something more regular like `localization-zh_CN`.
>
> --
> 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-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr1YJ0BuDZ6mXAKO%2BUFkG0tFiun6W-9GpWSfxVyUr5%2BZPw%40mail.gmail.com
> .
> 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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAMM7nTFX5My%3D1ADt_tb0ySVVO254cF%3DhE0SfKOxXMLfvHYytNg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Request permission for plugins

[arch]

Agree with this solution. And I give a prototype plugin.
https://github.com/LinuxSuRen/localization-plugin
Do I need to create a ticket on JIRA or just everyone take a look at this
project?

On Tue, Aug 28, 2018 at 12:57 AM Jesse Glick  wrote:

> On Mon, Aug 27, 2018 at 10:01 AM Slide  wrote:
> > I would hope that you would be able to localize in a single "Chinese
> Localization" plugin.
>
> Or, perhaps, a single plugin for _all_ localizations. For example,
> something like
>
>
> jenkinsci/l10n-plugin/src/main/resources/org/jenkinsci/plugins/workflow/cps/CpsFlowDefinition/config_zh_CN.properties
>
> but maybe there needs to be one top-level subdirectory per locale¹, or
> some directory structure indicating plugin name, etc. etc.
>
> > I am not sure how that would work myself
>
> So far I and other Jenkins core developers have just been throwing out
> ideas. Acc. to things Daniel said, there probably need to be some
> minor changes to core to make it work.
>
>
> ¹Would be useful to use
> https://help.github.com/articles/about-codeowners/#codeowners-syntax
> to associate each localization with a set of usernames.
>
> --
> 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-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr0pN9PyqzhjG03oKWNPtOCDRR7CkM6xUQ61g51cPCJDMQ%40mail.gmail.com
> .
> 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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAMM7nTH4fazLwqaxPWrdiwDPJwa72dGoo_o%2BP6N9qVRwfvWSgg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Request permission for plugins

[arch]

OK, I can try to do it as we discuss.

On Mon, Aug 27, 2018 at 10:00 PM Slide  wrote:

> I would hope that you would be able to localize in a single "Chinese
> Localization" plugin. I am not sure how that would work myself, but I think
> that would be better than plugin-a-zh, plugin-b-zh, etc.
>
> On Mon, Aug 27, 2018 at 6:56 AM arch  wrote:
>
>> For example, I want to localize five plugins(A, B, C, D, E). You mean I
>> need to create five repos, A-zh, B-zh, C-zh, D-zh, E-zh?
>>
>> On Mon, Aug 27, 2018 at 9:28 PM Jesse Glick  wrote:
>>
>>> On Mon, Aug 27, 2018 at 5:33 AM arch  wrote:
>>> > We could create a Chinese Localization plugin for Jenkins core. But we
>>> can't create every localization for other plugins. Right? Because there are
>>> lots of them.
>>>
>>> I do not see a problem here. If you are working on the Chinese
>>> localization, or Albanian or whatever, you get to decide how much you
>>> wish to localize. If you have time to localize every plugin listed in
>>> the Setup wizard and then some others, great. If you can only manage
>>> some of the most commonly seen screens (and maybe only part of core),
>>> so be it. You need to balance the desire for completeness with
>>> available resources, and keep in mind that as code is changed and
>>> refactored over time there will be some new message keys and some
>>> obsolete ones, so there is an ongoing cost proportional to the size of
>>> the localization.
>>>
>>> --
>>> 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-dev+unsubscr...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr3DoWyNdO%2BoacHxNx7vO%3DqpUV-xj8XjbFZM6fuTKCvj_g%40mail.gmail.com
>>> .
>>> 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 jenkinsci-dev+unsubscr...@googlegroups.com.
>>
> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-dev/CAMM7nTHZ4MX5eK4%3DY2yzHHhMQerpHVgudE28bThHsM54VVxbFg%40mail.gmail.com
>> <https://groups.google.com/d/msgid/jenkinsci-dev/CAMM7nTHZ4MX5eK4%3DY2yzHHhMQerpHVgudE28bThHsM54VVxbFg%40mail.gmail.com?utm_medium=email_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 jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/CAPiUgVcAOoAUZJ19obMx-zO6YD7KdgiQ6zEB-oqKo3UCXu7iew%40mail.gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/CAPiUgVcAOoAUZJ19obMx-zO6YD7KdgiQ6zEB-oqKo3UCXu7iew%40mail.gmail.com?utm_medium=email_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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAMM7nTGObLOSE8s6_t4yvj62%2BYoaA%3DaSJt-aYLkGHzjgHKaaeg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Request permission for plugins

[arch]

For example, I want to localize five plugins(A, B, C, D, E). You mean I
need to create five repos, A-zh, B-zh, C-zh, D-zh, E-zh?

On Mon, Aug 27, 2018 at 9:28 PM Jesse Glick  wrote:

> On Mon, Aug 27, 2018 at 5:33 AM arch  wrote:
> > We could create a Chinese Localization plugin for Jenkins core. But we
> can't create every localization for other plugins. Right? Because there are
> lots of them.
>
> I do not see a problem here. If you are working on the Chinese
> localization, or Albanian or whatever, you get to decide how much you
> wish to localize. If you have time to localize every plugin listed in
> the Setup wizard and then some others, great. If you can only manage
> some of the most commonly seen screens (and maybe only part of core),
> so be it. You need to balance the desire for completeness with
> available resources, and keep in mind that as code is changed and
> refactored over time there will be some new message keys and some
> obsolete ones, so there is an ongoing cost proportional to the size of
> the localization.
>
> --
> 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-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr3DoWyNdO%2BoacHxNx7vO%3DqpUV-xj8XjbFZM6fuTKCvj_g%40mail.gmail.com
> .
> 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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAMM7nTHZ4MX5eK4%3DY2yzHHhMQerpHVgudE28bThHsM54VVxbFg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Request permission for plugins

[arch]

Commit access is just for convenience. But I think that separate
localization resources are not so good for users experience, maybe it's
pretty simple. When I first install Jenkins on my computer, I wish I can
get a localization page instead of choosing languages plugin.

On Mon, Aug 27, 2018 at 3:12 AM Oleg Nenashev 
wrote:

> This would certainly be the physically simplest option, if it works.
>> Depends on whether code looking for locale variants checks the
>> `UberClassLoader`, or the defining loader of some plugin.
>>
> In the worst case, it is possible to use localization overrides via an
> engine similar to the Translation Assistance plugin.
>
> https://github.com/jenkinsci/translation-plugin/blob/master/src/main/java/hudson/plugins/translation/L10nDecorator.java
>
>
>> That said, I expect more problems from granting commit access to plugin
>> repos to merge localization changes, no matter how well intentioned and
>> executed, while we consider plugins as largely independent subprojects.
>>
> +1,
>
> On Monday, August 20, 2018 at 5:27:29 PM UTC+2, Jesse Glick wrote:
>
>> On Mon, Aug 20, 2018 at 9:24 AM Daniel Beck  wrote:
>> > Neither Messages nor Jelly view resources work. Only 'help files' work.
>>
>> OK. Probably relatively easy to fix.
>>
> --
> 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-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/b5fad2ae-d600-439a-b502-56663a4fcf60%40googlegroups.com
> 
> .
> 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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAMM7nTF9wdXVHu92re3XkBhxpAHtMt_PBo_Sjtkhej_gyRSC6A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: unit test error: java.lang.IllegalAccessError: tried to access method

[arch]

Yes, I just resolved this. The problem accused by the dependency of structs.

On Tue, Aug 21, 2018 at 10:19 PM Jesse Glick  wrote:

> On Tue, Aug 21, 2018 at 3:59 AM Rick  wrote:
> > When I run the JUnit test, got an errors, like this:
> >
> > java.lang.IllegalAccessError: tried to access method
> org.jenkinsci.plugins.structs.describable.DescribableModel.of(Ljava/lang/Class;)Lorg/jenkinsci/plugins/structs/describable/DescribableModel;
> from class org.jenkinsci.plugins.workflow.cps.DSL
> > at org.jenkinsci.plugins.workflow.cps.DSL.parseArgs(DSL.java:460)
>
> Most likely you are using mismatched plugin versions, typically
> visible (when using reasonably recent versions of Jenkins) by some
> earlier warnings about some plugins being unloadable for dependency
> reasons. If your parent POM is set to a reasonably recent version, you
> should get a more straightforward build error much earlier, in the
> `validate` phase.
>
> --
> 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-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr0PcqeQYAN-6yjUxas1WYHDy%3Di4tOMj7vFRaiqsviUFNg%40mail.gmail.com
> .
> 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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAMM7nTHdULK7rDcmq5DtoG0OG8xUn6Obbg7f3%2B%2BU2eSjg1V%2B0A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: default container in Kubernetes plugin

[arch]

ok, do I need create a ticket in
https://issues.jenkins-ci.org/secure/Dashboard.jspa first?

On Tue, Aug 21, 2018 at 6:57 PM Carlos Sanchez  wrote:

> sounds good to me
>
> On Tue, Aug 21, 2018 at 12:38 PM arch  wrote:
>
>> Yes, I get your point. So I suggest offer a UI option, and let end users
>> make choice.
>>
>> On Tue, Aug 21, 2018 at 6:34 PM Carlos Sanchez  wrote:
>>
>>> the problem is how to know when you want a container be a default, you
>>> would need to pass it as an option in the pod template definition
>>>
>>> On Tue, Aug 21, 2018 at 12:59 AM Rick  wrote:
>>>
>>>> When I configure a pod template with java container. Then run a shell
>>>> script in pipeline, it will cause an error that can't find command java. So
>>>> I must specify the container as java first.
>>>> I suggest that the java container should be the default container
>>>> instead of jnlp. Any feedback is thankful, welcome 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-dev+unsubscr...@googlegroups.com.
>>>> To view this discussion on the web visit
>>>> https://groups.google.com/d/msgid/jenkinsci-dev/15e65662-377e-41d3-8ee9-9177c8a044e1%40googlegroups.com
>>>> <https://groups.google.com/d/msgid/jenkinsci-dev/15e65662-377e-41d3-8ee9-9177c8a044e1%40googlegroups.com?utm_medium=email_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 jenkinsci-dev+unsubscr...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/jenkinsci-dev/CALHFn6PcDHb6mD5S8PE069z141h_MFi1ncLdhWrdxb73okLMsQ%40mail.gmail.com
>>> <https://groups.google.com/d/msgid/jenkinsci-dev/CALHFn6PcDHb6mD5S8PE069z141h_MFi1ncLdhWrdxb73okLMsQ%40mail.gmail.com?utm_medium=email_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 jenkinsci-dev+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-dev/CAMM7nTGws%2Bjh%2BZVuxEY4rU4sY8q%3DW41nTWcxUJnBq9CuTM3G3Q%40mail.gmail.com
>> <https://groups.google.com/d/msgid/jenkinsci-dev/CAMM7nTGws%2Bjh%2BZVuxEY4rU4sY8q%3DW41nTWcxUJnBq9CuTM3G3Q%40mail.gmail.com?utm_medium=email_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 jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/CALHFn6NncdK-%3DNUXQmbNb4CJ6UVu%2BquBb%2B20XoFLBTUiACAbJQ%40mail.gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/CALHFn6NncdK-%3DNUXQmbNb4CJ6UVu%2BquBb%2B20XoFLBTUiACAbJQ%40mail.gmail.com?utm_medium=email_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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAMM7nTG%2BtupG5mWpJ%2Bme%2BNECx0s%3DO%2BKaj9Se-5v2dxipru-Y6Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: default container in Kubernetes plugin

[arch]

Yes, I get your point. So I suggest offer a UI option, and let end users
make choice.

On Tue, Aug 21, 2018 at 6:34 PM Carlos Sanchez  wrote:

> the problem is how to know when you want a container be a default, you
> would need to pass it as an option in the pod template definition
>
> On Tue, Aug 21, 2018 at 12:59 AM Rick  wrote:
>
>> When I configure a pod template with java container. Then run a shell
>> script in pipeline, it will cause an error that can't find command java. So
>> I must specify the container as java first.
>> I suggest that the java container should be the default container instead
>> of jnlp. Any feedback is thankful, welcome 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-dev+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-dev/15e65662-377e-41d3-8ee9-9177c8a044e1%40googlegroups.com
>> 
>> .
>> 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 jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/CALHFn6PcDHb6mD5S8PE069z141h_MFi1ncLdhWrdxb73okLMsQ%40mail.gmail.com
> 
> .
> 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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAMM7nTGws%2Bjh%2BZVuxEY4rU4sY8q%3DW41nTWcxUJnBq9CuTM3G3Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Growing community via a stronger Twitter presence

[arch]

I can handle this. Yeah, WeChat is the Chinese version Twitter. Everyone
loves WeChat. Gitter is awesome. But just a few people to use it, we prefer
WeChat. And the Enterprise WeChat is more official.
But there is one problem, only enterprise or organization can register. If
we want to do this, we need Jenkins support.

On Mon, Aug 20, 2018 at 6:13 AM Oleg Nenashev 
wrote:

> Yes, having such resources would be a great help to promote the local
> Jenkins communities and events. If you are interested to create them,
> thumbs up! Just be sure you can dedicate enough time to maintain this
> resources in the active state.
>
> Personal experience: In Jenkins RU we use Twitter (@jenkins_ru
> <https://twitter.com/jenkins_ru>) but it is not that effective, because
> it is just time consuming to track and repost content (tip: I will
> appreciate contributions!). We also have a localized Gitter channel
> <https://gitter.im/jenkinsci-ru/public> which is pretty active. But I
> believe that we could have had more discussions if we were using a chat
> popular Russia (Telegram is blocked there, but apparently it is the most
> popular chat AFAICT). I'd guess WeChat would be a way to go in your case.
>
> Best regards,
> Oleg
>
>
>
> On Sun, Aug 19, 2018 at 11:58 PM arch  wrote:
>
>> Good to see Jenkins community is growing quickly, Twitter is also a great
>> and very popular platform.
>> And I hope more and more Chinese people could involve into the Jenkins
>> community, know what happened in the Jenkins community, clear the way how
>> to contribute. WeChat <https://en.wikipedia.org/wiki/WeChat> is very
>> popular in China, almost every Chinese people are using WeChat, maybe for
>> personal life or work. I think maybe we can publish some messages or news
>> into Enterprise WeChat
>> <https://en.wikipedia.org/wiki/WeChat#Enterprise_WeChat>. We can think
>> about sync with Twitter or addition from *Chinese Localization SIG
>> <https://jenkins.io/sigs/chinese-localization/>. If anyone is interested in
>> this proposal, please let me know. Thanks.*
>>
>> On Mon, Aug 20, 2018 at 2:52 AM Oleg Nenashev 
>> wrote:
>>
>>> These two already exist.
>>>>
>>> Nice 2 know
>>> Once Tweetdeck gets documented somewhere on Jenkins infra pages (e.g.
>>> just a link to the JEP), I think it's fully ready to go.
>>>
>>> P.S: Maybe it's a bit off-topic, but probably we should change avatar of
>>> the Twitter account. It still has a Jenkins 2.0 announcement image.
>>>
>>> On Friday, August 17, 2018 at 6:42:23 PM UTC+2, R Tyler Croy wrote:
>>>>
>>>> (replies inline)
>>>>
>>>> On Fri, 17 Aug 2018, Oleg Nenashev wrote:
>>>>
>>>> > I like the JEP draft in the current state.
>>>> >
>>>> > IMHO it would be great to extend Infrastructure Requirements a bit:
>>>> >
>>>> >- A new Tweetdeck account is created
>>>> >- Jenkins INFRA team has access to Tweetdeck so it can handle the
>>>> >requests if needed
>>>>
>>>>
>>>> These two already exist.
>>>>
>>>>
>>>> >- The account is documented on the Jenkins INFRA wiki pages or
>>>> jenkins.io
>>>> >
>>>> > BR, Oleg
>>>> >
>>>> > On Tuesday, August 14, 2018 at 2:34:37 PM UTC+2, Tracy Miranda wrote:
>>>> > >
>>>> > > Thanks Tyler, Daniel & Mark for the feedback so far.
>>>> > >
>>>> > > I've updated the JEP based on this:
>>>> > > https://github.com/jenkinsci/jep/pull/176
>>>> > >
>>>> > > Please review and let me know any further thoughts.
>>>> > >
>>>> > > Tracy
>>>> > >
>>>> > > On Mon, Aug 13, 2018 at 8:22 PM, R. Tyler Croy >>> > > > wrote:
>>>> > >
>>>> > >>
>>>> > >> Following up on this thread, Tracy's taken the initiative to
>>>> create a
>>>> > >> good JEP
>>>> > >> describing the proposed process here:
>>>> > >> https://github.com/jenkinsci/jep/pull/175
>>>> > >>
>>>> > >>
>>>> > >> As the primary poster of @jenkinsci, I'm really looking forward to
>>>> > >> sharing some
>>>> > >> responsibilities with other passionate twitter/jenkins
>>>

Re: Growing community via a stronger Twitter presence

[arch]

Good to see Jenkins community is growing quickly, Twitter is also a great
and very popular platform.
And I hope more and more Chinese people could involve into the Jenkins
community, know what happened in the Jenkins community, clear the way how
to contribute. WeChat  is very
popular in China, almost every Chinese people are using WeChat, maybe for
personal life or work. I think maybe we can publish some messages or news
into Enterprise WeChat
. We can think
about sync with Twitter or addition from *Chinese Localization SIG
. If anyone is interested in
this proposal, please let me know. Thanks.*

On Mon, Aug 20, 2018 at 2:52 AM Oleg Nenashev 
wrote:

> These two already exist.
>>
> Nice 2 know
> Once Tweetdeck gets documented somewhere on Jenkins infra pages (e.g. just
> a link to the JEP), I think it's fully ready to go.
>
> P.S: Maybe it's a bit off-topic, but probably we should change avatar of
> the Twitter account. It still has a Jenkins 2.0 announcement image.
>
> On Friday, August 17, 2018 at 6:42:23 PM UTC+2, R Tyler Croy wrote:
>>
>> (replies inline)
>>
>> On Fri, 17 Aug 2018, Oleg Nenashev wrote:
>>
>> > I like the JEP draft in the current state.
>> >
>> > IMHO it would be great to extend Infrastructure Requirements a bit:
>> >
>> >- A new Tweetdeck account is created
>> >- Jenkins INFRA team has access to Tweetdeck so it can handle the
>> >requests if needed
>>
>>
>> These two already exist.
>>
>>
>> >- The account is documented on the Jenkins INFRA wiki pages or
>> jenkins.io
>> >
>> > BR, Oleg
>> >
>> > On Tuesday, August 14, 2018 at 2:34:37 PM UTC+2, Tracy Miranda wrote:
>> > >
>> > > Thanks Tyler, Daniel & Mark for the feedback so far.
>> > >
>> > > I've updated the JEP based on this:
>> > > https://github.com/jenkinsci/jep/pull/176
>> > >
>> > > Please review and let me know any further thoughts.
>> > >
>> > > Tracy
>> > >
>> > > On Mon, Aug 13, 2018 at 8:22 PM, R. Tyler Croy > > > > wrote:
>> > >
>> > >>
>> > >> Following up on this thread, Tracy's taken the initiative to create
>> a
>> > >> good JEP
>> > >> describing the proposed process here:
>> > >> https://github.com/jenkinsci/jep/pull/175
>> > >>
>> > >>
>> > >> As the primary poster of @jenkinsci, I'm really looking forward to
>> > >> sharing some
>> > >> responsibilities with other passionate twitter/jenkins contributors
>> :)
>> > >>
>> > >>
>> > >>
>> > >>
>> > >>
>> > >> --
>> > >> 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/20180813192211.GG17800%40grape.lasagna.io
>> > >> .
>> > >> 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 jenkinsci-de...@googlegroups.com.
>> > To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-dev/2bb34025-53f4-4469-8d23-23799706bf80%40googlegroups.com.
>>
>> > 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 jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/804d7ff3-c38c-4fc6-9b2e-49c94a9b6ae9%40googlegroups.com
> 
> .
> 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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAMM7nTGzvyRWwAufkXXM6Y3fVP6RrJK7sx4G-PY5GraZxH0QZQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Request permission for plugins

[arch]

>
> I understand the process. The question is we lack Chinese reviewer. And I
> want to be volunteer. Thanks.
>

-- 
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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAMM7nTF_kV%2B06pL3o71YyFEhPayoktmpCUUJvhtnFMfN2imzmw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.