public inbox for blinux-list@redhat.com
 help / color / mirror / Atom feed
From: "Marc E. Christensen" <marc@ssv1.union.utah.edu>
To: mikedlr@it.com.pl, raman@mv.us.adobe.com,
	zocki@goldfish.cube.net, info@caldera.com, redhat@redhat.com,
	linux@pht.com, questions@infomagic.com, debian@debian.org,
	info@craftwork.com, LeBlanc@mcc.ac.uk, info@trans-am.com,
	info@cdrom.com, info@wgs.com, info@yggdrasil.com,
	info@lasermoon.co.uk
Cc: marc@ssv1.union.utah.edu
Subject: linux-access mailing list and invitation
Date: Wed, 31 Jul 1996 18:52:40 -0600 (MDT)	[thread overview]
Message-ID: <Pine.LNX.3.91.960731155635.3443D-100000@ssv1.union.utah.edu> (raw)


        This message is being sent out to developers of Linux
distributions and/or software.  It is not an automated mailing, it has
specifically been sent to you.

        There is a new Linux related mailing list that has recently been
created in order to help build support for Linux users with disabilities.
There are many people with disabilities who use the Linux operating
system, it is important to facilitate their needs as you develop products,
and/or distributions.  linux-access is a list created specifically to 
share ideas among developers and users of Linux in areas associated with
accessesability.

        The main focus of linux-access will be on developing and enhancing
access related technology, not on advocacy. In other words, while input is
welcome from all parties, this is not intended to be another "chat list"
but instead, a list which actively seeks solutions to access related
issues.

        I would like to extend an invitation for you, your organization or
company to participate in discussions on this list.  At the very least, 
join the list in order to listen in and get ideas for making your
products/projects more accessible as well as receive feedback.

        More information about the list is locate on the University of
Utah's Center for Disabled Student Services web site at:

        http://ssv1.union.utah.edu/CDSS/other/mailing_lists.html

        Information includes information about the list as well as
relative announcements which have been made.

Thank you,

--
Marc Christensen
SysOp CDSS University of Utah
http://ssv1.union.utah.edu








                 reply	other threads:[~ UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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.3.91.960731155635.3443D-100000@ssv1.union.utah.edu \
    --to=marc@ssv1.union.utah.edu \
    --cc=LeBlanc@mcc.ac.uk \
    --cc=debian@debian.org \
    --cc=info@caldera.com \
    --cc=info@cdrom.com \
    --cc=info@craftwork.com \
    --cc=info@lasermoon.co.uk \
    --cc=info@trans-am.com \
    --cc=info@wgs.com \
    --cc=info@yggdrasil.com \
    --cc=linux@pht.com \
    --cc=mikedlr@it.com.pl \
    --cc=questions@infomagic.com \
    --cc=raman@mv.us.adobe.com \
    --cc=redhat@redhat.com \
    --cc=zocki@goldfish.cube.net \
    /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).