For the record, see https://jira.codehaus.org/browse/MNGSITE-180
Cross-posting to dev list so that PMC can discuss that issue at what should be the exact wording. Cheers 2013/6/12 Stephen Connolly <stephen.alan.conno...@gmail.com> > On 12 June 2013 11:04, Stephen Colebourne <scolebou...@joda.org> wrote: > > > I made this mistake too. Could I make some suggestions? > > > > Add the banned naming to the top of plugin guides, such as: > > http://maven.apache.org/guides/plugin/guide-java-plugin-development.html > > > > > +1, anyone want to take a stab at providing a patch? > > > > Change this page to only have the single prefix-maven-plugin example: > > > > > http://maven.apache.org/guides/introduction/introduction-to-plugin-prefix-mapping.html > > I scan read and thought they were just two options. > > > > > +1, anyone want to take a stab at providing a patch? > > > > > Use big/bold/red font. > > "You must not name your plugin maven-foo-plugin as these are reserved > > by trademark for the Apache Maven project itself" > > > > Correction, in order to protect the Maven trademark, we need to get people > to acknowledge the mark whenever they use it. We have consulted with legal > and the agreement that was reached was that if we defined a pattern of > allowed usage, we need not be "all over" people who are complying with the > allowed pattern of usage. > > The allowed pattern of usage is that where the use of the mark is referring > to the plugin being for use with Maven, hence "___ Plugin for Maven" is > fine but "Maven ___ Plugin" is not. Obviously "___'s ___ plugin for Maven" > is even better, e.g. "Mojo's Cassandra plugin for Maven" (which has the > bigger fun of using two Apache marks... that plugin is the one that got me > sucked into this rats nets) > > As to the artifactId convention. That was a long standing, if undocumented > convention. The Maven Plugin Plugin currently emits a stern warning if you > use the maven-___-plugin pattern > > http://maven.apache.org/plugin-tools/maven-plugin-plugin/xref/org/apache/maven/plugin/plugin/AbstractGeneratorMojo.html#177 > > Perhaps we are at the point where we should start breaking builds rather > than just giving a stern warning... certainly the warning has been there > for long enough > > > > > > Sonatype's Maven Central upload should have a rule to prevent any new > > jar being pushed with the maven-*-plugin name (unless its an update to > > an existing version or within org.apache.maven group). > > > > Somebody from Sonatype would need to comment on that... or maybe the PMC > will request Sonatype to provide such a facility to assist in our > protection of our mark... needs thinking time > > > > > > I'd note that now I have a plugin in Maven Central with the wrong name > > I can't remove it, so getting this wrong is a right pain in the *** > > and messes lots of things up. > > > > What matters is that you are complying going forward and that, when we > become aware of infringing use, we get you to ack the trademark (sending > C&Ds if necessary). > > So step 1 is to ack the mark. As long as you ack the mark we are 90% happy. > > IANAL, but as I understand it, if you use the term in writing a plugin for > Maven *and* you use the approved naming convention (the one that makes it > clear that the plugin is *for* Maven) then you might not need to ack the > mark in the strictest sense, but it is safer to ack it anyway.... in other > words the approved naming is just to help people comply > > > > Stephen > > > > > > On 12 June 2013 07:59, James Green <james.mk.gr...@gmail.com> wrote: > > > Many thanks for filing this - I do assure you that I was not under the > > > impression the GitHub plugin was official or even endorsed but I agree > > that > > > the trademark requires work to enforce. And I just love their response > in > > > your ticket - made me laugh and cringe..! > > > > > > James > > > > > > > > > On 11 June 2013 22:44, Stephen Connolly < > stephen.alan.conno...@gmail.com > > >wrote: > > > > > >> On 11 June 2013 22:27, Stephen Connolly < > > stephen.alan.conno...@gmail.com > > >> >wrote: > > >> > > >> > On 11 June 2013 22:03, James Green <james.mk.gr...@gmail.com> > wrote: > > >> > > > >> >> If you search for maven-download-plugin you should reach a project > on > > >> >> GitHub. > > >> > > > >> > > > >> > Please advise them to rename their plugin as the current name is in > > >> > violation of the permitted usages of the ASF's trademark Maven: > > >> > > > >> > > > http://markmail.org/search/?q=list%3Aorg.apache.maven.dev#query:list%3Aorg.apache.maven.dev+page:1+mid:cmqxvj6ddshmnzwr+state:results > > >> > > > >> > And further the name confuses users as to who is responsible for the > > >> > plugin. > > >> > > > >> > > >> Filed: > > >> > > >> > > https://github.com/maven-download-plugin/maven-download-plugin/issues/14 > > >> > > >> I so hate having to do this... the "joys" of having to defend a > > trademark! > > >> > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > > For additional commands, e-mail: users-h...@maven.apache.org > > > > > -- Baptiste <Batmat> MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor !
