Ruby Release Goals for Debian Jessie
This page summarizes some ideas about possible goals for Ruby in Jessie:
Key:
TODO = not done
PENDING= (mostly?) done, but not in the archive yet
DONE = done and in the archive
Status |
Item |
Who |
Comments |
DONE |
|||
MRI - ruby and rubyX.Y & general |
|||
Ruby 1.8, 1.9, 2.0 are gone \o/ |
everybody! |
|
|
Don't explode during the wheezy->jessie upgrade |
terceiro |
|
|
gem2deb |
|||
integrate with autopkgtest |
boutil, some experiments by lunar |
||
Coordination |
|||
Organize monthly IRC meetings |
boutil |
for reviewing progress and discussing things in general |
|
Team sprint in 2014, Paris |
boutil |
|
|
Outstanding items |
|||
MRI - ruby and rubyX.Y & general |
|||
DISCUSS |
Decide on rubygems-integration install-by-default to $HOME |
|
would for the most part change how bundler "works" (makes us different from other distros, OSes) |
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 |
? |
|
DISCUSS |
Feedback on ruby-standalone |
|
|
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 |
|||
TODO |
Rubinius |
|
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 ? |
TODO |
JRuby |
|
Tom Marble, of debian-java team, is working on it - still true? |
Finish transition to new Ruby policy |
|||
TODO |
track remaining untransitioned packages and file bugs; adopt/hijack/salvage in the team or NMU or RM |
|
|
TODO |
update ruby-policy package (paulvt suggested converting it to pandoc) and publish |
|
|
gem2deb |
|||
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 |
|
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. There is a gem2deb patch for automatic rdoc processing. What about doc using yard or needing specific options/parameters? |
Coordination |
|||
TODO |
Organize a (periodic?) Ruby team sprint |
|
next around Mini DebConf UK or FOSDEM? |
TODO |
Code review? |
|
|
Outreach |
|||
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 |
Documentation |
|||
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 |
|
|
Addtl. Info / open questions
Issues on handling jquery embedded in autogenerated documentation:
- usual procedure: in debian/rules, we usually replace the embedded jquery with a symlink to the one from the libjs-jquery package.
- it was said that packages should not depend on jquery, because if install recommends is enabled (it is by default) you might get apache and all the rest
[terceiro] actually apache will only be brought in if install suggests is enabled. It will bring stuff such as wwwconfig-common which you probably do not want when installing a ruby package with documentation.
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.