The documentation is not very good.
It's a wee bit difficult for others to write documentation when they can't figure
the software out, because the developers never wrote any good ones. Eight months of
openser and I'm still trying to work out how all this branch stuff works. Don't
have a clue, and there's no books on this stuff either. If you ask in the list you get
half answers and riddles.
-----Original Message-----
From: Greg Fausak [mailto:lgfausak@gmail.com]
Sent: Monday, June 05, 2006 9:23 AM
To: Douglas Garstang
Cc: Juha Heinanen; users(a)openser.org
Subject: Re: [Users] Avpops tutorial
Douglas,
The programmer did write documentation! That's what we
currently have. Often it is a good idea for a non-programmer
(ie. user)
to write the documentation from their point of view.
Anyway, this is open software and the more people that help
develop it (and it's documentation) the better. If you don't write
it I'm sure somebody will someday :-)
-g
On 6/5/06, Douglas Garstang <dgarstang(a)oneeighty.com> wrote:
> -----Original Message-----
> From: Juha Heinanen [mailto:jh@tutpro.com]
> Sent: Sunday, June 04, 2006 11:01 AM
> To: Douglas Garstang
> Cc: Bogdan-Andrei Iancu; Sam Lee; users(a)openser.org
> Subject: RE: [Users] Avpops tutorial
>
>
> Douglas Garstang writes:
>
> > I'm not one of the developers.
>
> you don't need to be. in fact, it would give developers'
more time
to
develop,
i.e., write code.
How can I write the documentation when I don't understand
how the software
works?
Are you suggesting I learn C and look at the
code?
I'm of the opinion that developers should write
documentation. If other
people try to do it, they make bad
assumptions based on what they THINK they know. They then
write bad or wrong documentation which others read, and in
turn also write bad documentation. It's not a good model.
Doug
_______________________________________________
Users mailing list
Users(a)openser.org
http://openser.org/cgi-bin/mailman/listinfo/users
--
Greg Fausak
greg(a)thursday.com