How to use espeakup, revisited...

[John G. Heim]

----- Original Message ----- 
From: "Samuel Thibault" <samuel.thibault at ens-lyon.org>
To: "Speakup is a screen review system for Linux." <speakup at braille.uwo.ca>
People are not supposed to find useful information *here*, they're
supposed to find useful information in the *Notice*, which is
spkguide.txt and the manual pages, not this list (as that would mean
that users would have to either browse the archive (tedious), or ask
a question, wait, get an answer, ask another question, wait again,
etc.). We clearly said that we welcome contributions to these (I
personnally have absolutely no time atm to work on it, but can gladly
commit).
Obviously, no one with any sense would dispute the fact that the most 
efficient way to figure out how to use speakup is to read the documentation. 
But I do have a suggestion that I think would save a lot of headaches for us 
users. I think that the development team should try to use this list as a 
way to notify users of changes.

For example, I don't think any notice was posted to this list about the 
switch from cvs to git. I used to use the shell script that came with 
speakup to download updates. All of a sudden it stopped wworking. I read 
this list almost every day and I never saw that coming.

Obviously, I don't mean this as a criticism. I think you guys do fantastic 
work. I'm just saying that you could probably help a lot of people to avoid 
a lot of headaches if you posted messages here when such changes occured. 
And this stuff happens all the time. For example, there was the recent 
discussion about creating a file for a flag to indicate whether the synth 
was active or not. How are we going to know when that gets done? I guess I 
can keep browsing the documentation but wouldn't it make sense just to post 
a notification of that kind of thing to this list?