On Jan 12, 2008, at 12:09 PM, Giles B. wrote:
Is there a project to keep Gems documentation up to date?
Yes, it’s called RubyGems. If you find the documentation lacking,
submit a patch to the tracker on the RubyGems project on Rubyforge.
RDoc patches are preferred.
I mailed you a docs patch and you never responded. I apologize that I
didn’t know about the tracker, but come on. I tried to give you a
patch before I asked this question. I did find the documentation
lacking and I did submit a patch.
It might still be in my inbox then, but maybe not. I’m not the only
person who works on RubyGems, so sending it to one of us is probably
going to get your patch lost. The tracker is in same place as most
other Ruby projects, so when I find a bug in something, that’s the
first place I look.
Furthermore, by sending a patch only to one person, you reduce the
ability for people to collaborate. Maybe somebody else found the same
issue as you, and was going to write a patch. If you don’t use the
tracker, everybody has to grope in the dark.
If I want to patch something in FreeBSD, I don’t send a patch to the
first FreeBSD developer’s email I come across, I find the tracker, see
if it’s been reported, see if it’s got a patch, and then do some
work. If I want to patch something in Linux, I don’t send an email to
Linus, I go through the appropriate process.