Le Mardi 28 Août 2001 13:54, vous avez écrit :
> 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 d
On Tuesday 28 August 2001 10:45 am, you wrote:
> 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
> > >
> -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 s
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
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 Août 2001 20:59, vous avez écrit :
>16. Non-programmers that I talked to
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 De
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 don't have the original message, but all the points listed are good and
apply to programmers too, not just non-programmers. I like software that
is easy to use and just works. If it takes several hours to get a linux
program working, it is cheaper to just buy the Windows equivalent, which
almo
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 poss
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
On Mon, 27 Aug 2001, Juhana Sadeharju wrote:
> >From:Kevin Conder <[EMAIL PROTECTED]>
> >
> >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 al
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.
T
>From: Kevin Conder <[EMAIL PROTECTED]>
>
>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
implemented. One needs to look at manuals
On Sat, 25 Aug 2001 13:46, Kevin Conder wrote:
> I'm not trying to write a doctoral thesis so my process wasn't
> scientific. My information is based on informal conversations with friends
> and co-workers. Here is what I learned about how non-programmers use
> documentation:
Wow, that was
I've tried to give back to the Linux community by helping
with documentation. I've helped with some FAQs, HOWTOs, and am working on
a large reference manual. Lately I started wondering how non-programmers
actually use documentation so I asked a few.
I'm not trying to write a doct
15 matches
Mail list logo
