I've been writing Open Source documentation for ... well, a long time. We'll say fifteen years, for the sake of not having to go actually to remember too much of College, shall we? In my current life I write both formal online docs (Apache, PHP) and dead tree user manual kinds of docs (O'Reilly, Sams, APress, NoStarch).
I was pointed to this site, and was immediately enthralled. As I mentioned to a colleague this week, if I could get paid to just write user docs, full time, I'd leap at the chance. But, so far, I haven't had that opportunity, and so I write code. My passion, however, is explaining complicated things to people and seeing the light of understanding in their eyes.
But, as I started to look through the guide itself, I was disappointed that so little of it was actually written. Disappointed, but also a little excited, because that means that I can write it, right?
So the question is, where do I sign up, and is it ok to just start writing? I am very opinionated on the topic of writing end-user documentation, and am more than happy to share those views, but I don't want to stomp all over the process.
Truth be told, I already *did* start writing, but then I thought it might be polite to knock on the door and see if anyone else is at home. 'Cause if not, I might move in and start rearranging the furniture.
we hear you
I think you should continue writing and in a fashion similar to a documentation sprint. Others will join in, a few elements/changes will be discussed, and the like, but overall action is needed.
go for it
Activity on this site has slowed considerably since the initial burst of enthusiasm back in June. I, for one, heartily welcome your fresh enthusiasm. By all means, dig in. And there's nothing like a few strong opinions to get the conversation jump-started.
And, BTW, there are plenty of jobs writing user docs, but the vast majority of them are at proprietary software companies. They also might not pay what you're accustomed to getting as a programmer.