From: Matthew Galgoci <mgalgoci@redhat.com>
To: law@redhat.com
Cc: Ian Lance Taylor <ian@airs.com>,
Christopher Faylor <cgf@redhat.com>, <overseers@sourceware.org>
Subject: Re: Officially changing name to sourceware.org
Date: Fri, 05 Dec 2003 23:40:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.44.0312051838400.27170-100000@lacrosse.corp.redhat.com> (raw)
In-Reply-To: <200312052221.hB5MLtlS003113@speedy.slc.redhat.com>
> >There is a different company which owns the domain name
> >sourceware.com: Datasource Software Corporation.
> >
> >I own the domain name sourceware.org, and for some time now
> >sourceware.org has been an alias for sources.redhat.com.
> >
> >Anyhow, we may not want to use sourceware for commercial purposes.
> >But I don't think it would be a big problem to use sourceware.org.
> Is Pliant Technologies the company in Atlanta that was giving us
> a hard time about the "sourceware" name? IIRC they effectively
> demanded that we stop using the sourceware name, which eventually
> led to sources.redhat.com.
pliant was purchased by Market Central, Inc.
http://www.findarticles.com/cf_dls/m0EIN/2003_August_7/106394987/p1/article.jhtml
Perhaps someone should approach them and ask if for a legal document that would
give us the a-ok to use sourceware.org?
--
Matthew Galgoci
System Administrator
Red Hat, Inc
919.754.3700 x44155
next prev parent reply other threads:[~2003-12-05 23:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-04 23:34 Christopher Faylor
2003-12-04 23:49 ` Matthew Galgoci
2003-12-05 0:15 ` Ian Lance Taylor
2003-12-05 22:23 ` law
2003-12-05 23:40 ` Matthew Galgoci [this message]
2003-12-05 23:42 ` Jason Molenda
2003-12-05 23:52 ` Matthew Galgoci
2003-12-06 0:00 ` Jason Molenda
2003-12-06 0:02 ` Matthew Galgoci
2003-12-06 0:39 ` Christopher Faylor
[not found] ` <20031204161637.A81068@molenda.com>
2003-12-05 0:16 ` Jason Molenda
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=Pine.LNX.4.44.0312051838400.27170-100000@lacrosse.corp.redhat.com \
--to=mgalgoci@redhat.com \
--cc=cgf@redhat.com \
--cc=ian@airs.com \
--cc=law@redhat.com \
--cc=overseers@sourceware.org \
/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).