Re: Request to adopt label-linked-jobs-plugin

['Gavin Mogan' via Jenkins Developers]

In general you don't need community involvement unless the original author
has abandoned it and isn't available.

If they want you to co maintain or fully take over they can do so via
GitHub and approve a pr in the permissions repo.

Gavin

On Wed., Dec. 9, 2020, 11:11 p.m. Rick,  wrote:

> Hi team,
>
> I'd like to adopt label-linked-jobs-plugin
> . I'm a maintainer
> of serval Jenkins plugins.
>
> According to the current maintainer of label-linked-jobs-plugin. He has
> not worked on this plugin for a few years. And he wishes this plugin goes
> to an adoption process. See
> https://github.com/jenkinsci/label-linked-jobs-plugin/pull/8#issuecomment-740323007
>
> Best,
> --
> Zhao Xiaojie (Rick)
> Blog: https://github.com/LinuxSuRen
> Twitter: https://twitter.com/suren69811254
>
> --
> 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/CAMM7nTFsFBYS_Sd1b50R7ouJ-0iXhWMF9gToshbOeJ4WHRp_wQ%40mail.gmail.com
> 
> .
>

-- 
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/CAG%3D_DuvtmEFcK8VQ8aaWzQ4Zha8tip3ZTsGSouauxm5yRy4ynw%40mail.gmail.com.

Request to adopt label-linked-jobs-plugin

[Rick]

Hi team,

I'd like to adopt label-linked-jobs-plugin
. I'm a maintainer
of serval Jenkins plugins.

According to the current maintainer of label-linked-jobs-plugin. He has not
worked on this plugin for a few years. And he wishes this plugin goes to an
adoption process. See
https://github.com/jenkinsci/label-linked-jobs-plugin/pull/8#issuecomment-740323007

Best,
-- 
Zhao Xiaojie (Rick)
Blog: https://github.com/LinuxSuRen
Twitter: https://twitter.com/suren69811254

-- 
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/CAMM7nTFsFBYS_Sd1b50R7ouJ-0iXhWMF9gToshbOeJ4WHRp_wQ%40mail.gmail.com.

Re: Jenkins ebook #1

[Alyssa Tong]

my apologies for not being clear. My ask - on page 2, at the end of the
letter where we currently have "The Jenkins Project" we would like the
names of the governance board members below this line.  As though this
letter is from the governance board. Hope that helps.

On Tue, Dec 8, 2020 at 3:18 PM 'Gavin Mogan' via Jenkins Developers <
jenkinsci-dev@googlegroups.com> wrote:

> Hi Alyssa,
>
> The attachment looks really good, but I'm not entirely sure what you're
> asking. Are you suggesting page 2 should read "Jenkins Governance Board -
> ...Names" instead of "The Jenkins Project"? or the entire document? Or
> something else?
>
> Gavin
>
> On Mon, Dec 7, 2020 at 10:53 AM Alyssa Tong  wrote:
>
>> Hi All
>>
>> As many of you know, in April of this year we began collecting Jenkins
>> user stories, and case studies, aka Jenkins is the Way
>> . With so many stories captured we've taken
>> a few of those stories and created an ebook, see attachment.  The ebook
>> consists of a welcome letter. The letter has been written up (in the
>> attachment) and I propose we have the board members (below) as authors of
>> this letter if that's ok. Pls let me know? Any edits to this document pls
>> do let me know that as well.
>>
>>- Gavin Mogan
>>- Marky Jackson
>>- Kohsuke Kawaguchi
>>- Ullrich Hafner
>>- Oleg Nenashev
>>
>> Note: the # of plugins and installations will be updated in the next
>> version of the ebook.
>>
>> Thank you,
>> alyssa
>>
>> --
>> 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/CAC9wNaz2J9bomTOTMdeoNYxk4rCPveOJLfX%3DLZ1s3mU-ny3PSw%40mail.gmail.com
>> 
>> .
>>
> --
> 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/CAG%3D_Duuq-RWjtx_USNFQrccnnVGRALTtvSiFB5S0g-sLo7SpmQ%40mail.gmail.com
> 
> .
>

-- 
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/CAC9wNaxPmqtQXf-HMAju6h12fYuovJxtDKCY_7oJH1kC7QVrjg%40mail.gmail.com.

Re: Jenkins Operator managed service name (sublicensing)

[Oleg Nenashev]

Hi Pawel,

