# Where to report rubygems bugs

**URL:** <https://www.ruby-forum.com/t/where-to-report-rubygems-bugs/161661>\
**Category:** Ruby\
**Created:** [February 28, 2009, 4:55pm UTC](https://www.ruby-forum.com/t/where-to-report-rubygems-bugs/161661 "2009-02-28T16:55:36Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![rogerdpack](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/r/45deac/32.png) [@rogerdpack](https://www.ruby-forum.com/u/rogerdpack)\
**Post date:** [February 28, 2009, 4:55pm UTC](https://www.ruby-forum.com/t/where-to-report-rubygems-bugs/161661/1 "2009-02-28T16:55:36Z")

</div>

I’ve traditionally reported rubygems bugs to  
[http://rubyforge.org/tracker/?atid=575&group\_id=126&func=browse](http://rubyforge.org/tracker/?atid=575&group_id=126&func=browse)  
however [redmine.ruby-lang.org](http://redmine.ruby-lang.org) is now an option [and I sometimes feel  
like I"m submitting to deaf ears at the rubyforge one].  
Thoughts?  
-=r

---

<div class="post-metadata">

**Author:** ![rogerdpack](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/r/45deac/32.png) [@rogerdpack](https://www.ruby-forum.com/u/rogerdpack)\
**Post date:** [March 1, 2009, 10:53pm UTC](https://www.ruby-forum.com/t/where-to-report-rubygems-bugs/161661/2 "2009-03-01T22:53:25Z")

</div>

On Feb 28, 2009, at 07:54, Roger P. wrote:

> I’ve traditionally reported rubygems bugs to  
> [http://rubyforge.org/tracker/?atid=575&group\_id=126&func=browse](http://rubyforge.org/tracker/?atid=575&group_id=126&func=browse)

This is the correct place.

> however [redmine.ruby-lang.org](http://redmine.ruby-lang.org) is now an option

It’s a great option if you want me to ignore your bug.

> [and I sometimes feel like I"m submitting to deaf ears at the  
> rubyforge one].
> 
> Thoughts?

Maintaining RubyGems is a lot of work I don’t get paid for, so I  
intermix RubyGems work with other things I find more fun. I’ve been  
working on RDoc lately and will probably start up again on RubyGems in  
the next month or so.

If you want your bug fixed faster, make a bug report on RubyForge then  
hop on the mailing list [1] and propose a solution. Even better would  
be to submit a patch.

When I’m preparing to release RubyGems I look on RubyForge at the  
patches queue first followed by bugs then feature requests. Until I’m  
ready, though, I don’t read my bugmail as it just takes too much time.

1: [http://rubyforge.org/mailman/listinfo/rubygems-developers](http://rubyforge.org/mailman/listinfo/rubygems-developers)

---

<div class="post-metadata">

**Author:** ![rogerdpack](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/r/45deac/32.png) [@rogerdpack](https://www.ruby-forum.com/u/rogerdpack)\
**Post date:** [March 2, 2009, 1:45pm UTC](https://www.ruby-forum.com/t/where-to-report-rubygems-bugs/161661/3 "2009-03-02T13:45:11Z")

</div>

> Maintaining RubyGems is a lot of work I don’t get paid for, so I  
> intermix RubyGems work with other things I find more fun. I’ve been  
> working on RDoc lately and will probably start up again on RubyGems in  
> the next month or so.
> 
> If you want your bug fixed faster, make a bug report on RubyForge then  
> hop on the mailing list [1] and propose a solution. Even better would  
> be to submit a patch.
> 
> When I’m preparing to release RubyGems I look on RubyForge at the  
> patches queue first followed by bugs then feature requests. Until I’m  
> ready, though, I don’t read my bugmail as it just takes too much time.
> 
> 1: [http://rubyforge.org/mailman/listinfo/rubygems-developers](http://rubyforge.org/mailman/listinfo/rubygems-developers)

Thanks for your reply and the info. I’ll try to submit patches more  
often and feature requests less often 🙂  
-=r