Jason Tackaberry wrote:
> As a developer, or even as a systems engineer (which I am during the
> day), I'm happy to answer questions and explain how things work in
> detail. However I'm at my least happiest when writing documentation. :)
Full ACK
> Mind you, I also recognize that it's often a chicken-and-egg problem.
> You can't have users unless _somebody_ knows how it works, and that
> usually starts with the developers. But once you build that momentum,
> there are some very capable writers out there. (Unfortunately there are
> some very bad ones too. So it goes.)
The basic idea is: if you want to use something here with bad doc, tell
us. Hans wanted to use beacon and I wrote some basic doc for it. That is
how it works. But if someone finds out something by reading the inline
doc or the test cases, it would be nice if he/she writes a small doc and
sends a patch.
Dischi
--
Murphy's Laws:
(1) If anything can go wrong, it will.
(2) Nothing is as easy as it looks.
(3) Everything takes longer than you think it will.
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Freevo-users mailing list
Freevo-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freevo-users
