Re: Trademark sublicense request: TechMatrix Jenkins Support

[Oleg Nenashev]

Ack, thanks for the update!
We will update the trademark documentation accordingly.


On Mon, Oct 19, 2020 at 8:59 AM Yuji Tachibana 
wrote:

> Hello Oleg,
>
> >Please consider it confirmed.
> OK, we will publish a launch of Techmatrix Enterprise Support for Jenkins.
> Thank you very much for your understanding and quick response.
>
> Yuji
> 2020年10月16日金曜日 15:56:02 UTC+9 Oleg Nenashev:
>
>> Hello,
>>
>> I believe we discussed this option explicitly at the governance meeting.
>> Please consider it confirmed.
>>
>> Best regards,
>> Oleg
>>
>>
>> On Fri, Oct 16, 2020 at 2:45 AM Yuji Tachibana 
>> wrote:
>>
>>> Hello, Oleg
>>>
>>> Thank you for sharing the contents of board meeting.
>>> We would like to use the name  "TechMatrix Enterprise Support for
>>> Jenkins"
>>> After your final confirmation, we will announce to its launch to our
>>> market.
>>>
>>> Best Regards,
>>> Yuji
>>>
>>> 2020年10月16日金曜日 5:40:06 UTC+9 Oleg Nenashev:
>>>
 Hello Yuji,

 Just to summarize the yesterday's Governance Board review:

- We recommend using the Linux Foundation trademark usage guidelines
. "TechMatrix
Enterprise Support for Jenkins" or a similar name are approved as long 
 as
the naming pattern is followed.
- Based on the previous precedent, we approve "TechMatrix Jenkins
Support" should TechMatrix have a preference to use this trademark
- The final name choice is up to TechMatrix. Please let us know
about your final decision in this thread.

 Regarding the trademarks discussion in general:

- At the Governance meeting we approved further adoption of the
Linux Foundation trademark guidelines, with pre-approved patterns.
- We reviewed a few examples on public cloud Marketplaces, and we
confirm that many distribution vendors have neither requested a 
 trademark
sublicense nor following the Linux Foundation naming patterns. The
consensus is that we are okay with historical distributions having clear
distinctions in the name (“E.g. Jenkins distribution by AcmeCorp”).
Final policy is to be defined during the trademark policy renewal.

 Best regards,
 Oleg

 On Thursday, October 15, 2020 at 2:55:50 PM UTC+2 Arnaud Héritier wrote:

> +1 too for "TechMatrix Enterprise Support for Jenkins" or  "TechMatrix
> Jenkins Support"
> I agree that it could be good to follow Linux FDN convention as Yuji
> is ok with it
>
> On Thu, Oct 15, 2020 at 2:36 PM Yuji Tachibana 
> wrote:
>
>> Thank you for checking my request and sorry for not responding soon.
>> I'm totally fine with using "TechMatrix Enterprise Support for
>> Jenkins" under the trademark policy of Linux Foundation.
>> Please share the result, when the decision is made by board meeting,
>>
>> Best Regards,
>> Yuji
>>
>> 2020年10月14日水曜日 7:40:47 UTC+9 alytong13:
>>
>>> +1 on the approval and the Linux FDN suggested naming convention.
>>>
>>> On Tue, Oct 13, 2020 at 2:49 PM Oleg Nenashev 
>>> wrote:
>>>
 > It would be good to start following the Linux FDN for these
 things.

 I will add it to the tomorrow's agenda

 On Tuesday, October 13, 2020 at 11:46:59 PM UTC+2 slide wrote:

> Agreed on the approval and possible recommendations. It would be
> good to start following the Linux FDN for these things.
>
> On Tue, Oct 13, 2020 at 2:22 PM Oleg Nenashev 
> wrote:
>
>> Hello,
>>
>> It worth mentioning that the "CompanyName Jenkins Support" naming
>> pattern has been approved a few years ago for CloudBees Jenkins 
>> Support:
>> https://wiki.jenkins.io/display/JENKINS/Approved+Trademark+Usage
>> . Based on this precedent, I am +1 for approving the current 
>> trademark
>> request for "TechMatrix Jenkins Support".
>>
>> My personal preference would be to follow the Linux Foundation
>> trademark usage patterns
>> ,. In such case
>> the name would be "TechMatrix Support for Jenkins", "TechMatrix 
>> Enterprise
>> Support for Jenkins" or something like that.
>>
>> Best regards,
>> Oleg Nenashev
>>
>> On Friday, October 9, 2020 at 4:51:06 PM UTC+2
>> mind.the...@gmail.com wrote:
>>
>>> This is Yuji from TechMatrix, a distributor of CloudBees
>>> products in Japan
>>>
>>>
>>>
>>> I'd like to request the permission to use the following name
>>> that uses "Jenkins" in it:
>>>
>>> "TechMatrix Jenkins Support"
>>>
>>>
>>>
>>> The following is 

Re: Events Officer Role

[Alyssa Tong]

thank you so much Victor :)

On Mon, Oct 19, 2020 at 1:47 AM Victor Martinez <
victormartinezru...@gmail.com> wrote:

> Thanks Alyssa for all these years of hard work for the Jenkins community!!
> <3
>
> On Friday, 2 October 2020 at 19:13:52 UTC+1 alytong13 wrote:
>
>> Hi All,
>>
>>
>> As I've been Events Officer for quite some time now, I would like to step
>> down from this role at the end of my tenure on 3 December 2020. I feel
>> giving others a chance to fulfill this role will bring new insights and
>> creativity.
>>
>> I will continue to contribute to the Jenkins project by ways of
>> participation in the Advocacy and Outreach SIG, drive the Jenkins is the
>> Way initiative, assist the new Events Officer in the transition and in
>> events related activities.
>>
>> 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/1355b57e-38cd-4183-8b58-f16b7f911685n%40googlegroups.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/CAMBsfbtvjKr%3D8L1wz8WFvmfUh0DAvUcA98tOq-%2B1oj%3DOBa0cJQ%40mail.gmail.com.

Re: Proposal: Automating dependency management for repositories inside the jenkinsci org

[Ullrich Hafner]

I think that this can be done globally: for each repository a PR will be 
generated. So in order to finish the transition the repo owner still needs to 
merge the PR. However, I do not find a button to run this for all repositories 
:-(

> Am 19.10.2020 um 16:44 schrieb Jesse Glick :
> 
> On Mon, Oct 19, 2020 at 7:57 AM Baptiste Mathus  wrote:
>> If anybody still has the previous configuration, and would like to get an 
>> automated PR, please let me/us know and I can request it.
> 
> I would certainly want this but have no idea which repositories I
> might “own” which are configured with the preview app. Is there any
> harm in just requesting the conversion PR for every remaining repo?
> 
> -- 
> 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/CANfRfr3Z_UnaBsWpg%2BwXhut7YOvZUG9X8dsTB-7EXfouOqypvA%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/7EE25BD9-977B-4D6A-A029-C8F1063DE0B4%40gmail.com.

Re: Proposal: Automating dependency management for repositories inside the jenkinsci org

[Jesse Glick]

On Mon, Oct 19, 2020 at 7:57 AM Baptiste Mathus  wrote:
> If anybody still has the previous configuration, and would like to get an 
> automated PR, please let me/us know and I can request it.

I would certainly want this but have no idea which repositories I
might “own” which are configured with the preview app. Is there any
harm in just requesting the conversion PR for every remaining repo?

-- 
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/CANfRfr3Z_UnaBsWpg%2BwXhut7YOvZUG9X8dsTB-7EXfouOqypvA%40mail.gmail.com.

Re: APIs to expose build parameters to trigger builds

[Jesse Glick]

On Sat, Oct 17, 2020 at 11:49 PM ikedam  wrote:
> REST API looks expected to use to expose configurations, that is, to expose 
> static attributes rather than calculated results.

Not really. There is an export API from builds (`Run.getApi`), for
example, which is clearly dynamic.

> REST API is accessible from users with Item/READ permissions. The current 
> version of extensible-choice expose calculated values only to users with 
> Item/BUILD or Item/CONFIGURE permissions.

If there is some security reason to restrict information, simply guard
the `@Exported` getter with a `hasPermission` call, returning an empty
result for users without permission.

Note that this would affect other uses of the getter, which is usually
what you want: the caller is either internal, running as `ACL.SYSTEM`,
or is actually part of an authenticated request, in which case the
permission check is appropriate. If you really must retain the
original behavior, add a new getter with an arbitrary name which is
marked `@Restricted(DoNotUse.class) @Exported(name =
"originalPropertyName")` and does the permission check.

-- 
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/CANfRfr1J_NKoZbkQdOnQ9Qfknc7-3fR%3DAKWLHUadiGV3%3DHzuLg%40mail.gmail.com.

Re: Proposal: Automating dependency management for repositories inside the jenkinsci org

[Baptiste Mathus]

Hi all,

FYI, as I was using the Dependabot admin UI, I just requested Dependabot to
file automated PRs on a number of plugins:

https://github.com/pulls?q=is%3Aopen+is%3Apr+author%3Aapp%2Fdependabot-preview+user%3Ajenkinsci++%22Update+Dependabot+config+file%22+in%3Atitle

I was going to configure Dependabot on my buildtriggerbadge plugin, but
then realized Dependabot now has this nice feature to file automated PRs to
migrate from the previous Dependabot settings to the native one.

[image: image.png]

If anybody still has the previous configuration, and would like to get an
automated PR, please let me/us know and I can request it.

HTH
Cheers

Le jeu. 8 oct. 2020 à 13:29, Oleg Nenashev  a
écrit :

> I have started https://github.com/jenkinsci/.github/pull/40 with
> documentation notes. If anyone is interested to contribute and share your
> notes / best practices, please do so!
> Later we can move the page to
> https://www.jenkins.io/doc/developer/plugin-development/
>
> On Wednesday, June 24, 2020 at 11:03:25 PM UTC+2 Oleg Nenashev wrote:
>
>> FTR Dependabot is now embedded into GitHub. Probably it is a good time to
>> prepare official documentation
>> https://github.blog/2020-06-01-keep-all-your-packages-up-to-date-with-dependabot/
>
> --
> 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/af5db0c2-3be6-4efb-b017-c06cbe8ce912n%40googlegroups.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/CANWgJS5a6_NedKRH%2BYreUWFohpXNgtyxOwO88uHqERDvTw_v3A%40mail.gmail.com.

Re: Events Officer Role

[Victor Martinez]

Thanks Alyssa for all these years of hard work for the Jenkins community!! 
<3

On Friday, 2 October 2020 at 19:13:52 UTC+1 alytong13 wrote:

> Hi All,
>
>
> As I've been Events Officer for quite some time now, I would like to step 
> down from this role at the end of my tenure on 3 December 2020. I feel 
> giving others a chance to fulfill this role will bring new insights and 
> creativity.
>
> I will continue to contribute to the Jenkins project by ways of 
> participation in the Advocacy and Outreach SIG, drive the Jenkins is the 
> Way initiative, assist the new Events Officer in the transition and in 
> events related activities. 
>
> 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/1355b57e-38cd-4183-8b58-f16b7f911685n%40googlegroups.com.

Re: Jenkins-specific warnings for GitHub code scanning

[Daniel Beck]

On Sun, Oct 18, 2020 at 3:05 PM Ullrich Hafner 
wrote:

> Where should we report issues for false positives? I assume that those
> rules are written by a Jenkins community member, or are these general rules
> from Semmle?
>

These are Jenkins project specific rules only, we use CodeQL as the
tool/language but not the default rules (which is also why we use a custom
tool name; no conflict with the normal Semmle stuff if you choose to use
that as well). Please reach out to me directly with feedback. There's
currently no better (public) feedback channel for this yet.

-- 
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/CAMo7PtLdQ9%2Bfr2qf-%3DoMBnSZYoPwK17aE0NLMY7uGEf6oM9ZOw%40mail.gmail.com.

Re: Trademark sublicense request: TechMatrix Jenkins Support

[Yuji Tachibana]

Hello Oleg,

>Please consider it confirmed.  
OK, we will publish a launch of Techmatrix Enterprise Support for Jenkins.
Thank you very much for your understanding and quick response.

Yuji
2020年10月16日金曜日 15:56:02 UTC+9 Oleg Nenashev:

> Hello,
>
> I believe we discussed this option explicitly at the governance meeting.
> Please consider it confirmed.
>
> Best regards,
> Oleg
>
>
> On Fri, Oct 16, 2020 at 2:45 AM Yuji Tachibana  
> wrote:
>
>> Hello, Oleg
>>
>> Thank you for sharing the contents of board meeting.
>> We would like to use the name  "TechMatrix Enterprise Support for 
>> Jenkins" 
>> After your final confirmation, we will announce to its launch to our 
>> market.  
>>
>> Best Regards,
>> Yuji
>>
>> 2020年10月16日金曜日 5:40:06 UTC+9 Oleg Nenashev:
>>
>>> Hello Yuji,
>>>
>>> Just to summarize the yesterday's Governance Board review:
>>>
>>>- We recommend using the Linux Foundation trademark usage guidelines 
>>>. "TechMatrix 
>>>Enterprise Support for Jenkins" or a similar name are approved as long 
>>> as 
>>>the naming pattern is followed.
>>>- Based on the previous precedent, we approve "TechMatrix Jenkins 
>>>Support" should TechMatrix have a preference to use this trademark
>>>- The final name choice is up to TechMatrix. Please let us know 
>>>about your final decision in this thread.
>>>
>>> Regarding the trademarks discussion in general:
>>>
>>>- At the Governance meeting we approved further adoption of the 
>>>Linux Foundation trademark guidelines, with pre-approved patterns.
>>>- We reviewed a few examples on public cloud Marketplaces, and we 
>>>confirm that many distribution vendors have neither requested a 
>>> trademark 
>>>sublicense nor following the Linux Foundation naming patterns. The 
>>>consensus is that we are okay with historical distributions having clear 
>>>distinctions in the name (“E.g. Jenkins distribution by AcmeCorp”). 
>>>Final policy is to be defined during the trademark policy renewal.
>>>
>>> Best regards,
>>> Oleg
>>>
>>> On Thursday, October 15, 2020 at 2:55:50 PM UTC+2 Arnaud Héritier wrote:
>>>
 +1 too for "TechMatrix Enterprise Support for Jenkins" or  "TechMatrix 
 Jenkins Support"
 I agree that it could be good to follow Linux FDN convention as Yuji is 
 ok with it

 On Thu, Oct 15, 2020 at 2:36 PM Yuji Tachibana  
 wrote:

> Thank you for checking my request and sorry for not responding soon.
> I'm totally fine with using "TechMatrix Enterprise Support for 
> Jenkins" under the trademark policy of Linux Foundation.
> Please share the result, when the decision is made by board meeting, 
>
> Best Regards,
> Yuji
>
> 2020年10月14日水曜日 7:40:47 UTC+9 alytong13:
>
>> +1 on the approval and the Linux FDN suggested naming convention.
>>
>> On Tue, Oct 13, 2020 at 2:49 PM Oleg Nenashev  
>> wrote:
>>
>>> > It would be good to start following the Linux FDN for these things.
>>>
>>> I will add it to the tomorrow's agenda
>>>
>>> On Tuesday, October 13, 2020 at 11:46:59 PM UTC+2 slide wrote:
>>>
 Agreed on the approval and possible recommendations. It would be 
 good to start following the Linux FDN for these things.

 On Tue, Oct 13, 2020 at 2:22 PM Oleg Nenashev  
 wrote:

> Hello,
>
> It worth mentioning that the "CompanyName Jenkins Support" naming 
> pattern has been approved a few years ago for CloudBees Jenkins 
> Support: 
> https://wiki.jenkins.io/display/JENKINS/Approved+Trademark+Usage 
> . Based on this precedent, I am +1 for approving the current 
> trademark 
> request for "TechMatrix Jenkins Support".
>
> My personal preference would be to follow the Linux Foundation 
> trademark usage patterns 
> ,. In such case 
> the name would be "TechMatrix Support for Jenkins", "TechMatrix 
> Enterprise 
> Support for Jenkins" or something like that.
>
> Best regards,
> Oleg Nenashev
>
> On Friday, October 9, 2020 at 4:51:06 PM UTC+2 
> mind.the...@gmail.com wrote:
>
>> This is Yuji from TechMatrix, a distributor of CloudBees products 
>> in Japan
>>
>>  
>>
>> I'd like to request the permission to use the following name that 
>> uses "Jenkins" in it:
>>
>> "TechMatrix Jenkins Support"
>>
>>  
>>
>> The following is the brief introduction of what we are trying to 
>> launch is; TechMatrix Jenkins Support is a technical support service 
>> for 
>> Jenkins by our certified Jenkins engineers(CCJE).
>>
>> We provide technical