All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rik van Riel <riel@redhat.com>
To: Kurt Skurtveit <kskurt@gmail.com>
Cc: xen-devel@lists.xensource.com, bstein@redhat.com
Subject: Re: open source and trademark
Date: Sat, 07 Oct 2006 14:48:34 -0400	[thread overview]
Message-ID: <4527F682.5000803@redhat.com> (raw)
In-Reply-To: <ad1107850610062255w48889bf6s9e48251d934fbc2e@mail.gmail.com>

Kurt Skurtveit wrote:

>> Given internal (and external) concerns with our upcoming inclusion of a
>> hypervisor-based on a popular open source project, we're considering
>> using a neutral reference: 'CNH' - Common Neutral Hypervisor
>> I hope this is an acceptable term for others with similar issues.
> 
> This is from the same Red Hat that has the most restrictive of
> trademark policies in the open source world with Fedora Core and RHEL?
> Please, climb off your soap box.

It's not a question of soap box, but a question of "collection"
vs "component", as well as a question of practical matters.

Components like glibc, the Linux kernel, Xen, and other programs
need to be maintained for years in RHEL.  Probably way beyond the
time where XenSource would still be interested in approving patches
for 3.0.3.   If XenSource were to lose interest in supporting an
old release, that should not mean distributions lose their ability
to support users using that release.

Personally, I think Debian was right with their "iceweasel" decision.

As to the RHEL and Fedora trademarks, there is a reason that all the
trademarked bits are nicely separated out into their own RPMs.  We
intentionally make it easy for people to rename things. There might
be something on that in the Fedora lists archives, not sure though...

Renaming things may be inconvenient, but not being able to properly
support users is outright dangerous.  As long as the distributions
can agree on a common name for "the hypervisor formerly known as Xen",
the renaming shouldn't be all that bad.

-- 
Who do you trust?
The people with all the right answers?
Or the people with the right questions?

  parent reply	other threads:[~2006-10-07 18:48 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-07  5:55 open source and trademark Kurt Skurtveit
2006-10-07 13:02 ` Brian Stein
2006-10-07 18:48 ` Rik van Riel [this message]
2006-10-07 20:01   ` Daniel P. Berrange
  -- strict thread matches above, loose matches on Subject: below --
2006-10-04 17:31 alex
2006-10-04 22:19 ` Steven Hand
2006-10-06 18:34   ` Brian Stein
2006-10-07 14:54   ` Bastian Blank
2006-10-03 18:29 Ben Thomas
2006-10-03 20:24 ` Aron Griffis
2006-10-03 21:34   ` Bastian Blank

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=4527F682.5000803@redhat.com \
    --to=riel@redhat.com \
    --cc=bstein@redhat.com \
    --cc=kskurt@gmail.com \
    --cc=xen-devel@lists.xensource.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.