From: "Scott Berry" <sberry@northlc.com>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: Software speech opinions
Date: Tue, 26 Jun 2007 19:08:51 -0500 [thread overview]
Message-ID: <005601c7b84f$5bea08e0$c701a8c0@yellobow> (raw)
In-Reply-To: <06af01c7b81e$30ae08b0$4ba65c90@vv507j>
Right John,
I agree but have to disagree too. I have started helping for the first time
a site that I run software for my router off of. It is called www.xwrt.org
they make a web interface for Wrt project which can be found at
http://www.openwrt.org. But working for instance with a wiki is a bit of a
trick. That seems to be about how 90% (percent) of the open source docs are
kept. Now as for speakup, I do not use Speakup I do all admin chores
remotely through a Windows computer which works fine for me. So as for
Speakup I don't use it but like to keep current on it. I don't know how to
program in Linux at all. I don't expect Kirk to do everything either but it
is very good to voice. That might just be how the Speakup gets changed at
some point. I myself would like to see Speakup in the kernel and user space
we would have the best of both world.
TTFN,
Scott
----- Original Message -----
From: "John Heim" <jheim@math.wisc.edu>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Sent: Tuesday, June 26, 2007 1:17 PM
Subject: Re: Software speech opinions
>
> ----- Original Message -----
> From: "Albert E. Sten-Clanton" <albert.e.sten_clanton@verizon.net>
> To: "Speakup is a screen review system for Linux."
> <speakup@braille.uwo.ca>
> Sent: Tuesday, June 26, 2007 12:03 PM
> Subject: Re: Software speech opinions
>
>
>>> 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
>
> I never said anything of the sort.
>
>>. 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?
>
> Well, sort of, yeah. Pointing out problems is one thing. Complaining is
> another. And telling other people what they should do to solve your
> problems
> is yet another thing entirely.
>
> But anyway, my main point was to suggest that people ask themselves what
> they've contributed to the open source community. Even if you're not a
> coder, you can write documentation, maintain a web site, etc.
>
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
>
>
> --
> No virus found in this incoming message.
> Checked by AVG Free Edition.
> Version: 7.5.476 / Virus Database: 269.9.9/870 - Release Date: 6/26/2007
> 10:07 AM
>
>
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
` John Heim
` Glenn Ervin
` Scott Berry [this message]
` 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='005601c7b84f$5bea08e0$c701a8c0@yellobow' \
--to=sberry@northlc.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).