Re: [eclipse-pmc] New Top Level Project Charter

["Mike Wilson" <Mike_Wilson@xxxxxxxxxx>]

The problem with renaming *anything* today is that hurts your search ranking. Honestly, my preference would be "Eclipse SDK" mainly because that's what we've been calling ourselves for > 5 years now. If we change the name to "Eclipse Potato" (or anything else other than "SDK" (or maybe "IDE")), we're going to make ourselves harder to find and harder to remember -- not something you'd want for a project that is still active.

This is made worse by the request that the result be trademarkable. All it takes is a few google searches to realize that anything related to "Core", "Nucleus", etc. is not going to fly, so where does that leave us?

Here's a thought: Maybe we should call ourselves "Placeholder". We've already got a charter to match it. ;-P

McQ.

Sopot Cela ---2018/10/02 05:38:11---The answer below is your interpretation Wayne, and if applied to the letter would cause quite a lot

From: Sopot Cela <scela@xxxxxxxxxx>
To: eclipse-pmc@xxxxxxxxxxx
Date: 2018/10/02 05:38
Subject: Re: [eclipse-pmc] New Top Level Project Charter
Sent by: eclipse-pmc-bounces@xxxxxxxxxxx

---

The answer below is your interpretation Wayne, and if applied to the letter would cause quite a lot of Eclipse projects to be renamed (we have way more ambiguous stuff than SDK). 

If it's not too much trouble, would you please point us to the actual guidelines with a highlight to the rule that we are breaking by naming the TLP, e.g. "Eclipse SDK"?

Thanks,
Sopot

On Mon, Oct 1, 2018 at 4:35 PM, Wayne Beaton <wayne.beaton@xxxxxxxxxxxxxxxxxxxxxx> wrote:

All project names are claimed as trademarks of the Eclipse Foundation with the potential for us to seek registration. This is always a requirement.

Regarding the use of either "IDE" or "SDK"...

We can parse language all we want, but a project named "Eclipse SDK" is effectively a project named "Eclipse" ("Which SDK is it? Why, it's the Eclipse SDK") .and this is a violation of the trademark guidelines. 

Further, it is not the only project at the Eclipse Foundation that produces an IDE or SDK, and so it is misleading to refer to it as the SDK or the IDE project.

HTH,

Wayne

On Mon, Oct 1, 2018 at 8:57 AM Daniel Megert <daniel_megert@xxxxxxxxxx> wrote:
Hi Wayne
 
Sorry to bug you once again, but I already asked you in our private e-mail thread to point us to the place(s) in the trademark guidelines that do not allow us to use IDE or SDK. So, please do so, or we might just pick those again.
 
Thanks,
Dani
 
 
----- Original message -----
From: Wayne Beaton <wayne.beaton@xxxxxxxxxxxxxxxxxxxxxx>
Sent by: eclipse-pmc-bounces@xxxxxxxxxxx
To: eclipse-pmc@xxxxxxxxxxx
Cc:
Subject: [eclipse-pmc] New Top Level Project Charter
Date: Fri, Sep 28, 2018 10:18 PM
 
Greetings PMC.
 
Please find attached a PDF that contains a draft for an updated Top Level Project Charter. In this draft, I have attempted to generalize the mandate of the Top Level Project beyond the tools focus of the original document (you'll also notice that I've cut out the content that is covered by the standard charter). 
 
These edits currently live in a Google Doc. I will grant edit access to any PMC member that requests it (for completeness, the Google Doc is for editing purposes: I expect that we'll move the final version of this document onto the website).
 
Perhaps one of the first things that you'll likely notice is the name: "Eclipse Placeholder". As we've discussed, we need to come up with a new name. I've propagated that placeholder name through the document to show how and where I think that the new name has to be used.
 
I leave it to the PMC's discretion to decide who and how best to engage to make this selection.
 
Note that the Eclipse Foundation would very much like to be able to register the name as a trademark (note that "like to" is not intended to suggest any particular timeline for doing so). By way of expectation management, there is some risk that your first selection may not be something that we can register and so we may end up needing a second (or third) choice.
 
By way of clarification, the name that you need to select is for the Top Level Project (this name may also apply to the project's deliverables). It is the Eclipse Planning Council's responsibility to name the associated simultaneous release and related products. I will engage with them shortly to start this process.
 
Thanks,

Wayne
--
Wayne Beaton
Director of Open Source Projects | Eclipse Foundation, Inc.

Meet us at EclipseCon Europe 2018: LUDWIGSBURG, OCTOBER 23 - 25
 
_______________________________________________
eclipse-pmc mailing list
eclipse-pmc@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/eclipse-pmc
 

_______________________________________________
eclipse-pmc mailing list
eclipse-pmc@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/eclipse-pmc


--
Wayne Beaton
Director of Open Source Projects | Eclipse Foundation, Inc.

Meet us at EclipseCon Europe 2018: LUDWIGSBURG, OCTOBER 23 - 25

_______________________________________________
eclipse-pmc mailing list
eclipse-pmc@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/eclipse-pmc

-- 
Sopot Cela
Software Engineering Manager

_______________________________________________
eclipse-pmc mailing list
eclipse-pmc@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/eclipse-pmc