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 <o.v.nenas...@gmail.com> 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&step=3&lang=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 <k...@kohsuke.org> 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 <linux...@gmail.com> 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&utm_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-de...@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&utm_source=footer> >>>> . >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>> -- >>> 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 jenkinsci-de...@googlegroups.com. >> >> >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/jenkinsci-dev/CAN4CQ4xu0s7qMZUhx1LJrjKU5BtF2tc8kogsoE3K1e9fdxD6_w%40mail.gmail.com >>> <https://groups.google.com/d/msgid/jenkinsci-dev/CAN4CQ4xu0s7qMZUhx1LJrjKU5BtF2tc8kogsoE3K1e9fdxD6_w%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 jenkinsci-dev+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-dev/9fc4a631-95d6-46cc-8567-3a6e8709595e%40googlegroups.com > <https://groups.google.com/d/msgid/jenkinsci-dev/9fc4a631-95d6-46cc-8567-3a6e8709595e%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAMM7nTEzdvgyV5s62nBZK4jaX7SDVdsMazU3p724-0fULWs09g%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
