1256
Comment: Initial page.
|
4479
|
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)>> 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 == | = pkg-ruby-extras team (libraries and applications) = |
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] |
* '''[[/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]] |
Line 24: | Line 31: |
== Get involved == | How you can help: * <<Icon(star_on.png)>> Subscribe to the lists, and start contributing to solving bugs. * <<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 36: |
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]]. == 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 [[/RubyInWheezy]] for details. == 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)>><<Icon(star_on.png)>> 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 == <<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. :) |
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.
Contents
pkg-ruby team (interpreters)
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)
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
Currrent status of the gem2deb transition
Information for upstream developers: /RubyExtras/UpstreamDevelopers, /RubyExtras/OnRubygems
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.