Mat Schaffer wrote:
Cool. But what about building this into more than just guidelines?
I'd really like to see something akin to "getting started as a ruby
documenter" unless you see some reason against it. Start with checking
out ruby, then links to setup info for stdlib-doc with installation
pointers. Finally list the submission guidelines.
Yes. That would be good.
Basically, I'd like to see the barrier to entry lowered as much as
possible here. Granted, that may cause people to post some bad patches
here, but I think those will be the exception, and we don't have to
take every patch submitted. On the plus side, I could see it
encouraging some people to come in and fix poorly written documentation
even if they don't know too much about reading and interpreting code.
That's a good goal. I'd like, though, to start with basics and get
essential information up on ruby-doc first, and then continue to refine
and extend the guidelines.
Publish early and often, so to speak.
I'd be happy to add some of that stuff if you give me access. The
email address I use for writely is schapht@xxxxxxxxxxxx
Done.
Thanks!
-Mat
James
|
