Re: [linux-audio-dev] How non-programmers use documentation.
Le Lundi 27 Août 2001 20:59, vous avez écrit : 16. Non-programmers that I talked to have never sent a bug report or a feature request to a software company. The idea of sending one directly to a programmer or a technical writer was a completely foreign concept. errh errh in my case (I can't use effects in grecord, it core-dumps) I don't want people to say hey your machine is a mess oh oh you don't know how to install this ot that!. I'm kidding a little, but not too much. I believe the new filetree-standard under linux will help a lot: if I know my distro is compliant, if I know the prog I try to install is compliant, then I can say there's a bug or not. Elsewhere I'm in doubt. Shall I say I'm a bit scared applying the low-latency patches? I've tried but got some errors during compilation. So I gave up.
Re: [linux-audio-dev] How non-programmers use documentation.
Very good point. I could not put my finger on it, but you are right, what often stops you from sending bug reports is that you don't want to be taken for a fool :-). BR /Robert dany wrote: Le Lundi 27 Aot 2001 20:59, vous avez crit : 16. Non-programmers that I talked to have never sent a bug report or afeature request to a software company. The idea of sending one directlyto a programmer or a technical writer was a completely foreign concept. errh errh in my case (I can't use effects in grecord, it core-dumps) I don't want people to say "hey your machine is a mess" "oh oh you don't know how to install this ot that!". I'm kidding a little, but not too much.I believe the new filetree-standard under linux will help a lot: if I know my distro is compliant, if I know the prog I try to install is compliant, then I can say there's a bug or not. Elsewhere I'm in doubt. Shall I say I'm a bit scared applying the low-latency patches? I've tried but got some errors during compilation. So I gave up.
RE: [linux-audio-dev] How non-programmers use documentation.
-Original Message- From: Paul Sladen [mailto:[EMAIL PROTECTED]] On Tue, 28 Aug 2001, dany wrote: I believe the new filetree-standard under linux will help a lot: if I know my distro is compliant, if I know the prog I try to install is compliant, then I can say there's a bug or not. Elsewhere I'm in doubt. The other alternative is to standardise on Debian, and then just wait until the rest of the world catches up. that's basically the current situation:-) erik
Re: [linux-audio-dev] How non-programmers use documentation.
Hi, 12. Non-programmers don't want to see information about how a feature was implemented. In audio processing they will want if they are professionals. So many things can go wrong if DSP algorithms are incorrectly Definitly, to actually apply DSP you should know what you're doing. That isn't limited to DSP actually :) 16. Non-programmers that I talked to have never sent a bug report or a feature request to a software company. The idea of sending one directly to a programmer or a technical writer was a completely foreign concept. I consider this a bad attitude in open source land. Cheers, Alex -- Patch griefs with proverbs. -- William Shakespeare, Much Ado About Nothing
Re: [linux-audio-dev] How non-programmers use documentation.
On Mon, 27 Aug 2001, Alexander Ehlert wrote: 16. Non-programmers that I talked to have never sent a bug report or a feature request to a software company. The idea of sending one directly to a programmer or a technical writer was a completely foreign concept. I consider this a bad attitude in open source land. This troubled me also. If there's one behavior I wish I could change, it would be this. Perhaps we could make it a condition of usage... you may use this program free-of-charge but we'd like bug reports. Maybe we could make it easier to send bug reports by including a way to do it from the application itself. Just some ideas I had... === Kevin Conder, [EMAIL PROTECTED]
RE: [linux-audio-dev] How non-programmers use documentation.
most of the below seems quite reasonable, I just have few comments: -Original Message- From: Kevin Conder [mailto:[EMAIL PROTECTED]] ... 08. Non-programmers don't want detailed explanations, they want simple answers. then you can only do simple things... as simple as possible but not simpler (forgot who said that...) ... 16. Non-programmers that I talked to have never sent a bug report or a feature request to a software company. The idea of sending one directly to a programmer or a technical writer was a completely foreign concept. this is one area where non-programmers should change if they want good programs. communication is crucial, even more so in free software world. Lot of free programs provide fairly good support for bug reporting and public bug repositories where user can check whether the problem they encountered is already being worked... there are irc channels, newsgroups, mailing lists for various programs there are of incredible value to anybody (programmers and non-programmers) who want to use some program. The feedback is crucial for: - bugs being fixed - features being implemented - user's understanding of program functionality it's just a matter of foreign concept becoming a familiar one... erik
