Re: Call for help: documentation

I'll contribute for sure, have gotten use to exploring the source to
see how things work, and how to get things done... I'm definitely not
one for coordinating the doc project, I just have too much on my
plate...

Best

On Nov 14, 2007 11:27 PM, Jamis Buck 
<jamis-uHoyYlH2B+GakBO8gow8eQ@xxxxxxxxxxxxxxxx> wrote:
> Capistrano's documentation sucks.
>
> I fully acknowledge that. And I assume all the blame for it, too. I
> want to do something about it, but I've been far, far (far!) too
> swamped for the last six months to do more than acknowledge the need.
>
> So, I'm pleading for your help. Here's what I'd like to happen:
>
> 1. I'd like one (maybe two) people to step forward, to volunteer to
> coordinate the documentation effort. This person would ideally be
> responsible for identifying what needs to be documented,
> standardizing on a format for documentation, etc. They would work
> with me to make sure it fits with my vision for Capistrano, but
> mostly they would have a free reign to do what needs to be done.
>
> 2. I'd like as many people as possible to volunteer to submit
> documentation. This would happen after the coordinator identified
> what needs to be documented. People would then sign up to take on one
> of the areas pending documentation. If no action occurs on it within
> a month or so, that task would automatically become available again
> for someone else to sign up for.
>
> The documentation thus generated will be hosted at capify.org.
>
> Thoughts? Volunteers? If you'd like to coordinate the documentation
> effort, please email me directly, off-list. We'll see how many
> volunteer, and I'll pick the "winner". :)
>
> - Jamis
>



-- 

Kenneth Kalmer
kenneth.kalmer-Re5JQEeQqe8AvxtiuMwx3w@xxxxxxxxxxxxxxxx

Folding@home stats
http://fah-web.stanford.edu/cgi-bin/main.py?qtype=userpage&username=kenneth%2Ekalmer