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 <[email protected]> wrote: > I agree with the ideas to use [email protected]. 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 <[email protected]> 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 <[email protected]> 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 >>> [email protected]. 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 <[email protected]> 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 [email protected]. >>>>> 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&utm_source=footer> >>>>> . >>>>> For more options, visit https://groups.google.com/d/optout. >>>>> >>>> -- >>>> You received this message because you are subscribed to the Google >>>> Groups "Jenkins Developers" group. >>>> To unsubscribe from this group and stop receiving emails from it, send >>>> an email to [email protected]. >>>> To view this discussion on the web visit >>>> https://groups.google.com/d/msgid/jenkinsci-dev/CAMM7nTFfAF%3Ds8USwNSB-ncU4rCE98eNh%3D6sCZNH9MNeZcFjgCg%40mail.gmail.com >>>> <https://groups.google.com/d/msgid/jenkinsci-dev/CAMM7nTFfAF%3Ds8USwNSB-ncU4rCE98eNh%3D6sCZNH9MNeZcFjgCg%40mail.gmail.com?utm_medium=email&utm_source=footer> >>>> . >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>> -- >>> Kohsuke Kawaguchi >>> >> -- >> Kohsuke Kawaguchi >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Jenkins Developers" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/jenkinsci-dev/CAN4CQ4yxoM1%2B_sxfPiqNjHXpgrkV4soA9tm%3DEmH_v3__F7TYnQ%40mail.gmail.com >> <https://groups.google.com/d/msgid/jenkinsci-dev/CAN4CQ4yxoM1%2B_sxfPiqNjHXpgrkV4soA9tm%3DEmH_v3__F7TYnQ%40mail.gmail.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAMM7nTF415xArTqpyGVk4G%3DDojLmXcSQnpWr2sz%3De42-Mnuf1g%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
