Hi Wayne
No, it would be
"Eclipse Puppy" or "Eclipse Whatever". My question
was whether the trademark check is done against "Eclipse Puppy"
or just "Puppy".
And just to be
clear, "Puppy" is just my running gag. I don't suggest to call
it that way for real.
Dani
From:
Wayne
Beaton <wayne.beaton@xxxxxxxxxxxxxxxxxxxxxx>
To:
eclipse-pmc@xxxxxxxxxxx
Date:
10.10.2018
19:33
Subject:
Re:
[eclipse-pmc] New Top Level Project Charter
Sent
by: eclipse-pmc-bounces@xxxxxxxxxxx
Start with "Puppy". All Eclipse
projects are prefixed with "Eclipse". In some cases, the trademark
search reveals that we can only use the name with the prefix.
Wayne
On Wed, Oct 10, 2018 at 10:45 AM Daniel
Megert <daniel_megert@xxxxxxxxxx>
wrote:
> if
you type "<name> technology" into Google
What's <name>? "Eclipse Puppy" or just "Puppy"?
And sorry to be a PITA, but is "Eclipse SDK" or "Eclipse
IDE" turned down by your trademark expert or is it, that the EMO just
doesn't like those?
Dani
From: Wayne
Beaton <wayne.beaton@xxxxxxxxxxxxxxxxxxxxxx>
To: eclipse-pmc@xxxxxxxxxxx
Date: 10.10.2018
16:33
Subject: Re:
[eclipse-pmc] New Top Level Project Charter
Sent by: eclipse-pmc-bounces@xxxxxxxxxxx
Dani, there is no such document and I have no plan to produce one.
Perhaps you can follow the model that has been used in the naming exercise
that we've used for every single instance of the simultaneous release.
I recommend that you open a bug to solicit names, eliminate any that look
obviously bogus, and set up a poll to let the committers vote on the ones
that remain. As with the simultaneous release names, it's best that you
deliver an ordered list of results that I can take to the Trademarks team
for vetting.
The Eclipse Foundation has a trademarks expert on staff that will assist
with the full vetting. Determining whether or not a name can be trademarked
is a pretty involved process (trademarks have, for example, domains; you
can sometimes use a name that somebody else uses when you're in a
different field of business). You can get a pretty good idea, however,
if you type "<name> technology" into Google and see what
comes back; if any of the first page or so of the search reesults look
like something in a similar field of work, then using that name may be
challenging.
HTH,
Wayne
On Wed, Oct 10, 2018 at 10:11 AM Daniel Megert <daniel_megert@xxxxxxxxxx>
wrote:
Hi Wayne
> and I have cause to believe that
they will be reject if proposed.
>> Who:
>>> The EMO
> What else do you need to know?
What we (or at least I) are missing are the publicly available document(s)
and process(es) that allow us as PMC to choose valid names. Currently it
looks like our suggestions will be thrown in a black box and the EMO then
comes with a yes/no. For example, if we decide to call it "Eclipse
Puppy", we have no clue whether that would be accepted. Also, what
needs to be a valid trademark? "Eclipse Puppy" or just "Puppy"?
Is there a database where we can check for trademarks?
Dani
From: Wayne
Beaton <wayne.beaton@xxxxxxxxxxxxxxxxxxxxxx>
To: eclipse-pmc@xxxxxxxxxxx
Date: 09.10.2018
22:41
Subject: Re:
[eclipse-pmc] New Top Level Project Charter
Sent by: eclipse-pmc-bounces@xxxxxxxxxxx
Why: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 theIDE
project.
and
The
Java development kit is a software development kit (SDK) for building "Java"
applications.
The
Android SDK is for building "Android" applications.
The
"Eclipse SDK" is for building what, then?
Who:
The EMO
Wayne
On Tue, Oct 9, 2018 at 4:25 PM Aleksandar Kurtakov <akurtako@xxxxxxxxxx>
wrote:
On Tue, Oct 9, 2018 at 11:22 PM Wayne Beaton <wayne.beaton@xxxxxxxxxxxxxxxxxxxxxx>
wrote:
The discussion at the Planning Council is orthogonal.
The trademark guidelines do not permit a project to be called "Eclipse".
The Eclipse Foundation asserts trademark ownership of all project names,
so all project names must be something that we can trademark.
There is no documentation that states that you cannot call it "Eclipse
SDK" or "Eclipse IDE". I have asserted that both of these
names are inappropriate, and I have cause to believe that they will be
reject if proposed.
Rejected by whom? Why?
What else do you need to know?
Wayne
On Tue, Oct 9, 2018 at 11:18 AM Daniel Megert <daniel_megert@xxxxxxxxxx>
wrote:
Wayne
Not sure how long it will take regarding the TLP name. Currently we wait
for the process/trademark documents as requested in the Planning Council
meeting. The PMC is fine with the updated charter, as long as the current
name is used.
Dani
From: Lars
Vogel <lars.vogel@xxxxxxxxxxx>
To: eclipse-pmc@xxxxxxxxxxx
Date: 05.10.2018
10:19
Subject: Re:
[eclipse-pmc] New Top Level Project Charter
Sent by: eclipse-pmc-bounces@xxxxxxxxxxx
+1 to the charter with the same name restrictions as the other PMC team
members stated
Thomas Watson <tjwatson@xxxxxxxxxx>
schrieb am Mi., 3. Okt. 2018, 19:45:
Other than the name change, I am fine with the charter.
Tom
----- Original message -----
From: "Daniel Megert" <daniel_megert@xxxxxxxxxx>
Sent by: eclipse-pmc-bounces@xxxxxxxxxxx
To: eclipse-pmc@xxxxxxxxxxx
Cc:
Subject: Re: [eclipse-pmc] New Top Level Project Charter
Date: Wed, Oct 3, 2018 10:53 AM
Anyone any objections or updates to the new charter except for the name?
Dani
From: Wayne
Beaton <wayne.beaton@xxxxxxxxxxxxxxxxxxxxxx>
To: eclipse-pmc@xxxxxxxxxxx
Date: 28.09.2018
22:18
Subject: [eclipse-pmc]
New Top Level Project Charter
Sent by: eclipse-pmc-bounces@xxxxxxxxxxx
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[attachment "DRAFT_ Eclipse Placeholder
Top Level Project Charter.pdf" deleted by Daniel Megert/Zurich/IBM]
_______________________________________________
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
_______________________________________________
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
--
Alexander Kurtakov
Red Hat Eclipse Team
_______________________________________________
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
_______________________________________________
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
_______________________________________________
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
_______________________________________________
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