documentation & dear love
Wed Jun 27 09:19:00 GMT 2001
>However, I can see that the documentation could be misconstrued.
>Cygwin's documentation is not perfect. I don't know of any project
>which has perfect documentation. I would dearly love to have someone
>actively working on it.
I'll step up and volunteer to work on documentation. I've been building
up to working on coding (getting cygwin and the tools to compile for a
start) since I'm a hacker first, but I am aware that too many open
source projects are in dire need of documentatation and I'm getting
sufficient number of technical challenges at work at this point.
Unless you prefer to have more people writing code, of course.
Christopher (or anyone), can you give me a ballpark idea of what needs
to be done and where I might start? I've spent a fair amount of time
under the "Contributing" link, but it seems mostly to be about writing
code. Should I look at updating the user's guide? The FAQ? I've been
using cygwin since about b17 and have been on and off the list, so I
think I'm fairly qualified to help with the docs. And I'll certainly
consult the list or whomever I should consult about suggested updates
Jason Dufair - email@example.com
"The oldest one captains the bleak white ship of bone with palsied hands
The one of middle years wears a hope like chains
The youngest one cries tears of scarlet, and adjusts her latest smile"
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
More information about the Cygwin