[Mldonkey-users] documenting mldonkey

[Brett Dikeman]

My comments about CIDR-range based server blacklisting reminded me of 
something.

  Months ago I emailed one of the developers asking if they wanted 
assistance with writing documentation for mldonkey- I said I'd do it 
provided I got a promise from developers to help with questions as I 
worked my way through mldonkey's options and such(ie what I couldn't 
figure out from the mailing list, playing with it, and if need be, 
reading source code), and a promise that when something that affected 
the user was changed(ie, behavior, UI element, feature/command 
change, etc), someone would let me know(if I couldn't learn about it 
from simply lurking on a dev list) and provide a little info so it 
could be added into said documentation.

That was almost exactly two months ago.  I never got a reply- not a word.

I'm one of those folks who believes in trying to help fix something 
rather than standing around and complaining about it, which is why I 
extended the offer to help....instead of just bitching "there aren't 
any docs!"

If there is something in the works, I'll offer my help if it can be 
used and slip into the background on the issue, but if there isn't, 
then I would like to start something.

It can be a lot easier with help from developers(and it is, IMHO, in 
their interests to have good docs, since the better the docs, the 
less time spent answering the same question every other day), but if 
push comes to shove, the user community can pool their knowledge and 
assemble documentation on their own.

At the time, I made a brief start by going through the list archives 
message by message looking for tidbits that could be documented; my 
theory is "if it's been asked, it needs to be documented".  Given the 
volume, help would be greatly appreciated.  It is at least a starting 
point, yes?

If you have an interest in helping, please email me directly.  I'll 
see what reaction is like(both from developers and users) and go from 
there...

Brett
--