public inbox for ecos-maintainers@sourceware.org
 help / color / mirror / Atom feed
From: Jonathan Larmour <jifl@eCosCentric.com>
To: Gary Thomas <gary@mlbassoc.com>
Cc: eCos Maintainers <ecos-maintainers@sources.redhat.com>,
	Alex Schuilenburg <alexs@ecoscentric.com>
Subject: Re: Patch policy
Date: Wed, 07 May 2003 23:02:00 -0000	[thread overview]
Message-ID: <3EB99066.1030502@eCosCentric.com> (raw)
In-Reply-To: <1052344447.30126.14197.camel@hermes>

Gary Thomas wrote:
> 
> I'm OK with this.  BTW, can we actuall use the eCos logo that's on the
> page?

An interesting point. Here's my interpretation (although IANAL):

By the strictest legal definition anybody should seek permission for use 
of trademarks. But that's true with _any_ use of trademarks so we couldn't 
even mention "eCos". As you can see, out on the net, that's not true, and 
it is well established that you cannot defend a trademark in one place if 
you've never defended it elsewhere, so we're pretty safe. And established 
practice (and case law) says you can, as long as there's no attempt to 
pass off, normally by acknowledging the trademark.

We also have a considerable defence in using it because of the continuity 
of "permission"... Red Hat established the eCos site on sourceware and 
have continued to allow us to use and enhance it.... this is just one of 
those enhancements. The fact it resides on a different machine should make 
no difference.

What we may need to have on there is a "Legal information" link to 
acknowledge that eCos/RedBoot and the logo are trademarks of Red Hat, or 
just written in small font text at the bottom.

Interestingly, the main s.r.c eCos and redboot websites have _never_ 
mentioned trademarks, nor has the logo ever had a (TM) superscript. The 
logo isn't a registered trademark AFAIK, so RH's legal protection is minimal.

Of course the other strong argument is that Red Hat don't really have any 
desire to make a fuss when the point is that they don't intend to assert 
control over eCos any more.

Jifl
-- 
eCosCentric    http://www.eCosCentric.com/    The eCos and RedBoot experts
--[ "You can complain because roses have thorns, or you ]--
--[  can rejoice because thorns have roses." -Lincoln   ]-- Opinions==mine

  parent reply	other threads:[~2003-05-07 23:02 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-06 12:59 Gary Thomas
2003-05-06 13:17 ` Mark Salter
2003-05-06 13:26 ` Andrew Lunn
2003-05-06 13:34   ` Gary Thomas
2003-05-06 13:40     ` Andrew Lunn
2003-05-06 13:44       ` Gary Thomas
2003-05-06 14:51       ` Jonathan Larmour
2003-05-06 14:46   ` Jonathan Larmour
2003-05-07 20:30     ` Jonathan Larmour
2003-05-07 21:54       ` Gary Thomas
2003-05-07 22:48         ` Alex Schuilenburg
2003-05-07 23:02         ` Jonathan Larmour [this message]
2003-05-07 23:39           ` Alex Schuilenburg
2003-05-07 23:55             ` Jonathan Larmour
2003-05-08  0:18               ` Alex Schuilenburg
2003-05-08  3:16                 ` Jonathan Larmour
2003-05-08  9:45                   ` Alex Schuilenburg
2003-05-07 23:27       ` Alex Schuilenburg
2003-05-06 15:00 ` Jonathan Larmour
2003-05-06 15:06   ` Gary Thomas

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3EB99066.1030502@eCosCentric.com \
    --to=jifl@ecoscentric.com \
    --cc=alexs@ecoscentric.com \
    --cc=ecos-maintainers@sources.redhat.com \
    --cc=gary@mlbassoc.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).