Trademark sublicense request: CloudBees Jenkins X Support

classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

Trademark sublicense request: CloudBees Jenkins X Support

Tracy Miranda
Hi all,

On behalf of CloudBees, I’d like to request the permission to use the following name that uses ‘Jenkins’ in it:
  • CloudBees Jenkins X Support
This will be a name of a support offering (not a product) for Jenkins X support from CloudBees
This is inclusive of all the services components provided: s support personnel, knowledgebase, CSM interaction, docs, etc.  

The aim has been to keep this consistent with existing names already approved including previously approved CloudBees Jenkins Support. 

I will add this as an agenda item for Dec 5th project governance meeting to be able to get a decision there. If you have any concerns or objections, please chime in on this thread prior to the meeting, so that we can address them.

Tracy

--
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/CACTaz6qewJZXcJgwUSiZ8ERi7YGWH2b4e4Dg0JhDc0RaO0_Mfw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Trademark sublicense request: CloudBees Jenkins X Support

Oleg Nenashev
Since these is already "CloudBees Jenkins Support" has been already approved, I see no reason why it cannot be approved from the process standpoint.
So +1 from me

On Tuesday, November 27, 2018 at 4:10:56 PM UTC+1, Tracy Miranda wrote:
Hi all,

On behalf of CloudBees, I’d like to request the permission to use the following name that uses ‘Jenkins’ in it:
  • CloudBees Jenkins X Support
This will be a name of a support offering (not a product) for Jenkins X support from CloudBees
This is inclusive of all the services components provided: s support personnel, knowledgebase, CSM interaction, docs, etc.  

The aim has been to keep this consistent with existing names already approved including previously approved CloudBees Jenkins Support. 

I will add this as an agenda item for Dec 5th project governance meeting to be able to get a decision there. If you have any concerns or objections, please chime in on this thread prior to the meeting, so that we can address them.

Tracy

--
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/ec85b2e4-c6d6-4fda-8586-5a03d43cb21f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Trademark sublicense request: CloudBees Jenkins X Support

jstrachan
In reply to this post by Tracy Miranda
+1 from me too

On Tuesday, November 27, 2018 at 3:10:56 PM UTC, Tracy Miranda wrote:
Hi all,

On behalf of CloudBees, I’d like to request the permission to use the following name that uses ‘Jenkins’ in it:
  • CloudBees Jenkins X Support
This will be a name of a support offering (not a product) for Jenkins X support from CloudBees
This is inclusive of all the services components provided: s support personnel, knowledgebase, CSM interaction, docs, etc.  

The aim has been to keep this consistent with existing names already approved including previously approved CloudBees Jenkins Support. 

I will add this as an agenda item for Dec 5th project governance meeting to be able to get a decision there. If you have any concerns or objections, please chime in on this thread prior to the meeting, so that we can address them.

Tracy

--
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/7e1815b5-f2ff-41e8-81f7-80adb251106e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Trademark sublicense request: CloudBees Jenkins X Support

James Rawlings-2
+1 from me

On Wednesday, December 5, 2018 at 5:09:55 PM UTC, [hidden email] wrote:
+1 from me too

On Tuesday, November 27, 2018 at 3:10:56 PM UTC, Tracy Miranda wrote:
Hi all,

On behalf of CloudBees, I’d like to request the permission to use the following name that uses ‘Jenkins’ in it:
  • CloudBees Jenkins X Support
This will be a name of a support offering (not a product) for Jenkins X support from CloudBees
This is inclusive of all the services components provided: s support personnel, knowledgebase, CSM interaction, docs, etc.  

The aim has been to keep this consistent with existing names already approved including previously approved CloudBees Jenkins Support. 

I will add this as an agenda item for Dec 5th project governance meeting to be able to get a decision there. If you have any concerns or objections, please chime in on this thread prior to the meeting, so that we can address them.

Tracy

--
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/26de20fd-f7b2-48d4-8dca-ce9c3959566a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Trademark sublicense request: CloudBees Jenkins X Support

Parker Ennis
In reply to this post by Tracy Miranda
+1. Will be great for consistency and continuing to improve the collaboration with the community to make Jenkins X the best it can be. A testament to the bright future ahead.


On Tuesday, November 27, 2018 at 10:10:56 AM UTC-5, Tracy Miranda wrote:
Hi all,

On behalf of CloudBees, I’d like to request the permission to use the following name that uses ‘Jenkins’ in it:
  • CloudBees Jenkins X Support
This will be a name of a support offering (not a product) for Jenkins X support from CloudBees
This is inclusive of all the services components provided: s support personnel, knowledgebase, CSM interaction, docs, etc.  

The aim has been to keep this consistent with existing names already approved including previously approved CloudBees Jenkins Support. 

I will add this as an agenda item for Dec 5th project governance meeting to be able to get a decision there. If you have any concerns or objections, please chime in on this thread prior to the meeting, so that we can address them.

Tracy

--
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/eef1b4fb-5b83-4293-958c-576cecd5e448%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Trademark sublicense request: CloudBees Jenkins X Support

James Nord-3
In reply to this post by Tracy Miranda
I see no reason why we should treat "Jenkins X" with different rules from "Jenkins", and as such given this follows the trend of usage already approved here is my +1


On Tuesday, November 27, 2018 at 3:10:56 PM UTC, Tracy Miranda wrote:
Hi all,

On behalf of CloudBees, I’d like to request the permission to use the following name that uses ‘Jenkins’ in it:
  • CloudBees Jenkins X Support
This will be a name of a support offering (not a product) for Jenkins X support from CloudBees
This is inclusive of all the services components provided: s support personnel, knowledgebase, CSM interaction, docs, etc.  

The aim has been to keep this consistent with existing names already approved including previously approved CloudBees Jenkins Support. 

I will add this as an agenda item for Dec 5th project governance meeting to be able to get a decision there. If you have any concerns or objections, please chime in on this thread prior to the meeting, so that we can address them.

Tracy

--
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/c2a8bf27-6fac-4f7d-a690-e846fcde5e3c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.