Differences between revisions 26 and 27
Revision 26 as of 2011-07-19 09:29:52
Size: 4680
Comment:
Revision 27 as of 2011-07-19 09:49:39
Size: 4661
Comment:
Deletions are marked like this. Additions are marked like this.
Line 3: Line 3:
The ""Debian/Ruby teams"" maintain the Ruby interpreters, libraries and applications. There are actually two different Ruby teams in Debian: The '''Debian/Ruby teams''' maintain the Ruby interpreters, libraries and applications. There are actually two different Ruby teams in Debian:
Line 26: Line 26:
 * '''Team Documentation''': [[/RubyExtras]]. In particular, see the [[/RubyExtras/JoiningTheTeam|Joining the Team]] page. Note that ome of the docs are outdated, especially after the switch from Svn to Git.  * '''Team Documentation and current packaging practices''': [[/Packaging]]. Note that ome of the docs might be outdated. Please improve them!
Line 28: Line 28:
 * [[http://git.debian.org/?p=pkg-ruby-extras/pkg-ruby-extras.git;a=summary|Git repository (to be used with mr, see team documentation)]]
Line 29: Line 30:
 * [[http://git.debian.org/?p=pkg-ruby-extras/pkg-ruby-extras.git;a=summary|Git repository (to be used with mr, see team documentation)]]
Line 31: Line 31:
 * [[http://pet.43-1.org/pkg-ruby-extras/pet.cgi|PET overview]]
* The [[/RubyInWheezy]] page documents the current packaging practices.
 * [[http://pet.43-1.org/pkg-ruby-extras/pet.cgi|PET overview for packages in Git]]
 * [[http://pk
g-ruby-extras.alioth.debian.org/cgi-bin/pet.cgi|PET overview for packages in SVN]]

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.

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

pkg-ruby (interpreters)

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

How you can help:

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

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

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

pkg-ruby-extras (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

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