From: Jason Molenda <jason@molenda.com>
To: overseers@sources.redhat.com
Subject: Re: suggested change to sources.redhat.com page
Date: Wed, 01 Nov 2000 10:53:00 -0000 [thread overview]
Message-ID: <20001101105239.A10573@shell17.ba.best.com> (raw)
Message-ID: <20001101105300.0vXMIDjdM0GTT3BqxK-ymO0kg2_3Ni6NlkKA-DsgElg@z> (raw)
In-Reply-To: <20001101103628.A6983@shell17.ba.best.com>
On Wed, Nov 01, 2000 at 10:36:28AM -0800, Jason Molenda wrote:
> My two cents: Of course it's inappropriate, that's why I wrote
> it. Y'all can decide if you want to change it (I'm not going to
> mind one way or the other), but it isn't accidental
I suppose I could stand to expand on this a bit.
I went overly informal on the front sourceware web page to make it
clear to users that they were no longer on a corporate site. This
was largely in reaction to our earlier pathetic attempts to have
a corporate spin on free software PR (I'm thinking of the time
around 1994 - 1998). Our cygnus.com site was trying so desperately
to be a large corporation that we looked like weak posers, and it
was so marketing-drenched that the important technical facts rarely
got through it all.
On sourceware I wanted to divorce from that corporate presence
entirely. The only things marketing had a hand in are the mission
statement (I would never have written one, but it wasn't terrible
so I didn't mind) and the front page graphic (I think we paid some
consultant $1k or so to come up with "red").
Given that historical background, I wanted net.developers to know
that they were in a press release-free zone when they were on
sourceware, that they wouldn't have to wade through any marketing-style
English with little technical credence, that they would not see
"headquarter" used as a verb.
Maybe this isn't as necessary these days (I haven't looked at
redhat.com in a long time), in which case the change that this
person sent in is not objectionable - it still maintains the
important point of the privacy statement.
Jason
next prev parent reply other threads:[~2000-11-01 10:53 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-30 6:08 Mark Sobell
2000-11-01 10:09 ` Mark Sobell
2000-12-30 6:08 ` Jason Molenda
2000-11-01 10:37 ` Jason Molenda
2000-12-30 6:08 ` Phil Edwards
2000-11-01 11:04 ` Phil Edwards
2000-12-30 6:08 ` Benjamin Kosnik
2000-11-01 12:26 ` Benjamin Kosnik
2000-12-30 6:08 ` Christopher Faylor
2000-11-01 11:35 ` Christopher Faylor
2000-12-30 6:08 ` Jason Molenda [this message]
2000-11-01 10:53 ` Jason Molenda
2000-12-30 6:08 ` Frank Ch. Eigler
2000-11-01 10:49 ` Frank Ch. Eigler
2000-12-30 6:08 ` Jim Kingdon
2000-11-01 13:52 ` Jim Kingdon
2000-12-30 6:08 ` sources.redhat.com Paul Weinstein
2000-11-01 16:49 ` sources.redhat.com Paul Weinstein
2000-12-30 6:08 ` sources.redhat.com Tom Tromey
2000-11-02 12:07 ` sources.redhat.com Tom Tromey
2000-12-30 6:08 ` sources.redhat.com Paul Weinstein
2000-11-02 13:49 ` sources.redhat.com Paul Weinstein
2000-12-30 6:08 ` suggested change to sources.redhat.com page Ian Lance Taylor
2000-11-01 11:59 ` Ian Lance Taylor
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=20001101105239.A10573@shell17.ba.best.com \
--to=jason@molenda.com \
--cc=overseers@sources.redhat.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).