= !!! Stale outdated version !!! = If you're here due to following the first result from searching for Ruby, '''what you're looking is at:''' https://wiki.debian.org/Ruby or https://wiki.debian.org/Teams/Ruby. <> = General Information = The '''Debian Ruby team''' maintains Ruby software in Debian. This includes the interpreters, libraries and applications. * Libraries and applications are maintained inside the [[https://alioth.debian.org/projects/pkg-ruby-extras/|pkg-ruby-extras project]]. * The interpreter packages are maintained inside of the [[https://alioth.debian.org/projects/collab-maint/|collab-maint project]]. The complete information is spread across this page and the following pages: <> == Packages information == * [[http://qa.debian.org/developer.php?login=pkg-ruby-extras-maintainers%40lists.alioth.debian.org&comaint=yes|Packages overview]] * [[http://pet.debian.net/pkg-ruby-extras/pet.cgi|PET overview for packages in Git]] * [[http://udd.debian.org/dmd.cgi?email1=pkg-ruby-extras-maintainers%40lists.alioth.debian.org|Debian Maintainer Dashboard for the team]] * [[http://anonscm.debian.org/gitweb/?pf=pkg-ruby-extras|list of all Git repositories owned by the pkg-ruby-extras team]] = Joining Debian Ruby Extras Maintainers = Debian Ruby team does its activities under the alioth group which contains repositories where the team maintained packages are version controlled, mailing lists where discussions take place etc. == Communication == === Mailing List === 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 debian-ruby@lists.debian.org === IRC === Debian Ruby team maintains the IRC channel [[http://webchat.oftc.net/?channels=debian-ruby|#debian-ruby]] in the OFTC server where team members hang around. This channel acts as a quick way to communicate with the team and is used heavily during sprints, online meetings etc. == Alioth == The team's alioth group can be found here - https://alioth.debian.org/projects/pkg-ruby-extras/ . To maintain the packages under Debian Ruby team, it is preferred to join the team and version control the packages under the git repos available. Steps for joining alioth group are 1. Create an account in alioth - https://alioth.debian.org/account/register.php 2. Upload your SSH key to alioth - https://alioth.debian.org/account/editsshkeys.php i. To know about creating an SSH key, visit https://wiki.debian.org/Alioth/SSH 3. Request to join the Debian Ruby team - https://alioth.debian.org/project/request.php?group_id=30665 4. Wait for a group admin to add you to the group. 5. To speed up the procedure, send an email to the mailing list (debian-ruby@lists.debian.org) stating your request to join the alioth group and preferably the package you intend to maintain under the team. = Contributing to Debian Ruby Extras Maintainers Team = If you are a Debian enthusiast with basic Ruby knowledge, you can help Debian Ruby Extras 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 [[http://bugs.debian.org|Debian Bug Tracker]] or [[https://wiki.debian.org/reportbug|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. == Bug triaging == You can also help to triage bugs, by choosing bugs from https://bugs.debian.org/pkg-ruby-extras-maintainers@lists.alioth.debian.org 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 1. reproduce them on your local machine / clean chroot as needed 2. confirm bug's existence and validity 3. Tag bugs appropriately 4. Close invalid ones == Fixing bugs == 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. == Documentation == 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 [[https://wiki.debian.org/FrontPage?action=newaccount|creating an account]] in Debian Wiki and cleaning up the pages to contain only valid, prompt and updated information == Packaging == '''Workflow about packaging new Ruby based software for Debian can be found [[/Packaging|here]].''' == Maintaining == 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. = Miscellaneous Documentation = * [[/InterpreterTransitions | Interpreter Transition Mechanism]] - Steps to follow on updating the version of Ruby interpreters in Debian archives. * [[http://pkg-ruby-extras.alioth.debian.org/wheezy/|Current status]] of the gem2deb transition * '''[[/Packaging|Team Documentation and current packaging practices]]'''. * Information for upstream developers: [[/RubyExtras/UpstreamDevelopers]], [[/RubyExtras/OnRubygems]]