Is Jakarta Bean Validation 2 or 3 still supposed to use the "Duke" logo? about validation-spec HOT 7 OPEN

We removed it from the spec files but it's the logo of Bean Validation so we thought we would keep it on the website.

The website is outside of the Eclipse org.

from validation-spec.

@waynebeaton, @ivargrimstad Is that an acceptable practice, also for other specs including MVC or NoSQL, or CDI-Spec, although that has a different logo now anyway?

NoSQL.org is a bit different because it is a front page for the implementation project and not Jakarta NoSQL, but there the question of the Duke logo also comes up in a similar way.

from validation-spec.

The Duke logo is Open Source.

And this is not the Duke logo, this is the Bean Validation logo which was based on the Duke logo.

It’s also Open Source.

from validation-spec.

Eclipse and with it also "EE4J" I guess have slightly different restrictions or permissions than your average JUG or a random Open Source project on GitHub. Please clarify with @ivargrimstad, @waynebeaton and maybe somebody in the Marketing Committee, if the logo is valid for a Jakarta EE project or not.

For example @m0mus had a JSON-B logo based on Duke with a hockey mask like Jason in Friday the 13th on http://json-b.net/, but after it moved to Jakarta EE both the JSON-B and "Yasson" sites no longer use Duke or anything derived from the Duke image.

from validation-spec.

The short version is that you can incorporate Duke into artwork on your site, but Duke cannot be incorporated into a project logo.

The Eclipse Foundation claims trademark of all project logos (most of these claims are "common law"), and holds and protects them on behalf of the project. While Duke is licensed in manner that permits derivative works, we've determined that we cannot claim trademark of project logos that incorporate Duke.

The image in the middle of the cited page looks like just some cool artwork to me. The smaller version of the image in the top left, however, feels like a logo and so that use is problematic.

Based on the reference from the project's Git READMEs, this site is being treated as the official project website. If this is the case, the website content needs to be moved under the purview of the project team (i.e., it needs to be moved under Eclipse Foundation management), and updated to include things like a footer with pointers to the terms of use.

If it's just a community portal, then it needs to be treated as one (i.e., just a source of interesting and otherwise useful information about the project, and not the source of "work in progress" information). Minimally, the trademarks used on the site need proper demarcation and there needs to be a trademark attribution statement.

from validation-spec.

Thanks for the clarification, I assume regardless of spec or implementation projects this also applies to JNoSQL.

from validation-spec.

Thanks for the clarification, I assume regardless of spec or implementation projects this also applies to JNoSQL.

Yes.

from validation-spec.