From: "Glenn K0LNY" <glennervin@cableone.net>
To: "Chris Brannon" <chris@the-brannons.com>, <speakup@linux-speakup.org>
Subject: Re: announcing: Blind and Low Vision Unix Users Group
Date: Fri, 19 Feb 2021 14:44:09 -0600 [thread overview]
Message-ID: <00a601d706ff$f9682c60$6400a8c0@NUCPPYH> (raw)
In-Reply-To: <877dn3sse1.fsf@the-brannons.com>
Hi Chris,
Is there a screenreader for Unix?
Thanks
Glenn
----- Original Message -----
From: "Chris Brannon" <chris@the-brannons.com>
To: <speakup@linux-speakup.org>
Sent: Friday, February 19, 2021 2:40 PM
Subject: announcing: Blind and Low Vision Unix Users Group
Hi folks,
This is a vision I've had for many years, and now I'm slowly starting to
realize it. More information is at https://blvuug.org but I will paste
the markdown source for the homepage inline. It is readable plaintext
and I don't have to repeat myself.
I'm sorry if anyone is annoyed by the self-promotion, but I suspect most
people on this list might be interested. Please feel free to spread
this around.
# Blind and Low-Vision Unix Users Group
Welcome to BLVUUG, the Blind and Low-Vision Unix Users Group.
We are a not-for-profit association of people working to improve and promote
greater accessibility of free Unix operating systems for the visually
disabled.
The group is founded on the principles of mutual aid and cooperating to
advance the
social good. There isn't much here yet. The rest of the page is an
informal charter. If all of this sounds exciting to you, please subscribe
to the mailing list:
[discuss+subscribe@blvuug.org](mailto:discuss+subscribe@blvuug.org).
## Abstract Goals
* To promote communication among blind and low vision Unix users and to
connect them with potential sighted allies.
* To foster collaboration among people working on Unix-based adaptive
technology for people with visual disabilities.
* Eventually, to serve as a vehicle for funding development of said
technologies.
* To enable community members to promote products or services generally
useful to the blind Unix community.
## Concrete Goals
We'll be adding a code forge (a la github and other code hosting sites)
to be a home for accessibility related projects. We promise that it will
be something that is usable from a text mode web browser and with
command-line
tools. In other words, it will be aggressively interoperable and
fluff-free.
We will also add a forum for communication among the community. Again,
the promise of aggressive interoperability is made for the forum. It
should be usable from email, web, and hopefully NNTP.
We will have a "classified ads" section on the site or as part of the forum.
Out of principle,
we will *never* accept paid advertising. The purpose of the classifieds
is to connect and enable, rather than foster mindless consumerism or
profiteering.
## Legalese
In the US state of Oregon, where BLVUUG's founder resides, this group
is considered a "not for profit association" under Oregon law. Here's a
little blurb cribbed from
[Nonprofit Association of
Oregon](https://nonprofitoregon.org/helpline_resources/tools_information/faqs/starting_a_nonprofit),
discussing what this means and comparing nonprofit associations and
nonprofit corporations.
>Oregon nonprofits can be either unincorporated associations or
>corporations.
>If you do not file Articles of Incorporation with the Secretary of State,
>your organization will be an unincorporated association by default.
>An unincorporated association is defined as a group of people who come
>together
>for some purpose other than to do business, such as book clubs,
>small hobby groups, etc.
>
>The positive aspects of associations are:
>
>* There are no registration or reporting requirements to the Oregon
>Secretary of State or DOJ
>* There is greater flexibility in how the organization is run
>* Change in membership doesn’t impact the existence of the organization
>
>The negative aspects of associations are:
>
>* There is no protection for the members. Everyone involved is equally and
>personally liable for the debts and lawsuits
>* It is not possible to open a bank account because the association cannot
>obtain an Employer Identification Number (EIN). Anyone in the association
>can open a personal bank account on behalf of the association, but this can
>blur the line between personal and association assets
>
>Unincorporated associations are often most appropriate for groups with
>smaller
>budgets. They are a poor choice if your organization will be engaging in
>any
>activities with potential financial risk or that might result in physical
>or
>emotional injuries. Corporations, on the other hand,
>provide a much higher degree of legal protection for the individuals
>involved.
>They are also subject to more reporting requirements and to ORS 65.
>The legal liability protection is often enough reason to choose this
>structure.
At some point, especially if we start connecting projects with funding, it
might be advisable to incorporate. That's a problem for another day.
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
Chris Brannon
` Glenn K0LNY [this message]
` Chris Brannon
` Didier Spaier
` chris
` Mike Ray
` Chris Brannon
` MENGUAL Jean-Philippe
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='00a601d706ff$f9682c60$6400a8c0@NUCPPYH' \
--to=glennervin@cableone.net \
--cc=chris@the-brannons.com \
--cc=speakup@linux-speakup.org \
/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).