Amelia, Mike, no need to rush with the Duke replacement. I just wanted to kick the discussion off because at least two EE4J projects (JAX-RS and Yasson) presumably need to replace their logos due to EMO's recent denial of Duke (see https://dev.eclipse.org/ipzilla/show_bug.cgi?id=16051#c5). The problem is not the license of the Duke (BSD) but the fact that Oracle trademarked it. As a mascot is an indispensible tool of community forming, I thought it would be good to have a contest rather sooner than later. -Markus From: ee4j-pmc-bounces@xxxxxxxxxxx [mailto:ee4j-pmc-bounces@xxxxxxxxxxx] On Behalf Of Amelia Eiras Sent: Dienstag, 8. Mai 2018 03:13 To: EE4J PMC Discussions Subject: Re: [ee4j-pmc] Design Contest: Replacement for Duke Mascot Markus & Jakarta EE community, Hola from airport, ✈️ day for me so please bare with this quick follow up. Duke logo is not a O’s trademark. Will confirm & properly follow up facts via this thread or new thread after talking within peers from the marketing committee. Markus— Where did that communication got stablished btw you & EF? thank you for #walkingthetalk! 💙 If the idea is to replace Duke, isn’t that a Jakarta EE mascot? If so, wouldn’t that be a question for the working group, rather than the PMC? FWIW, I rather like this idea, but would slightly prefer to wait a while before pushing ahead, only because of all of the other things on our plates. But perhaps there’s some urgency here I’m unaware of. Please note new email address. Dear PMC, recently I was told by the EF that I must not further use the Duke as a Mascot for any EE4J projects, as the EF wants to trademark all logos but the Duke is trademarked by Oralce. While I literally hate this decision, I have to respect it and find a solution. For marketing reasons, and just for fun, having a Mascot would be great. The only solution I do see is that we have to start a Mascot Design Contest. BTW, this time we should respect all the critics we earned with the Logo Design Contest: We need to have clearly described ALL criteria upfront, give enough time (six weeks at least), and publicly announce on the mailing list. What do you think? -Markus
|