Differences between revisions 2 and 50 (spanning 48 versions)
Revision 2 as of 2013-08-16 09:52:21
Size: 2159
Comment:
Revision 50 as of 2014-08-29 06:35:23
Size: 6144
Editor: ?CédricBoutillier
Comment: possible locations for next sprint, mention gem2deb patch for documentation
Deletions are marked like this. Additions are marked like this.
Line 11: Line 11:
== Ruby 1.8 removal ==

Transition tracker: http://release.debian.org/transitions/html/ruby1.8-removal.html
Line 16: Line 13:
|| ''PENDING'' || Drop Ruby 1.8 suppor from gem2deb || AntonioTerceiro || done in git ||
|| ''TODO'' || Identify packages with hard dependency on ruby1.8 and file bugs || || ||
|| ''TODO'' || Make sure non-leaf packages are fixed || || this is not about doing all the work alone, but tracking the progress it and poking people ||
|| ''TODO'' || special case: KDE ruby packages still build for Ruby1.8 only || || ||
|| ''TODO'' || identify Ruby 1.8-only packages probably throw them away || || ||
|| ''TODO'' || Request removal of ruby1.8 || || ||
||<rowspan=9>'''DONE''' ||
||||||||<style="font-weight: bold; font-size:120%; text-align:left; line-height:250%;">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 || ||
||||||||<style="font-weight: bold; font-size:120%; text-align:left; line-height:250%;">gem2deb ||
|| integrate with autopkgtest || boutil, [[https://lists.alioth.debian.org/pipermail/pkg-ruby-extras-maintainers/2013-September/016366.html|some experiments by lunar]] ||
||||||||<style="font-weight: bold; font-size:120%; text-align:left; line-height:250%;">Coordination ||
|| Organize monthly IRC meetings || boutil || for reviewing progress and discussing things in general ||
|| Team sprint in 2014, Paris || boutil || ||
||||||||<style="font-weight: bold; font-size:150%; text-align:left; line-height:250%;">Outstanding items ||
||||||||<style="font-weight: bold; font-size:120%; text-align:left; line-height:250%;">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 || || ||
||||||||<style="font-weight: bold; font-size:120%; text-align:left; line-height:250%;">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? ||
||||||||<style="font-weight: bold; font-size:120%; text-align:left; line-height:250%;"> 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 || ||
||||||||<style="font-weight: bold; font-size:120%; text-align:left; line-height:250%;">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 [[http://anonscm.debian.org/gitweb/?p=pkg-ruby-extras/ruby-debian-doc.git;a=summary|ruby-debian-doc]] which is an unfinished proposal on a tool to automatically generate documentation from installed packages. There is a [[https://lists.debian.org/debian-ruby/2014/04/msg00073.html|gem2deb patch]] for automatic rdoc processing. What about doc using yard or needing specific options/parameters? ||
||||||||<style="font-weight: bold; font-size:120%; text-align:left; line-height:250%;">Coordination ||
|| ''TODO'' || Organize a (periodic?) Ruby team sprint || || next around [[https://lists.debian.org/debian-devel-announce/2014/08/msg00011.html|Mini DebConf UK]] or FOSDEM? ||
||||||||<style="font-weight: bold; font-size:120%; text-align:left; line-height:250%;">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 ||
||||||||<style="font-weight: bold; font-size:120%; text-align:left; line-height:250%;">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 || || ||
Line 23: Line 52:
QUESTION: add lintian checks for packaging depending on ruby1.8?
Line 25: Line 53:
== Other interpreters == === Addtl. Info / open questions ===
Line 27: Line 55:
|| Status || Item || Who || Comments ||
|| ''PENDING'' || ruby2.0 || AntonioTerceiro || mostly done in git ||
|| ''TODO'' || Rubinius || AntonioTerceiro (WILL APPRECIATE HELP) || WIP in git, probably already outdated wrt upstream ||
|| ''TODO'' || JRuby || || talk to Java people if they are interested to update their package ||
Line 32: Line 56:
QUESTION: is anyone from the Ruby team actually interested in JRuby? 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.
Line 34: Line 61:
== Finish transition to new Ruby policy ==
Line 36: Line 62:
|| Status || Item || Who || Comments ||
|| ''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 improvements ==

 * fix remaining bugs
 * process TODO list

== Coordination ==

|| Status || Item || Who || Comments ||
|| ''TODO'' || Organize a (periodic?) Ruby team sprint || || ||
|| ''TODO'' || Organize monthly IRC meetings || || for reviewing progress and discussing things in general ||

QUESTION: do we want/need a monthly IRC meeting?
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.

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?

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.