Rename Plugin Title

[Gavin Mogan]

Looking at https://plugins.jenkins.io/sauce-ondemand and https://wiki.jenkins-ci.org/display/JENKINS/Sauce+OnDemand+Plugin I would really like to change the name of the plugin. I'm not picky about the artifact id, i know the side effects of changing that, but I would like to change the name.

Is it as simple as renaming the wiki page, and updating the <url> in the pom.xml file? I vaguely remember something about items in the update center not showing up if the wiki page didn't match the plugin page but I can't find what it needed to actually match.

According to https://groups.google.com/d/msg/jenkinsci-dev/oEHEjKo08yA/ShbomKaaA7QJ i'm pretty sure thats it, but I wanted to double check before I changed the url and did a release since I'm pretty sure wiki urls need to match wiki titles.

Gavin

[Daniel Beck]

> On 27.02.2017, at 09:14, Gavin Mogan <ga...@gavinmogan.com> wrote:
>
> Is it as simple as renaming the wiki page, and updating the <url> in the pom.xml file? I vaguely remember something about items in the update center not showing up if the wiki page didn't match the plugin page but I can't find what it needed to actually match.

The name of the plugin shown pretty much everywhere is just https://github.com/jenkinsci/sauce-ondemand-plugin/blob/209729e8ae033319b9d5db68e0c5d82ce4338021/pom.xml#L28 (Jenkins removes leading 'Jenkins' on the UI).

The wiki page title is independent from that, but renaming that must be coordinated with the release of a change in <url> to prevent the update center from determining the URL is wrong.

[Gavin Mogan]

Awesome, thanks for confirming everything.

Since Jenkins removes the start of Jenkins, is there any restriction on the use of the name? I saw cloudbees before has had to apply for use, but I know thats for seperate projects.

We want to rename it to "Sauce Labs for Jenkins" as the for <product> is what we settled on for the other integrations of ours.

Is that allowed? Or should we just call it "Sauce Labs" or something?

Gavin

--
You received this message because you are subscribed to a topic in the Google Groups "Jenkins Developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-dev/IscTZjPxJos/unsubscribe.
To unsubscribe from this group and all its topics, send an email to jenkinsci-dev+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/6AC5480C-CCD9-4DE3-B9AA-8785C92FD068%40beckweb.net.

For more options, visit https://groups.google.com/d/optout.

[Daniel Beck]

> On 28.02.2017, at 01:51, Gavin Mogan <ga...@gavinmogan.com> wrote:
>
> Since Jenkins removes the start of Jenkins, is there any restriction on the use of the name? I saw cloudbees before has had to apply for use, but I know thats for seperate projects.
>
> We want to rename it to "Sauce Labs for Jenkins" as the for <product> is what we settled on for the other integrations of ours.
>
> Is that allowed? Or should we just call it "Sauce Labs" or something?

Right, CloudBees applies for trademark usage for their products: https://jenkins.io/project/governance/#trademark

I don't think this applies to Jenkins plugins (I think the difference is that plugin names are not typically trademarks), not sure.

The reason we strip leading "Jenkins" from plugin names in the Jenkins plugin manager is that it's redundant: Users are looking at a list of _plugins_ for _Jenkins_, and many of them are called "Jenkins Whatever Plugin". Two thirds of that should be obvious.