On Wednesday 13 October 2010 22:05:40 Ibrahim Haddad wrote:
> Hello Andrew,
> 
> Please accept my apologies for late reply. This is regarding your request
> to use:
> 
>        Smeegol, an openSUSE release based on the netbook user interface
> that came from the Meego(TM)* project.
>        * Meego is a trademark of the Linux Foundation.

I agree with Andrew and Greg that it's a wee bit late to respond AFTER the 
release now... The last email in this thread was from 26/9 and you promised an 
answer 'in the day or two' on 21/9.

I'm not blaming you, the whole process here is strange to say the least. There 
is little if any clear documentation on compliance, the sites you pointed to 
contain little or no information as to the usage of MeeGo. And the link on 
linux-foundation-trademark-usage-guidelines you mentioned a few times from my 
IANAL-pov doesn't seem to forbid the usage of MeeGo from the announcement. Not 
even mentioning the unclear situation with regard to what "the MeeGo stack" 
actually is and isn't.

> In order to maintain the MeeGo mark, the Linux Foundation must consistently
> control the use of any form of the word MeeGo and the related logos and
> characters to avoid confusion.
>
> Unfortunately, from a trademark law perspective, the proposed usage above
> is absolutely not recommended, as such usage will weaken the MeeGo mark
> and make it less enforceable.
> 
> It is not in the benefit of MeeGo project to use "Smeegol". We therefore
> can not approve such usage of MeeGo mark in "Smeegol". We understand that
> you've already announced it and we will be happy to work with you to come
> up with a different name (for the good of the MeeGo project).

Ok, LF thinks the name Smeegol, while funny and inventive, might not be the 
best name of the decade.

Is LF OK with saying:

DarkRider, an openSUSE release based on the netbook user interface
 that came from the Meego(TM)* project.
        * Meego is a trademark of the Linux Foundation.

And can you confirm that the rest of the wording of the announcement and the 
way the software has been build is fine with the Linux Foundation? Of course, 
I'm sure Andrew would remove any left-overs of MeeGo logo's and graphics he 
finds.

Or must we remove any reference to MeeGo? From both the announcement and the 
product? And by then it's OK to use the name Smeegol? And when can we expect, 
as Andrew asks, a list of what has to be removed? Must we go as far as to 
rename package names?

Thanks,
Jos Poortvliet
(openSUSE community manager)

> Thank you,
> Ibrahim
> 
> On Mon, Sep 20, 2010 at 2:42 PM, Andrew Wafaa <[email protected]> wrote:
> > Firstly sorry if this is the wrong list to send this question to, please
> > advise on the best one if it isn't here.
> > 
> > I have been spending my time trying to get the MeeGo UX into reasonable
> > shape on my preferred distro of choice - openSUSE.  Now before I make
> > any form of release/spin/$WHATEVER I would just like to get
> > clarification on what I can/can't use.
> > 
> > My understanding is that to use the word "MeeGo" in any direct naming is
> > a no-no unless I pass compliance, of which part of that would mean
> > taking on Connman and other parts of the MeeGo stack that just aren't in
> > my preferred distro and to be honest, we wouldn't want them in there as
> > we have a well tried & tested stack.
> > 
> > So my simple question is, if I use the MeeGo UX can I say "$RELEASE is
> > based on MeeGo's User eXperience, sitting ontop of $DISTRO.
> > Complimenting the other Desktop Environments that are on offer, and
> > offering some additional components (listing components).
> > 
> > When things were Moblin, there was a clearly defined usage of UX.  This
> > seems to have disappeared under MeeGo so things aren't as simple as they
> > used to be.
> > 
> > Many thanks,
> > 
> > Andy
> > 
> > --
> > Andrew Wafaa
> > IRC: FunkyPenguin.
> > GPG: 0x3A36312F
> > openSUSE: Get It, Discover It, Create It at http://www.opensuse.org
> > 
> > _______________________________________________
> > MeeGo-dev mailing list
> > [email protected]
> > http://lists.meego.com/listinfo/meego-dev

Attachment: signature.asc
Description: This is a digitally signed message part.

_______________________________________________
MeeGo-dev mailing list
[email protected]
http://lists.meego.com/listinfo/meego-dev

Reply via email to