From: "John Heim" <jheim@math.wisc.edu>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: gentoo drops speakup
Date: Mon, 16 Jul 2007 09:16:47 -0500 [thread overview]
Message-ID: <01bb01c7c7b3$f1c52110$4ba65c90@vv507j> (raw)
In-Reply-To: <20070715163625.GA10814@localhost.localdomain>
> This isn't big news, speakup works just fine the way it is up to and
> including 2.6.21.6. I would not be at all surprised therefore if
> slackware were to drop speakup by their next release, if the current
> issues with speakup weren't fixed by that time. It would surprise me
> greatly though to see a distro's team of maintainers take it upon
> themselves to cure speakup's serial code and other problems, just so
> they could include a speakup-patched kernel in their next
> release. Note, I am not saying myself that speakup has problems, I
> haven't looked at the code for a while. I'm just repeating what others
> have said on this in the past, so no flames if you please.
I would like to know what, if anything, can be done to get the resources
allocated that are needed to fix this problem. Could the kernel development
team fix it if they wanted to? What determines their priorities and where
does the development time come from?
I wonder if it would help to draw attention to the problem. What is the NFB
doing about this? They are always talking about jobs. It seems to me that a
lot of jobs for blind people depend on speakup. It's conceivable that a
group like the NFB might even be willing to put up enough money to have
somebody work on it for 3 months or 6 months or whatever it would take to
fix the problem. Who knows? It might be worth exploring anyway.
But maybe I'm out of bounds. I don't want to step on anybody's toes. I don't
think it would be worthwhile for me to volunteer to work on the code. But if
I can help in some other way...
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
josh
` Luke Yelavich
` Zachary Kline
` Ralph W. Reid
` Gregory Nowak
` John Heim [this message]
` Chuck Hallenbeck
` Kirk Reiser
` Albert E. Sten-Clanton
` Georgina Joyce
` John Heim
` Gregory Nowak
` Travis Siegel
` Joseph C. Lininger
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='01bb01c7c7b3$f1c52110$4ba65c90@vv507j' \
--to=jheim@math.wisc.edu \
--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).