From: ccrawford@acb.org
To: speakup@braille.uwo.ca
Subject: Re: RH9 disks on the net.
Date: Tue, 8 Apr 2003 10:35:59 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.44.0304081029001.7733-100000@localhost.localdomain> (raw)
In-Reply-To: <20030408104401.GA1594@borg.optusnet.com.au>
OK OK Everyone; I am right and the world is wrong. Smile.
Since accessibility to Redhat or any other operating system is a
legal acre of quicksand, it's probably best that we use diplomatic
levers to get them to incorporate access. This does not mean please
please please, it means we need to continue to communicate with them and
remind them of the advantages to sales within certain areas such as
federal procurements. This is especially true in an open source and
volunteer environment that has a curious mix of commercialism.
Since we want to promote accessible linux environments then we
should do that with Redhat and anyone else who will listen. Over time
we can garner more territory in the OS and once material connections are
made to the workplace we will have the kind of leverage that gets into
legal issues.
Hope this helps.
-- Charlie Crawford.
On Tue, 8 Apr 2003, Shaun Oliver wrote:
> *SNIP*
> Was it Redhat that acquired AFB or was it the other way around?
> *SNIP*
>
> here's my $0.2 worth on the subject.
> janina, I've normally seen your side of the argument a good deal of the
> time. and each time you've provided what I would consider reasonable
> arguments.
> not that everyone else agrees with them though, and even I don't agree
> with all of them.
> however, when one starts to make personal attacks on people suggesting
> the possibility of their hearing voices, and how dare you pick on my
> beloved red hat, and shooting off your mouth, or in this case, keyboard
> calls into question your competency as an advocate for people with
> visual impairments. there's no need for such attacks on this list and
> yes, even I'm guilty of it from time to time. however, that doesn't
> excuse your actions in previous posts to this list on this matter.
> save your personal attacks for your partner in heated discussions or
> arguments. let's keep it real people, we're in the business of helping.
> and let's help where we can however we can whenever we can.
> like kirk says, why be helpful when you are not.
> thank you for listening to my rantings.
>
>
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 73+ messages / expand[flat|nested] mbox.gz Atom feed top
William F. Acker WB2FLW +1-303-722-7209
` Darrell Shandrow
` William F. Acker WB2FLW +1-303-722-7209
` Darrell Shandrow
` Janina Sajka
` Janina Sajka
` Luke Davis
` Janina Sajka
` Luke Davis
` Janina Sajka
` Aaron Howell
[not found] ` <20030408153227.GA3492@rednote.net>
` Janina Sajka
` Luke Davis
` Aaron Howell
` Janina Sajka
` Aaron Howell
` Aaron Howell
` Adam Myrow
` Aaron Howell
` Janina Sajka
` Darrell Shandrow
` Chuck Hallenbeck
` Shaun Oliver
` ccrawford [this message]
` Janina Sajka
` Shaun Oliver
` Janina Sajka
` Steve Holmes
` Thomas D. Ward
` Gregory Nowak
` Linux distros (was Re: RH9 disks on the net.) Adam Myrow
` Doug Sutherland
` Gregory Nowak
` Doug Sutherland
` Lorenzo Prince
` Doug Sutherland
` Luke Davis
` Doug Sutherland
` Luke Davis
` Doug Sutherland
` Lorenzo Prince
` Doug
` Luke Davis
` Doug
` Alex Snow
` Thomas D. Ward
` Buddy Brannan
` Alex Snow
` RH9 disks on the net Thomas D. Ward
` Darrell Shandrow
` Janina Sajka
` Gregory Nowak
` Darrell Shandrow
` Janina Sajka
` Charles Crawford
` Shaun Oliver
` Shaun Oliver
` Darrell Shandrow
` Aaron Howell
` Darrell Shandrow
` Tommy Moore
` Darrell Shandrow
` Aaron Howell
` Lorenzo Prince
` Aaron Howell
` Luke Davis
` ccrawford
` ccrawford
` Janina Sajka
` Gregory Nowak
` Steve Holmes
` Thomas D. Ward
` Thomas D. Ward
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.0304081029001.7733-100000@localhost.localdomain \
--to=ccrawford@acb.org \
--cc=speakup@braille.uwo.ca \
/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).