From: "Albert E. Sten-Clanton" <albert.e.sten_clanton@verizon.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: Software speech opinions
Date: Tue, 26 Jun 2007 13:03:40 -0400 [thread overview]
Message-ID: <002d01c7b813$f27baf70$6405a8c0@ALBERTLC7SN0ZA> (raw)
In-Reply-To: <047301c7b809$9b0d3920$4ba65c90@vv507j>
> I would ask people spouting off in this thread to ask themselves what *they*
> have contributed. It seems to me that a lot of people are making suggestions
> for what other people should do or sell.
>
> Say the best thing to do is to move speakup into user space. How is that
> going to get done? I guess we're all going to volunteer Kirk to do it. Eh?
You seem to be saying that the mere users should keep their traps shut. In real life, a good majority of the people who use computers will know little or nothing about how to fix the problems that arise. Do you really propose that these people, such as my wife, have no business complaining or suggesting because they're not ultranerds?
As for myself, I do intend to learn enough to work on speakup and other code. I'm a programmer; that stuff grabs me; I hope to make a living at it again. but if I were to try to "contribute" at the moment, the worst code ever found in the kernel or in Speakup would look like utter beauty and perfection compared to what I'd write. You'd want me executed for pretending I could do anything useful! Yet, for me to learn what I need to, I need things to work well enough, just like the users I know who'd rather swallow thumbtacks than write programs. I can think of no reason I should refrain from making suggestions for improvement, if I treat people right when I do it.
Nobody here said that he or she had appointed Kirk to do all the work folks want. Kirk would probably punch out anybody who tried to do that. Ignorant as I am, however, I think I can tell that a number of people on this list know enough to do the job, and maybe some of them will when they have the time. If so, I'd bet the suggestions put here will be of some help to them in deciding how best to use that time. If that doesn't happen, well, then those of us who can't do the job, for whatever reasons, will either endure the problems or look for a better system.
Al
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
Keith Hinton
` Jan Buchal
` Doug Sutherland
` Gaijin
` Doug Sutherland
` C.M. Brannon
` Travis Siegel
` Glenn Ervin
` Doug Sutherland
` Gaijin
` Gregory Nowak
` Gaijin
` Doug Smith
` Doug Sutherland
` Gaijin
` Glenn Ervin
` Doug Sutherland
` Glenn Ervin
` Steve Holmes
[not found] ` <20070626042409.GA25331@cm.nu>
` Glenn Ervin
` John Heim
` Albert E. Sten-Clanton [this message]
` John Heim
` Glenn Ervin
` Scott Berry
` John Heim
` Scott Berry
` Albert E. Sten-Clanton
` Doug Sutherland
` Doug Sutherland
` Glenn Ervin
` John Heim
` Butch Bussen
` John Heim
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='002d01c7b813$f27baf70$6405a8c0@ALBERTLC7SN0ZA' \
--to=albert.e.sten_clanton@verizon.net \
--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).