| Re: [eclipse.org-planning-council] Mars+1 Naming Issues |
|
From: Ian Bull
Sent: Saturday, February 28, 2015 3:43 PM
To: Eclipse Planning Council private list
Reply To: Eclipse Planning Council private list
Subject: Re: [eclipse.org-planning-council] Mars+1 Naming Issues
|
MarkusDo you happen to have any "feeling" if this would pass trademark review?Thanks,
On 27 February 2015 at 23:24, Wayne Beaton <wayne@xxxxxxxxxxx> wrote:
Suggestion found in the Proposals forum [1]:
Mars should be renamed Vulcan
Renaming Mars is out of the question at this point the process, but shall we consider using the name for Mars+1 ?
"Eclipse Vulcan" (Live Long and Prosper)
If anybody actually thinks that this is a decent idea, I recommend that we let it stew for at least a few days before we make a decision.
Paying homage is cool, being perceived as exploiting the death of a famous person is not.
This also sets us up for "Eclipse Wayne" in 2017. How do you like them apples, Lynn?
Wayne
[1] https://www.eclipse.org/forums/index.php?t=rview&goto=1639799#msg_1639799
On 26/02/15 05:10 PM, Chris Aniszczyk wrote:
DougS, lets not make that assumption and leave it to counsel.
DaveW, the timing thing was mostly a nice goal to reach, it's not set in stone.
Here's my suggestion, I created a poll with the remaining list of names with an option to write one in (you can also state N/A for none of them):
I'd like to have the Planning Council give input here and we'll move forward with the top choices from this list if there is a solid consensus. There are some solid names in the list but if they aren't good either, we'll be out of luck.
Furthermore, if there's no solid consensus, I will restart a community input for new names given the circumstances.
We can also potentially do this at EclipseCon too... maybe have a bucket where people can drop in name suggestions or tweet them @eclipsecon
I'll send an email out on Monday based on the results of this poll.
On Thu, Feb 26, 2015 at 9:27 AM, Doug Schaefer <dschaefer@xxxxxxx> wrote:
I’m actually super keen on numbers. Not sure what you mean by going back to numbers again, Dani. We haven’t done that since the very first release, 3.1, which was barely a simrel. We’ve been using names ever since. Note also that all our main competitors out there use numbers as well. IntelliJ, for example is at IntelliJ 14, Visual Studio has used years ever since they started simultaneous releases.
My main concern right now though is that Naboo is highly unlikely to pass either. The rest of the names are really fringe names. I’d hate to steal thunder from our messaging to explain what the name means.
Doug
From: Daniel Megert <daniel_megert@xxxxxxxxxx>
Reply-To: Eclipse Planning Council private list <eclipse.org-planning-council@xxxxxxxxxxx>
Date: Thursday, February 26, 2015 at 9:00 AM
To: Eclipse Planning Council private list <eclipse.org-planning-council@xxxxxxxxxxx>
Subject: Re: [eclipse.org-planning-council] Mars+1 Naming Issues
I'm fine with either of the two approaches, and not so hot on going back to numbers again.
Dani
From: Chris Aniszczyk <caniszczyk@xxxxxxxxx>
To: Eclipse Planning Council private list <eclipse.org-planning-council@xxxxxxxxxxx>
Date: 25.02.2015 23:04
Subject: Re: [eclipse.org-planning-council] Mars+1 Naming Issues
Sent by: eclipse.org-planning-council-bounces@xxxxxxxxxxx
I think restarting the vote to include O,P,N is the wrong approach and will eat up a lot of time.
My suggested approach is we work down the list of names that weren't vetted yet:
Naboo: 8%
Narvi: 3%
Nash: 2%
Nano: 2%
Nibiru: 2%
Naiad: 1%
I think it's the simpler solution and still respects the initial community input. Plus, some of the names like Nash and Narvi are cool IMHO. If the PC feels strongly about any of the names left in the list, I can create a quick poll for us to vote and move forward with the PC's top choices, as the final decision of a name rests with us.
Any objections towards this approach?
On Wed, Feb 25, 2015 at 3:40 PM, Pascal Rapicault <pascal@xxxxxxxxxxxx> wrote:
I honestly don't think it matters to announce Mars + 1 at EclipseCon
It is probably the case that most ppl don't know the current release name we are going to ship in June, so telling them what will be the next name probably does not matter. It is not like if we were going to start a big marketing effort right away.
IMO if we have it for the day after the release, it is soon enough.
On 02/25/2015 04:31 PM, Doug Schaefer wrote:
We don’t have time for that do we? We’re only 2 weeks away from EclipseCon where I believe we wanted to announce the name (/number).
I’m not sure it’s bad luck. He have had trouble a few times over the years.
Doug.
From: David M Williams <david_williams@xxxxxxxxxx>
Reply-To: Eclipse Planning Council private list <eclipse.org-planning-council@xxxxxxxxxxx>
Date: Wednesday, February 25, 2015 at 4:17 PM
To: "mike.milinkovich@xxxxxxxxxxx" <mike.milinkovich@xxxxxxxxxxx>, Eclipse Planning Council private list <eclipse.org-planning-council@xxxxxxxxxxx>
Subject: Re: [eclipse.org-planning-council] Mars+1 Naming Issues
It does help, Mike, thanks. I probably originally heard "commonly used names", and shorted that in my memory to "common names" where as in legal terms, it means more "generic names". (Which, still doesn't help us lay-people much, in being able to judge such things.)
Given Mike's comment that it was "just bad luck", I still suggest we "restart" expanding the pool to include "O" and "P" as well as "N".
Chris, would you mind? (and, if you can think of how/if to include getting community feedback on "using the year (or other numeral instead)" that might be interesting to know. Such as, if overwhelming support for "just using the year", then ... perhaps we should consider that more seriously? -- then again, if lots of "complaints" about the idea, we'd know not to go down that path.
Thanks,
From: Mike Milinkovich <mike.milinkovich@xxxxxxxxxxx>
To: eclipse.org-planning-council@xxxxxxxxxxx,
Date: 02/25/2015 03:40 PM
Subject: Re: [eclipse.org-planning-council] Mars+1 Naming Issues
Sent by: eclipse.org-planning-council-bounces@xxxxxxxxxxx
On 25/02/2015 3:01 PM, David M Williams wrote:
I also thought, the reason we tended towards names of people, planets, and ancient gods was that we were told "common names" can not be trademarked. Has that changed? Wrong in the first place? Or, is the "external attorney" judging on a different criteria? These are not names *we* want to trademark, right? Would it make a difference if we make "Eclipse" part of "official name" (such as the "Eclipse Mars" release) ... and, don't think anyone would say we could not abbreviate in URLs, etc. to the shorter name of .../releases/mars (for example). [Mike, feel free to take these legal questions, off-line, if appropriate. But, it would help if we had guidance on "types of names" that were not subject to being trademark ... unless there really is no such thing.]
We already do make Eclipse part of the official name.
I'm not sure where the impression that common names cannot be trademarked came from. AFAIK, any name can be trademarked in a given context.
IANAL but as I understand it, there are basically two scenarios where we can use a name: (a) no one is using it, and (b) lot of organizations are using it, so no single entity has a dominant claim.
I do not believe that there is any useful criteria that I (or anyone else) can supply on what kind of names to consider. This year (unlike in the past), every single name we looked at has strong incumbents using that name. It's just bad luck.
Hope that helps.
--
Mike Milinkovich
mike.milinkovich@xxxxxxxxxxx
+1.613.220.3223 (mobile)
_______________________________________________
eclipse.org-planning-council mailing list
eclipse.org-planning-council@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipse.org-planning-council
IMPORTANT: Membership in this list is generated by processes internal to the Eclipse Foundation. To be permanently removed from this list, you must contact emo@xxxxxxxxxxx to request removal.
---------------------------------------------------------------------
This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.
_______________________________________________
eclipse.org-planning-council mailing list
eclipse.org-planning-council@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipse.org-planning-council
IMPORTANT: Membership in this list is generated by processes internal to the Eclipse Foundation. To be permanently removed from this list, you must contact emo@xxxxxxxxxxx to request removal.
_______________________________________________
eclipse.org-planning-council mailing list
eclipse.org-planning-council@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipse.org-planning-council
IMPORTANT: Membership in this list is generated by processes internal to the Eclipse Foundation. To be permanently removed from this list, you must contact emo@xxxxxxxxxxx to request removal.
--
Cheers,
Chris Aniszczyk
http://aniszczyk.org
+1 512 961 6719_______________________________________________
eclipse.org-planning-council mailing list
eclipse.org-planning-council@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipse.org-planning-council
IMPORTANT: Membership in this list is generated by processes internal to the Eclipse Foundation. To be permanently removed from this list, you must contact emo@xxxxxxxxxxx to request removal.
_______________________________________________
eclipse.org-planning-council mailing list
eclipse.org-planning-council@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipse.org-planning-council
IMPORTANT: Membership in this list is generated by processes internal to the Eclipse Foundation. To be permanently removed from this list, you must contact emo@xxxxxxxxxxx to request removal.
--
_______________________________________________ eclipse.org-planning-council mailing list eclipse.org-planning-council@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/eclipse.org-planning-council IMPORTANT: Membership in this list is generated by processes internal to the Eclipse Foundation. To be permanently removed from this list, you must contact emo@xxxxxxxxxxx to request removal.
--
Wayne Beaton
@waynebeaton
The Eclipse Foundation
_______________________________________________
eclipse.org-planning-council mailing list
eclipse.org-planning-council@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipse.org-planning-council
IMPORTANT: Membership in this list is generated by processes internal to the Eclipse Foundation. To be permanently removed from this list, you must contact emo@xxxxxxxxxxx to request removal.
_______________________________________________
eclipse.org-planning-council mailing list
eclipse.org-planning-council@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipse.org-planning-council
IMPORTANT: Membership in this list is generated by processes internal to the Eclipse Foundation. To be permanently removed from this list, you must contact emo@xxxxxxxxxxx to request removal.
