From: "James Homuth" <james@the-jdh.com>
To: <speakup@braille.uwo.ca>
Subject: Possibly OT: general Linux accessibility channel on IRC?
Date: Mon, 12 Jan 2009 03:24:33 -0500 [thread overview]
Message-ID: <01bb01c9748f$338af5a0$6400a8c0@quan> (raw)
I appologise if this belongs anywhere but on these lists, however I'm rather
curious on the subject and figured this would be the best possible way to
get the opinions of the people to whom it would be most relevant. I was
wondering what the general opinion would be of a linux accessibility
channel, geared not specificly to Orca or Speakup, but to accessibility in
general; whether you use command line or desktop, Orca or Speakup, or even
Emaxspeak. Interested parties can contact me off-list, and we can go from
there. I was thinking of using the OFTC IRC network, as it seems most geared
towards the idea behind not just Linux, but accessibility. Again, I
appologise if this is off topic in any way and would encourage anyone with
an interest, because of the possible off-topic nature, to mail me privately.
Sincerely,
James Homuth
next reply other threads:[~ UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
James Homuth [this message]
` Samuel Thibault
` Nick Gawronski
` Kirk Reiser
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='01bb01c9748f$338af5a0$6400a8c0@quan' \
--to=james@the-jdh.com \
--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).