On 06/06/10 14:36, Lee Hambley wrote:
> Robin, Cap site is a wiki, feel free to contribute the above in some
> useful format… I approach this the same way Rafael does… if in doubt - ack.

Lee,

That's a cop out and not entirely helpful. I'm not a ruby coder so I
don't find it all that easy to dig through source code to find answers
simple questions that should be answered in basic documentation.

capistrano is a powerful tool, but with power comes complexity and
complex tools need documentation. capistrano documentation is sadly
lacking, as you acknowledge yourself:

"We know that documentation is something that really lets us down,
that's why there is a repository for a handbook below, please open an
issue on it if you would like something documented"

http://github.com/leehambley/capistrano-handbook (not updated since
April 26, 2009).

"If you prefer the wiki style of documentation, then please see our wiki"

http://wiki.capify.org (doesn't exist; no trace of it on archive.org).

How about spending some time to at least organise the website and
identify areas where documentation could be improved?

R.

-- 
* You received this message because you are subscribed to the Google Groups 
"Capistrano" group.
* To post to this group, send email to [email protected]
* To unsubscribe from this group, send email to 
[email protected] For more options, visit this group at 
http://groups.google.com/group/capistrano?hl=en

Reply via email to