Differences between revisions 1 and 35 (spanning 34 versions)
Revision 1 as of 2007-05-26 20:18:50
Size: 1256
Comment: Initial page.
Revision 35 as of 2012-01-02 18:00:53
Size: 5299
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
= The Debian/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
Line 3: Line 5:
== Task description == Both teams share some infrastructure, and have common members.
Line 5: Line 7:
The Debian/Ruby Extras team maintains libraries and applications written in and for the Ruby language. The Ruby interpreter itself is not a responsibility of the team, though we strive to maximize our cooperation with the Ruby maintainers. Most discussions happen on the [[http://lists.debian.org/debian-ruby/| debian-ruby mailing list]]. Discussions specific to pkg-ruby-extras also happen on the [[http://lists.alioth.debian.org/mailman/listinfo/pkg-ruby-extras-maintainers | 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.
Line 7: Line 10:
== Infrastructure == <<TableOfContents>>
Line 9: Line 12:
 * '''Website''': http://pkg-ruby-extras.alioth.debian.org/
 * '''Alioth Project''': http://alioth.debian.org/projects/pkg-ruby-extras
 * '''Subversion repository''': svn://svn.debian.org/pkg-ruby-extras/ (svn client), http://svn.debian.org/wsvn/pkg-ruby-extras/ (browser)
= pkg-ruby team (interpreters) =
Line 13: Line 14:
== Interacting with the team ==  * Packages are maintained in git using collab-maint. See PTS pages for [[http://packages.qa.debian.org/r/ruby1.8.html|ruby1.8]] and [[http://packages.qa.debian.org/r/ruby1.9.1.html|ruby1.9.1]].
Line 15: Line 16:
 * '''Email''': [[MailTo(pkg-ruby-extras-maintainers AT lists DOT alioth DOT debian DOT org)]]
 * '''IRC''': most of the members of the time reside on #debian-ruby on irc.debian.org (OFTC)
'''How you can help''' (<<Icon(star_on.png)>> indicates difficulty: <<Icon(star_on.png)>>=easy, <<Icon(star_on.png)>><<Icon(star_on.png)>><<Icon(star_on.png)>>=hard):
 * <<Icon(star_on.png)>> Go through bugs, see if you can reproduce them and provide more information. Report them upstream when needed.
 * <<Icon(star_on.png)>> 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 [[http://www.debian.org/doc/developers-reference/resources.html#pts-commands|developers reference]] for details).
 * <<Icon(star_on.png)>><<Icon(star_on.png)>> Checkout the Git repositories, see if you can provide a patch for some issues.
Line 18: Line 21:
== Useful links == For all of this, you might need to learn basics of Debian packaging. See [[http://www.debian.org/devel/|this page]] and the packaging-tutorial package.
Line 20: Line 23:
 * [http://bugs.debian.org/cgi-bin/pkgreport.cgi?maint=pkg-ruby-extras-maintainers%40lists.alioth.debian.org BTS page]
 * [http://qa.debian.org/developer.php?login=pkg-ruby-extras-maintainers%40lists.alioth.debian.org&comaint=yes Packages overview]
 * [http://pkg-ruby-extras.alioth.debian.org/subversion.html Team's Subversion Guide]
= pkg-ruby-extras team (libraries and applications) =
Line 24: Line 25:
== Get involved ==  * '''[[/Packaging|Team Documentation and current packaging practices]]'''. Note that some of the docs might be outdated. Please improve them!
 * Alioth Project: http://alioth.debian.org/projects/pkg-ruby-extras
 * [[http://qa.debian.org/developer.php?login=pkg-ruby-extras-maintainers%40lists.alioth.debian.org&comaint=yes|Packages overview]]
 * [[http://pet.43-1.org/pkg-ruby-extras/pet.cgi|PET overview for packages in Git]]
 * [[http://pkg-ruby-extras.alioth.debian.org/cgi-bin/pet.cgi|PET overview for packages in SVN]]
 * [[http://pkg-ruby-extras.alioth.debian.org/wheezy/|Currrent status]] of the gem2deb transition
 * Information for upstream developers: [[/RubyExtras/UpstreamDevelopers]], [[/RubyExtras/OnRubygems]]
 * [[http://lists.debian.org/debian-ruby/|The team mailing lists archives]]
How you can help:
 * <<Icon(star_on.png)>> Subscribe to the lists, and start contributing to discussions.
 * <<Icon(star_on.png)>> Improve documentation (that page, the [[/Ruby]] page, etc..
 * <<Icon(star_on.png)>> Use the Packages overview to go through all existing bugs, and see if you can help with solving some of them.
 * <<Icon(star_on.png)>><<Icon(star_on.png)>> Checkout the Git repository, and see if you can improve the existing packages. There are many things that can be improved!
Line 26: Line 39:
Just contact us via email or on IRC. = Mid- and Long-term tasks =
To learn about the recent stuff that happened in Debian/Ruby world, see [[http://www.lucas-nussbaum.net/blog/?p=681|this blog post]].

== Keep our packages bug-free and up-to-date ==
<<Icon(star_on.png)>>
Start from the packages overview mentioned above.

== Finish the transition to gem2deb ==
<<Icon(star_on.png)>>
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 ==
<<Icon(star_on.png)>>
Provide backports for the key Ruby packages (interpreter, rubygems) for both Debian and Ubuntu stable releases.

== Switch to 1.9 as default ==
<<Icon(star_on.png)>><<Icon(star_on.png)>>
Since we use alternatives, it is quite easy to switch to 1.9 as default. Switch to 1.9 as default using update-alternatives, and then report issues.

== Package other Ruby interpreters ==
<<Icon(star_on.png)>><<Icon(star_on.png)>><<Icon(star_on.png)>>
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 [[http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=591817|#591817]])

== Generation of ri and rdoc documentation ==
<<Icon(star_on.png)>><<Icon(star_on.png)>><<Icon(star_on.png)>>
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.

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.

Switch to 1.9 as default

{*}{*} Since we use alternatives, it is quite easy to switch to 1.9 as default. Switch to 1.9 as default using update-alternatives, and then report issues.

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. :) Bonus points for solutions that do not require changing the existing packages.