We had a conversation at the Jenkins Governance meeting last week, and the 
consensus was that we are not ready to vote. Our consensus was that 
"VirtusLab Operator Service for Jenkins" or similar names represent a 
pretty much automatic approval while VirtusLab Jenkins Operator Service 
needs voting. I do not think there is an exceptional case, IMHO we should 
stick to the process. It is a +[1...-1] vote from the community members, 
with absolute majority vote in the mailing list and at the next governance 
meeting.

Given your explicit preference for "VirtusLab Jenkins Operator Service" , I 
think we should start the voting with target of concluding it next week. 
Fine with you?

Best regards,
Oleg Nenashev

On Monday, December 7, 2020 at 8:12:11 PM UTC+1 pdo...@virtuslab.com wrote:

> Hi Oleg 
>
> Not sure if this was already discussed. Of course if it is possible we 
> would definitely prefer *VirtusLab Jenkins Operator Service* as it 
> clearly indicates intent (it is Jenkins Operator - delivered as service; 
> given it is based on Jenkins Operator OSS project). However I do understand 
> we could only ask for charitable interpretation here.
>
> Is there anything we could do to be counted as exceptional case?
>
> On Tuesday, December 1, 2020 at 12:37:51 PM UTC+1 Oleg Nenashev wrote:
>
>> >  Your suggestions are very reasonable. I think *VirtusLab Jenkins 
>> Operator Service* might be a good name we could use.  
>>
>> Following the Linux Foundation trademark guidelines remains the 
>> preference IMO, e.g.  "VirtusLab Operator Service for Jenkins". Would it 
>> work for you? 
>> The suggested *VirtusLab Jenkins Operator Service* name technically may 
>> be approved by the Jenkins Governance Meeting, but it rather for 
>> exceptional cases in our current policy. Would be great to get feedback 
>> from others ahead of the meeting. 
>>
>> > Regarding the Azure Marketplace, is it worth starting to look at 
>> someone (guessing it would be the Governance Board?) starting to try and 
>> contact the vendors who are supplying the marketplace items to alert them 
>> that the names should really be changed (and then starting to look to 
>> enforce it later down the track)?
>>
>>
>>
>> On Monday, November 30, 2020 at 2:59:48 PM UTC+1 pdo...@virtuslab.com 
>> wrote:
>>
>>> Your suggestions are very reasonable. I think *VirtusLab Jenkins 
>>> Operator Service* might be a good name we could use.
>>>
>>> On Sunday, November 29, 2020 at 11:51:18 PM UTC+1 Richard Bywater wrote:
>>>
 I agree that I think use of a company name within the title is 
 appropriate if it's not part of a base Jenkins community offering. e.g. 
 Jenkins Operator Service might be ok for an official Jenkins community 
 offering of an Operator Service but not for an offering by a particular 
 company.

 Regarding the Azure Marketplace, is it worth starting to look at 
 someone (guessing it would be the Governance Board?) starting to try and 
 contact the vendors who are supplying the marketplace items to alert them 
 that the names should really be changed (and then starting to look to 
 enforce it later down the track)?

 Richard.

 On Mon, 30 Nov 2020 at 11:31, Oleg Nenashev  
 wrote:

> Hi Pawel,
>
> TBH I am not sure "Jenkins Operator Service" would be approved, it is 
> too generic. I would definitely hesitate voting for it. There is no 
> precedent of such name being approved before for product names, only for 
> community-focused events and : 
> https://www.jenkins.io/project/trademark/approved-usage/ . Before the 
> Linux Foundation trademark guidelines were adopted, the product names 
> commonly had the "COMPANY_NAME Jenkins Something" or the "Jenkins 
> Something 
> by COMPANY_NAME" naming pattern. It's probably something you could 
> consider.
>
> Feedback/suggestions from others would be appreciated.
>
> P.S: As we discussed a few months ago, product naming on public cloud 
> marketplaces is a mess at the moment: 
> https://azuremarketplace.microsoft.com/en-us/marketplace/apps?page=1=jenkins
>  
> . So we still need to maintain a balance in trademark sublicense reviews 
> so 
> that good faith requests do not create disadvantages compared to vendors 
> who do not submit trademark sublicense requests. Maybe a listing of 
> commercial offerings on our site could help with that (similar to 
> https://wiki.jenkins.io/display/JENKINS/Commercial+Support which 
> still needs to be moved to jenkins.io)
>
> BR, Oleg
>
> On Thursday, November 26, 2020 at 1:38:18 PM UTC+1 
> pdo...@virtuslab.com wrote:
>
>> You are right. In case of this name we would need to pursue the 
>> approval from Kubernetes organization. 
>>
>> If possible I think ideal name (from our perspective) would be *Jenkins 
>> Operator* *Service*. I