The Debian/Ruby teams maintain the Ruby interpreters, libraries and applications. There are actually two different Ruby teams in Debian:

Both teams share some infrastructure, and have common members.

Most discussions happen on the debian-ruby mailing list. Discussions specific to pkg-ruby-extras also happen on the pkg-ruby-extras-maintainers list. You should be subscribed to both if you want to follow Ruby in Debian. We also use IRC (#debian-ruby on irc.debian.org) quite a lot.

pkg-ruby team (interpreters)

How you can help ({*} indicates difficulty: {*}=easy, {*}{*}{*}=hard):

For all of this, you might need to learn basics of Debian packaging. See this page and the packaging-tutorial package.

pkg-ruby-extras team (libraries and applications)

How you can help:

Mid- and Long-term tasks

To learn about the recent stuff that happened in Debian/Ruby world, see this blog post.

Keep our packages bug-free and up-to-date

{*} Start from the packages overview mentioned above.

Finish the transition to gem2deb

{*} We are currently transitioning from a cdbs-based packaging tool to gem2deb, a modern dh-based tool. See /Packaging for details, and the transition status at http://pkg-ruby-extras.alioth.debian.org/wheezy/ and http://pkg-ruby-extras.alioth.debian.org/wheezy/details.html. Pick up a package tnat needs to be transitioned, and work on it.

Provide backports

{*} Provide backports for the key Ruby packages (interpreter, rubygems) for both Debian and Ubuntu stable releases.

Deprecate Ruby1.8

{*}Since Wheezy, Ruby 1.9.3 has been the default Ruby interpreter in Debian. Upstream support for Ruby 1.8 is about to stop, but some packages still depend on ruby1.8 package. Help track down these packages, file bug reports and send patches.

Package other Ruby interpreters

{*}{*}{*} It would be nice to make progress towards having the same support for Rubinius and JRuby.

Generation of ri and rdoc documentation

{*}{*}{*} Currently we do not to generate the ri and rdoc documentation, as there are good online services providing it (like rdoc.info). We might change our mind later. :) Bonus points for solutions that do not require changing the existing packages.