Differences between revisions 29 and 30
Revision 29 as of 2011-07-19 10:10:49
Size: 4780
Comment:
Revision 30 as of 2011-07-19 10:13:16
Size: 4479
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:

Line 26: Line 24:
 * '''Alioth Project''': http://alioth.debian.org/projects/pkg-ruby-extras
 * [[http://git.debian.org/?p=pkg-ruby-extras/pkg-ruby-extras.git;a=summary|Git repository (to be used with mr, see team documentation)]]
 * '''Subversion repository''' (DEPRECATED): svn://svn.debian.org/pkg-ruby-extras/ (svn client), http://svn.debian.org/wsvn/pkg-ruby-extras/ (browser)
 * Alioth Project: http://alioth.debian.org/projects/pkg-ruby-extras

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:

  • {*} 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.

pkg-ruby-extras team (libraries and applications)

How you can help:

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

  • {*} 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.

Finish the transition to gem2deb

{*} We are currently transitioning from a cdbs-based packaging tool to gem2deb, a modern dh-based tool. See /RubyInWheezy for details.

Provide backports

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

Switch to 1.9 as default

{*}{*}{*} Since we use alternatives, it is quite easy to switch to 1.9 as default. However, 1.9 doesn't sound like a reasonable target now, even if it is likely to become one during the wheezy cycle.

Package other Ruby interpreters

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

  • For JRuby, it is in non-free (see http://packages.qa.debian.org/j/jruby.html) because of some dependencies. We can't depend on it if it stays non-free because it would make all ruby software part of contrib.

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

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. :)