(replies inline) On Wed, 09 Oct 2019, Parker Ennis wrote:
> On behalf of CloudBees, I’d like to request permission to use the following > name with ‘Jenkins’ in it: > > • Jenkins Master Class > > "Jenkins Master Class" will be a series of educational webinars hosted by > CloudBees that invites experts from both the Jenkins community and CloudBees > to > team up and share their knowledge with others. The intent is to host 10+ > webinars, or "courses," with a duration of about an hour each released on a > monthly cadence. They will be recorded for future use. Here's a loose [1] > example of the concept from which we're drawing inspiration. The "test" we have typically applied to such requests in the past was whether the use of the mark was pecific to Jenkins, as opposed to including other non-Jenkins applications/products. For example, I have no problem with this so long as the content of the "master class" are specifically around Jenkins as it is understood by the open source community, i.e. open source plugins and core, etc. If this "master class" were to contain Jenkins-based commercial products, such as CLoudBees Core, then I would have an objection to the use of the Jenkins trademark for the effort. Knowledge sharing is certainly a noble goal, but for the use of the Jenkins mark, the scope should be necessarily limited. Toodles --- GitHub: https://github.com/rtyler GPG Key ID: 0F2298A980EE31ACCA0A7825E5C92681BEF6CEA2 -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/RsYEboXMRk5QGxcXH0moxY7pT4lEdZ636ceepYhZL0XiTh9Ep5xNzwdrKd-JelWpcKE13oh0ufLhApxcHtZpypn7eoZ3dPX7b2Xc2SyriLc%3D%40brokenco.de.
signature.asc
Description: OpenPGP digital signature
