# Ruby team BoF agenda ## Introductions Let's make a round of introductions so we can meet any new team member joining us today :) ## Some statistics Thanks Andreas for providing data through teammetrics! http://blends.debian.net/liststats/authorstat_debian-ruby.png http://blends.debian.net/liststats/bugs_pkg-ruby.png http://blends.debian.net/liststats/commitstat_ruby-team.png http://blends.debian.net/liststats/maintainer_per_package_ruby-team.png http://blends.debian.net/liststats/uploaders_pkg-ruby.png http://blends.debian.net/liststats/wnpp_pkg-ruby.png it would be good to have the evolution of the number of bugs open too... about the curve of maintainers: does it count unique names in salsa commits, or the Uploaders field of the control file? ## Ruby 3.2 transition This subject was raised in our mailing list recently: https://lists.debian.org/debian-ruby/2023/07/msg00012.html Steps before we really start the transition: - Package ruby 3.2 (upload to experimental) - Update ruby-defaults to use ruby 3.2 as an alternative interpreter (upload to experimental) - Rebuild reverse dependencies and file bugs if any issue is found - Fix all issues - Start the transition in unstable (coordinate with the release team), planned for october ## Rails 7 transition - Hard transition, breaking changes - Try to not entangle with ruby transition - Start after ruby 3.2 transition ## Rack 3 transition - Maybe do it together with the rails 7 transition ## RuboCop::Packaging update! \o/ \o/ - https://github.com/utkarsh2102/rubocop-packaging/ - https://rubygems.org/gems/rubocop-packaging - Drop many patches from our packages, lowering the maintenance burden - Development is not so active but it is still really helpful for upstream maintainers ## Next sprint? - Paris is still doable, depending on the calendar - Terceiro mentioned he could try to host the sprint in Salvador, Bahia, Brazil - Maybe try to do it around MiniDebConf Brazil in the beginning of May + Make sure it is not too late for us ## Inactivity in our team - After sprints and release our team reduces the amount of work done - we could try to organize (again) regular IRC meeting, maybe not monthly, but every 2 months - encourage people to send update of their works, like what people do for debian-lts - [ACTION ITEM] Utkarsh will send an email to the mailing list about rebooting our IRC meetings (comments above from Cedric) ## MiniDebConf 24 in Japan (DebConf 25) - Great ruby community there - Maybe use those events to improve our relationship with upstream maintainers -