ANN - Jenkins Trademark is transferred to the Linux Foundation

[Oleg Nenashev]

Dear all,

Just to follow-up on the old topic, the Jenkins trademark has been recently transferred to LF Charities Inc. which is a subsidiary of the Linux Foundation. This concludes the long process of Jenkins assets transition from the Software in Public Interest (SPI) to the Linux Foundation. This started when we voted to join the Continuous delivery Foundation in 2018, and I am excited to see it finally completed.

What changes?

• Trademark Usage. The Linux Foundation Trademark usage policy is now required for the project. We won't be approving new trademark usage requests violating this policy. https://github.com/jenkins-infra/jenkins.io/pull/4030 updates the trademark documentation on the website. I suggest reviewing and approving it at today's governance meeting
• Trademark Attribution. The Jenkins trademark attribution changes, hence all users are expected to gradually replace attribution to "Jenkins® is a registered trademark of the Linux Foundation" in the resources (websites, marketing materials, etc., etc.). There is no strict deadline for this update
• Reimbursements. We still have some assets controlled by SPI, most notably the old treasury which still has some money there. If someone needs to request reimbursements from the project, please follow the SPI Reimbursement Process ann CC the Jenkins Governance Board in the requests. Once we use all SPI money, we will switch to the LFX process documented in JEP-15.

More changes to come.

Best regards,

Oleg Nenashev

Jenkins Governance Board

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLB6eS_1CBOB29m7fyZPDAzkU6R9hp%2Bwp1DW3J3L5_Cqtw%40mail.gmail.com.

[Oleg Nenashev]

Quick update about the trademark references. The official guidance from the Linux Foundation is to use "Jenkins is a registered trademark of LF Charities Inc." attribution. They needed a 501(c)(3) legal entity to hold the trademark due to some legal obstacles the LF hit during the trademark transition.

The guidelines will be updated accordingly

On Wednesday, February 24, 2021 at 2:38:21 PM UTC+1 Oleg Nenashev wrote:

Dear all,

Just to follow-up on the old topic, the Jenkins trademark has been recently transferred to LF Charities Inc. which is a subsidiary of the Linux Foundation. This concludes the long process of Jenkins assets transition from the Software in Public Interest (SPI) to the Linux Foundation. This started when we voted to join the Continuous delivery Foundation in 2018, and I am excited to see it finally completed.

What changes?

• Trademark Usage. The Linux Foundation Trademark usage policy is now required for the project. We won't be approving new trademark usage requests violating this policy. https://github.com/jenkins-infra/jenkins.io/pull/4030 updates the trademark documentation on the website. I suggest reviewing and approving it at today's governance meeting
• Trademark Attribution. The Jenkins trademark attribution changes, hence all users are expected to gradually replace attribution to "Jenkins® is a registered trademark of the Linux Foundation" in the resources (websites, marketing materials, etc., etc.). There is no strict deadline for this update
• Reimbursements. We still have some assets controlled by SPI, most notably the old treasury which still has some money there. If someone needs to request reimbursements from the project, please follow the SPI Reimbursement Process ann CC the Jenkins Governance Board in the requests. Once we use all SPI money, we will switch to the LFX process documented in JEP-15.

More changes to come.

Best regards,

Oleg Nenashev

Jenkins Governance Board

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/8ed446dc-6b97-49e1-9054-f8e09297b42fn%40googlegroups.com.

[Oleg Nenashev]

Another quick update: The Linux Foundation has no process for sublicensing the trademarks except the "Linux" one.

In proactive we have never fully followed the sublicense process, so I will remove the documentation for it entirely.

On Monday, March 8, 2021 at 10:42:18 AM UTC+1 Oleg Nenashev wrote:

Quick update about the trademark references. The official guidance from the Linux Foundation is to use "Jenkins is a registered trademark of LF Charities Inc." attribution. They needed a 501(c)(3) legal entity to hold the trademark due to some legal obstacles the LF hit during the trademark transition.

The guidelines will be updated accordingly

On Wednesday, February 24, 2021 at 2:38:21 PM UTC+1 Oleg Nenashev wrote:

Dear all,

Just to follow-up on the old topic, the Jenkins trademark has been recently transferred to LF Charities Inc. which is a subsidiary of the Linux Foundation. This concludes the long process of Jenkins assets transition from the Software in Public Interest (SPI) to the Linux Foundation. This started when we voted to join the Continuous delivery Foundation in 2018, and I am excited to see it finally completed.

What changes?

• Trademark Usage. The Linux Foundation Trademark usage policy is now required for the project. We won't be approving new trademark usage requests violating this policy. https://github.com/jenkins-infra/jenkins.io/pull/4030 updates the trademark documentation on the website. I suggest reviewing and approving it at today's governance meeting
• Trademark Attribution. The Jenkins trademark attribution changes, hence all users are expected to gradually replace attribution to "Jenkins® is a registered trademark of the Linux Foundation" in the resources (websites, marketing materials, etc., etc.). There is no strict deadline for this update
• Reimbursements. We still have some assets controlled by SPI, most notably the old treasury which still has some money there. If someone needs to request reimbursements from the project, please follow the SPI Reimbursement Process ann CC the Jenkins Governance Board in the requests. Once we use all SPI money, we will switch to the LFX process documented in JEP-15.

More changes to come.

Best regards,

Oleg Nenashev

Jenkins Governance Board

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/e4a63edd-8204-4606-9431-15e3f85574bfn%40googlegroups.com.