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 <[email protected]> wrote: > On 11.11.2014, at 14:14, Ulli Hafner <[email protected]> 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 [email protected]. > 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
