Hi,
One for the marketing committee?
My preference would be for a set of consistent sub-brands for projects rather than a hotchpotch of project created logos whether Duke related or not. If EF needs to trademark logos then that will
likely preclude Duke as you say.
IANAL so my final conclusion is, IF the EF needs to be able to claim trademark on sub-project loos then yes they can’t derive from existing IP.
Steve
From: ee4j-pmc-bounces@xxxxxxxxxxx <ee4j-pmc-bounces@xxxxxxxxxxx>
On Behalf Of Ivar Grimstad
Sent: 10 April 2018 07:02
To: EE4J PMC Discussions <ee4j-pmc@xxxxxxxxxxx>
Subject: Re: [ee4j-pmc] Project logos based on "Duke"
Hi,
My input on this is that we should find a way to allow Duke images. Not the ones that are TM:ed by Oracle, but the community contributed open source ones.
As you point out, there is a connection between Duke and Java and this connection won't go away. And as all EE4J projects currently are Java projects, I cannot see any reason why we should distance us from that. Using the Java-cup would
be wrong, but Duke...?
Hey EE4J PMC...
We have a couple of projects that either already have, or are planning to adopt logos that are based on "Duke".
We have what I think is a hard stop. Duke, while BSD-licensed, is a copyright and claimed trademark of Oracle. So, while derivative works of Duke are permitted, claiming trademark of those derivative works is at least excessively challenging
(effectively impossible). Like project name trademarks, the Eclipse Foundation, asserts trademark ownership (albeit unregistered for the most-part) of project logos on behalf of the community.
TL;DR: the EF needs to be able to claim ownership/trademark of the logo, but can't make that claim for a derivative logo. So project logos cannot derive from existing (copyrighted and trademarked) property.
Further, there is a tight association between Duke and Java. There is an obvious tight connection between the Jakarta EE technologies and Java as well, but am concerned that reinforcing the connection between Jakarta EE technologies and
Duke introduces confusion (maybe I'm thinking about this too hard).
I am also concerned that there is a tight association between Oracle and Duke, which may compromise vendor neutrality. I may well be overthinking this one as well.
So my question is... Do you agree with my assessment that project logos cannot derive from existing intellectual property?
Am I missing something important?
--
Wayne Beaton
Director of Open Source Projects
_______________________________________________
ee4j-pmc mailing list
ee4j-pmc@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ee4j-pmc
--
Java Champion, JCP EC/EG Member, EE4J PMC, JUG Leader
|
