Re: Trademark sublicense request: Jenkins Health Advisor by CloudBees

I think this pretty safely falls into the naming convention we have accepted for a good long while. +1 On Tue, Sep 24, 2019 at 0:19 Arnaud Héritier wrote: > I will abstain because I'm contributing actively on this project. > I will answer to all questions with pleasure but I sadly cannot join

Re: Trademark sublicense request: Jenkins Health Advisor by CloudBees

I will abstain because I'm contributing actively on this project. I will answer to all questions with pleasure but I sadly cannot join the meeting tomorrow. Cheers On Mon, Sep 23, 2019 at 10:47 PM Oleg Nenashev wrote: > Needs more feedback ahead of the Governance meeting on Sep 25th. Please >

Re: Trademark sublicense request: Jenkins Health Advisor by CloudBees

I am in favor of this change (+1). This is plugin is open source (https://github.com/jenkinsci/cloudbees-jenkins-advisor-plugin ) and I feel changing the name to Jenkins Health Advisor by CloudBees show value in upstream plugin

Trademark sublicense request: Jenkins Health Advisor by CloudBees

Needs more feedback ahead of the Governance meeting on Sep 25th. Please vote, everyone! Personally I abstain in the case of this vote. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving

Trademark sublicense request: Jenkins Health Advisor by CloudBees

Hi All, On behalf of CloudBees, I’d like to request permission to use the following name with ‘Jenkins’ in it: - *Jenkins Health Advisor by CloudBees* This will replace the existing name in use today for the "CloudBees Jenkins Advisor" plugin (previously trademark approved