Re: Software speech opinions

["Albert E. Sten-Clanton" <albert.e.sten_clanton@verizon.net>]

> >.  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.
> 

I know there are good and bad ways of "pointing out problems," which is why I mentioned treating people right when you do it.  I hope I generally do.  

As for "telling other people what they should do to solve your problems," that's about what I'd expect of any constructive user of any product to do if he or she didn't create the product--for that matter, whether it's "free" or not.  To me, the question is not whether you should do it, but how.

> 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.
> 
This is certainly a fair point.  I'd add only that you can't be expected to contribute in those ways until you know what you're doing.  I've learned the hard way that bad documentation sometimes is worse than none at all, for example.  In any event, my impression is that those who made suggestions or complaints on the relevant topics here are already givers as well as takers.

Somebody else suggested giving money to the free software movement.  That also seems a good idea, though I don't know to whom I'd donate for the purpose of, say, getting Speakup or similar non-visual access into the vanilla kernel as a standard feature (assuming it can be done).

Al