Yukihiro Matsumoto wrote:
Hi,
In message "Re: can members of this list commit docs? (was Re: Addition to open3.rb
...)"
on Mon, 24 Jan 2005 09:46:51 -0500, Sam Roberts <sroberts@xxxxxxxxxxxx>
writes:
...
| how do you find the maintainer of a library, so you can send docs to them
| if this isn't the right place?
Many files contain auther information. Maintainers should
be reading ruby-core, so use that list to find and notice
the maintainers if you don't find them.
Matz, how do you feel about using the rubyforge bug tracker [0] for
posting documentations issues and submitting patches? I think it is a
good way to maintain a record of what has been reported and for those
with the authority and inclination to get the patches into the source.
I've had a few people contact me and ask how they get documentation
corrections through the pipeline, and I've been telling them to post
either here or on ruby-core, but using the bug tracker seems a lot
cleaner. (If nothing else, it means that one need not subscribe to a
list to report a documentation error or submit a fix.)
There is no category for documentation per se, so perhaps there should
some sort of prefix in the summary field. Or not, if the summary simply
declares that the report or patch is for documentation
James
[0] http://rubyforge.org/tracker/?atid=1698&group_id=426&func=browse
|
