AGENDA! \o/


- Presentation of present people
- Plans for the bullseye release:
	- Rails 6 transition?
		+ Rails 6 RC1 released.
		+ dependencies are ready for RC1 / now starting rdepends
		+ in Salsa wiki: https://salsa.debian.org/ruby-team/rails/wikis/Transition-to-Rails-6-for-Debian-Bullseye
	- Ruby 2.7/2.8 transition?
		- ruby 2.8 might be too late
	- Use debhelper-compat (=12), instead of "debhelper (>= 11~)" and d/compat. is problem with dwz solved?
	- Make all the packages autopkgtest-able (maybe a LHF or something?)
		- fetch tests from upstream (don't hesitate to use tarballs from GitHub instead of gems)
		- change dh-make-ruby to use github in debian/watch if metadata says package homepage is a github repository
	- Try to use cme (libconfig-model editor) to refresh debian (e.g. control) files?
	  (or something else if someone has other experience from other teams)?
	- Also tools to push changes to several (all) git repos of the team
	- debian/upstream/metadata

- Better support for newcomers:
	- Reviewing and sponsorship process
	- Encourage people with no uploading rights yet to review RFS requests
	- Regroup/Update/Improve documentation wiki.debian.org/Ruby (and other pages scattered)
		+ it may be easier for newcomers to write/update doc about what they learn
	- Salsa CI pipeline for all packages
	- [ACTION NEEDED] Shruth: Create a page (git repo with .md + gitlab) for the newcomers documentation (maybe Gitlab pages) ?

- Team meetings:
	- Ruby Sprints (yearly, maybe?)?
	- Revive (monthly or bimestrial) IRC meetings?
	- [action] utkarsh: Send an email to the mailing list about next sprint
	
- Call for Help:
	- The interpreter and toolchain maintenance.
		+ Handle BTS
		+ Pay attention to security updates in stable
		+ Keep up with upstream in testing/unstable
		+ Latest transition steps were documented in wiki 
		  - https://wiki.debian.org/Teams/Ruby/InterpreterTransitions
		  - for 2.5: https://wiki.debian.org/Teams/Ruby/ruby2.5

- Discussion:
	- Different versions of Rubygems available in the archive (Andrew Lee).
	- Provide infra (containers) support to users like upstream (Andrew Lee).
		- i.e.: building a .deb package of an app that uses specific versions of gems (bundler) instead of the ruby-* packages
		- python has a similar thing where a .deb can contain an entire python virtualenv. it's possible to do something similar for ruby, "just needs to be done" :-)
	- Try to build all reverse (build) dependencies is very nice but sometimes can take a very long time, especially when it goes back to gitlab... (local machine)
		+ Praveen: ci.debian.net provides api for running autopkgtests of reverse dependencies

	- track obsolete libraries (that were used e.g. only as build dep of old dependencies...)
	  + Can we use https://pet.debian.net/pkg-ruby-extras/pet.cgi ?