Differences between revisions 39 and 40
Revision 39 as of 2013-06-20 22:10:55
Size: 5720
Editor: ?CédricBoutillier
Comment: update some info
Revision 40 as of 2013-06-22 07:07:50
Size: 5844
Editor: ?CédricBoutillier
Comment: add list of git repos
Deletions are marked like this. Additions are marked like this.
Line 35: Line 35:
   * [[http://anonscm.debian.org/gitweb/?pf=pkg-ruby-extras|list of all Git repositories owned by the pkg-ruby-extras team]]

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

  • the pkg-ruby team, which maintains the interpreter
  • the pkg-ruby-extras team, which maintains libraries and applications

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)

  • Packages are maintained in git using collab-maint. See PTS pages for ruby1.8 and ruby1.9.1.

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

  • {*} Go through bugs, see if you can reproduce them and provide more information. Report them upstream when needed.

  • {*} Subscribe to the pkg-ruby packages (ruby1.8, ruby1.9.1, ruby-defaults) on the Packages Tracking System, and then contribute to the bug mail you get. (It is a good idea to also subscribe to bugmail from Ubuntu, see developers reference for details).

  • {*}{*} Checkout the Git repositories, see if you can provide a patch for some issues.

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:

  • {*} Subscribe to the lists, and start contributing to discussions.

  • {*} Improve documentation (that page, the ?/Ruby page, etc..

  • {*} Use the Packages overview to go through all existing bugs, and see if you can help with solving some of them.

  • {*}{*} Checkout the Git repository, and see if you can improve the existing packages. There are many things that can be improved!

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.

  • JRuby is now in main (see PTS page) but is outdated. Contact Java team for possible collaboration?

  • For Rubinius, there's an ITP (see #591817)

  • mruby has been uploaded in experimental (link to PTS)

  • Work on Ruby2.0 is ongoing (see #697703).

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.