> > If Jenkins ever gets a good solution for plugin renaming, then perhaps the > name of the plugin could be revisited... but just not before a significant > proportion of the community have versions of Jenkins that would be ok with > a plugin rename.
However, there's a risk of naming clashes in several cases. As example, we have "metadata-plugin" and "google-metadata-plugin". Essentially they're different plugins with almost similar names and IMO similar functionality. I'm not sure how to resolve the naming issue in such case without a company prefix. Probably, Robert Sandell and Matt Moor agree to just merge them (needs a separate discussion) My proposals: 1. Explicitly display JIRA component IDs in plugin-info-macro on Wiki 2. Leave the decision regarding company prefixes to plugin owners Best regards, Oleg Nenashev 2014-11-11 20:40 GMT+03:00 Stephen Connolly <stephen.alan.conno...@gmail.com >: > Well it was our plugin, but we open sourced it and it now belongs to the > community > > There would have been a host of issues with the existing installations if > we renamed it, so it was simpler to keep the existing name. > > If Jenkins ever gets a good solution for plugin renaming, then perhaps the > name of the plugin could be revisited... but just not before a significant > proportion of the community have versions of Jenkins that would be ok with > a plugin rename. > > On 11 November 2014 17:28, Daniel Beck <m...@beckweb.net> wrote: > >> On 11.11.2014, at 14:14, Ulli Hafner <ullrich.haf...@gmail.com> wrote: >> >> > Maybe we should also remove the prefix cloudbees from the folders >> plugin. It took me a while to find the component in Jira… >> >> That's part of the plugin name everywhere (display name, short name, >> repo, component), so I'd be surprised if there was nobody looking for the >> plugin _with_ that prefix. >> >> Different from Jenkins/Hudson/CI it's also not redundant in the context >> of Jenkins CI. (Jenkins removes leading "Jenkins " from plugin names on the >> UI because it's so useless, so I expect that users will not generally >> consider that part of the plugin name.) >> >> IMO it's legitimate branding of their plugins. Note that most (or all) >> Cloudbees Plugins have that prefix (it's just the only one available on the >> Jenkins project hosted update center, and that only since version 4.0 was >> open sourced). >> >> -- >> 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 jenkinsci-dev+unsubscr...@googlegroups.com. >> For more options, visit https://groups.google.com/d/optout. >> > > -- > 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/T_V9Z71rbPk/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > jenkinsci-dev+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- 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 jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
