From: Per Bothner <per@bothner.com>
To: overseers@sourceware.cygnus.com
Subject: Re: rename: narrowing it down
Date: Sat, 30 Dec 2000 06:08:00 -0000 [thread overview]
Message-ID: <m2hfc5x9a5.fsf@kelso.bothner.com> (raw)
In-Reply-To: <200005111602.MAA11419@devserv.devel.redhat.com>
I like Sources.redhat.com, but I see your point that it might imply it
contains "all the source to Red Hat's products". Solution: make sure
it does, or at least point to it. I.e. if you call it
sources.redhat.com, then it should have a prominent pointer to where
source rpms, and other source to open-source redhat code. It doesn't
have to be on the site itself, but there should be a pointer. On the
other hand, if you want to compete with sourceforge, perhaps you don't
want to make the reference to redhat sources *too* prominent on the
page - but it must be prominentenough that people looking for redhat
sources can find them.
The same comments may apply to some of the other suggestions, but
less strongly.
--
--Per Bothner
per@bothner.com http://www.bothner.com/~per/
WARNING: multiple messages have this Message-ID
From: Per Bothner <per@bothner.com>
To: overseers@sourceware.cygnus.com
Subject: Re: rename: narrowing it down
Date: Thu, 11 May 2000 10:58:00 -0000 [thread overview]
Message-ID: <m2hfc5x9a5.fsf@kelso.bothner.com> (raw)
Message-ID: <20000511105800.HMd6EPOhgp0MzeyF3WAnjuCnB4PpOZCcnCu37q5bMQY@z> (raw)
In-Reply-To: <200005111602.MAA11419@devserv.devel.redhat.com>
I like Sources.redhat.com, but I see your point that it might imply it
contains "all the source to Red Hat's products". Solution: make sure
it does, or at least point to it. I.e. if you call it
sources.redhat.com, then it should have a prominent pointer to where
source rpms, and other source to open-source redhat code. It doesn't
have to be on the site itself, but there should be a pointer. On the
other hand, if you want to compete with sourceforge, perhaps you don't
want to make the reference to redhat sources *too* prominent on the
page - but it must be prominentenough that people looking for redhat
sources can find them.
The same comments may apply to some of the other suggestions, but
less strongly.
--
--Per Bothner
per@bothner.com http://www.bothner.com/~per/
next prev parent reply other threads:[~2000-12-30 6:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-30 6:08 Jim Kingdon
2000-05-11 9:02 ` Jim Kingdon
2000-12-30 6:08 ` LAST CALL on sources.redhat.com Jim Kingdon
2000-05-15 13:17 ` Jim Kingdon
2000-12-30 6:08 ` Per Bothner [this message]
2000-05-11 10:58 ` rename: narrowing it down Per Bothner
2000-12-30 6:08 ` Benjamin Kosnik
2000-05-12 9:58 ` Benjamin Kosnik
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=m2hfc5x9a5.fsf@kelso.bothner.com \
--to=per@bothner.com \
--cc=overseers@sourceware.cygnus.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).