Ruby Release Goals for Debian Jessie

This page summarizes some ideas about possible goals for Ruby in Jessie:

Key:

Ruby Interpreter specifics

Ruby 1.8, 1.9, 2.0 are gone \o/

Status

Item

Who

Comments

TODO

Multi-Arch for arch:any/arch:all mixed dependency chains

?

pkg-perl decided on something, unclear what's being done for Python

TODO

Check upstream support for 2.1 and if they do releases or we need to git pull stuff

?

DONE

Don't explode during the wheezy->jessie upgrade

terceiro

TODO

Decide on rubygems-integration install-by-default to $HOME

DISCUSS; terceiro: writes mail

would for the most part change how bundler "works" (makes us different from other distros, OSes)

?

Feedback on ruby-standalone

DISCUSS

DISCUSS

Backport 2.1 to wheezy

?

is it still worth it -- decide for the future how it could be done for jessie?

DISCUSS

ruby-head versions for stable

?

Other interpreters

Status

Item

Who

Comments

TODO

Rubinius

terceiro (WILL APPRECIATE HELP) ?DavidSuárez

WIP in git, probably already outdated wrt upstream. Updated to last git commit, links against debian packaged libs, builds (atm) with 1.9 only support, what to do with packaged gems ?

PENDING

JRuby

?DavidSuárez

Tom Marble, of debian-java team, is working on it

Finish transition to new Ruby policy

Status

Item

Who

Comments

TODO

track remaining untransitioned packages and file bugs; adopt/hijack/salvage in the team or NMU or RM

boutil, gwolf

TODO

update ruby-policy package (paulvt suggested converting it to pandoc) and publish

boutil

gem2deb improvements

DONE

integrate with autopkgtest

boutil, some experiments by lunar

TODO

fake autopkgtest integration

terceiro

reap benefits before reuploading everything -- also probably happening for pkg-perl

TODO

fix remaining bugs, or mark the unfeasible ones as WONTFIX

it would be nice to use this as a way of getting new people in gem2deb maintainance

TODO

process ./TODO list in the git repository

ditto

TODO

automatically build and ship developer docs

avtobiff

please try to solve the issue of embedded jquery as part of this. See below for notes from the discussion. See also ruby-debian-doc which is an unfinished proposal on a tool to automatically generate documentation from installed packages

Issues on handling jquery embedded in autogenerated documentation:

Coordination

Status

Item

Who

Comments

TODO

Organize a (periodic?) Ruby team sprint

boutil

the first one will be in Paris just before the Paris MiniDebConf

DONE

Organize monthly IRC meetings

boutil

for reviewing progress and discussing things in general

Outreach

Status

Item

Who

Comments

TODO

Coordinate an initiative for getting more people in the team. maybe together with the general Debian mentoring initiative

we already get many RFS mails, maybe just more manpower for handling them

TODO

Coordinate PR about the state of Ruby in Debian

coverage on Ruby Weekly News woud be nice

TODO

Create a "Ruby Development" task

more useful than having a live image, and makes creating a live image easier if needed

QUESTION: [terceiro] crazy idea: would we want to work on a Debian Ruby Live/Install DVD to demonstrate the team's work? The idea would be to boot a system with everything you need to start developing Ruby and Rails right away, including nice editors, all the libraries and programs one would need.

Documentation

Status

Item

Who

Comments

TODO

Review existing team documentation in the wiki and propose a way of improving the doc itself and its maintainability

TODO

Give special love to documentation for newcomers on how to get involved and contribute

TODO

Figure out and document how to deal with packaging of apps that rely on bundler/Gemfile/etc