The Debian Ruby team maintains Ruby software in Debian. This includes the interpreters, libraries and applications. All packages are now hosted in the ruby-team group on Salsa.
Joining the Debian Ruby team
The general discussion mailing list of Debian Ruby team can be found at https://lists.debian.org/debian-ruby/ . The mailing list is open for anybody to join and post and acts as the central point of access for communication with the Team. To post to the mailing list, send a mail to email@example.com
- #debian-ruby on irc.debian.org (OFTC) where team members hang around.
#debian-ruby-changes on irc.debian.org (OFTC) for KGB notifications.
This is the server hosting all git repositories maintained by the ruby-team. The repositories are all public. You can send merge requests for one-shot fixes. You can also request membership to the group ruby-team and wait for an admin to add you to the group. To speed up the procedure, send an email to the mailing list (firstname.lastname@example.org) stating your request to join the alioth group and preferably the package you intend to maintain under the team.
Information about the transition from Alioth to Salsa can be found here.
Contributing to the Debian Ruby team
If you are a Debian enthusiast with basic Ruby knowledge, you can help Debian Ruby team's activities. There are different ways to contribute to Debian Ruby team, which includes (and is not limited to)
Identifying and reporting bugs
If you are a user of the packages maintained by Debian Ruby team, you can help us by reporting the bugs you find in the packages using the Debian Bug Tracker or reportbug tool. You can also add wishlist bugs about changes/features you would like to be added to the package so as to make it better to use.
You can also help to triage bugs, by choosing bugs from https://email@example.com or https://udd.debian.org/dmd/?email1=pkg-ruby-extras-maintainers%40lists.alioth.debian.org&email2=&email3=&packages=&ignpackages=&format=html#todo, and try to
- reproduce them on your local machine / clean chroot as needed
- confirm bug's existence and validity
- Tag bugs appropriately
- Close invalid ones
If you have knowledge in Ruby, you can fix bugs that have been filed against the team maintained packages by providing patches and helpful information. Those like FTBFS bugs are often caused by test failures in packages and should be fixed to ensure reproducibility of the packages.
Chances of bugs are more during transition of the Ruby version and any help in identifying, tagging and fixing them are much appreciated.
This wiki, and it's subpages are intended to collect all the information regarding the structure, activities and conventions of Debian Ruby team, and needs extensive care and help to be maintained in good, up-to-date state. Start by creating an account in Debian Wiki and cleaning up the pages to contain only valid, prompt and updated information
Workflow about packaging new Ruby based software for Debian can be found here.
Maintainance of a package involves the tasks like updating a package to the latest version, keeping the package to be in accordance with the current Debian policies and standards etc. To know about updating a package and uploading it, visit here.
Libraries and applications were previously maintained inside the pkg-ruby-extras project on Alioth, while the interpreter packages were maintained inside of the collab-maint project. These locations are now deprecated.
Interpreter Transition Mechanism - Steps to follow on updating the version of Ruby interpreters in Debian archives.
Sub pages of this documentation can be found below: