Re: Trademark sublicense request: CloudBees Jenkins Metrics

I interpret Stephen's response as "I don't object". In such case I confirm that I am fine with the request. Even if a request about this product occasionally lands in Jenkins JIRA, we can close them and refer to this thread. with all the typical caveats about CloudBees, Inc. having a

Re: Trademark sublicense request: CloudBees Jenkins Metrics

I think the presence of the "CloudBees" as a prefix has such overriding clarity in terms of the origin of the effort, that I'm having hard time imagining that creates a confusion in that regard. It is true that they share the same "Metrics" part, but that's not the trademarked part. That said, I

Re: Trademark sublicense request: CloudBees Jenkins Metrics

I personally find that the proposed name could cause confusion with the Metrics plugin, however given that the Metrics plugin was developed on company time, I feel it would be disingenuous of me to leverage a side-effect of being paid to do that development that has resulted in me being the

Re: Trademark sublicense request: CloudBees Jenkins Metrics

Generally the request looks good to me. OTOH it would be great to get feedback from the maintainer of the Metrics Plugin (Stephen Connolly?). If CloudBees plans to release a "CloudBees Jenkins Metrics Plugin" as a part of this new

Trademark sublicense request: CloudBees Jenkins Metrics

On behalf of CloudBees, I’d like to request the permission to use the following name that uses ‘Jenkins’ in it: - CloudBees Jenkins Metrics To help people understand how this name is going to be used, let me describe a bit about the effort for which we’d like to use this name. Back several