Ruby Team BoF - DebConf20 ========================= Tuesday, August 25th at 16:00-16:45 UTC Link to Jitsi Room TBD, but it will be available on: https://debconf20.debconf.org/talks/17-ruby-team-bof/ 0. Agenda ========= 1. Welcome to this BoF! \o/ 2. Statistics 3. What all happened since the last BoF? 4. The "good" & "bad" Parts of ruby2.7 Transition. (& what can we learn from them!?) 5. Rails 6 Transition (what's the state, what should we do!?) 6. What we want to achieve for the next release? (ruby3.0 for bullseye or bookworm?) 7. Possible sprints in 2020/21. (where - any takers? :)) 8. Any other business? 8<---8<---8<---8<---8<---8<---8<---8<---8<---8<---8< 1. Welcome to this BoF! \o/ =========================== Thank you for dropping by, we're glad that you could make it. Please introduce yourself briefly by telling us: * What's your name & nick? * What do you do in Debian & Ruby team? 8<---8<---8<---8<---8<---8<---8<---8<---8<---8<---8< 2. Statistics -> kanashiro talked to Andreas Tille last year to start to gather some data about the Ruby team in the context of his Teammetrics project, and it's live now * Thanks Andreas!! -> Uploaders * http://blends.debian.net/liststats/uploaders_pkg-ruby.png * The single person peak has been reduced - More people contributing? -> Activity in debian-ruby mailing list * http://blends.debian.net/liststats/authorstat_debian-ruby.png * Less activity, should we use it more? - Has emails been replaced by IRC discussions/meetings? -> Bugs closed * http://blends.debian.net/liststats/bugs_pkg-ruby.png * Apparently we are lowering the number of bugs closed over the years - Less bug reports? Not fixing all the bugs? - Increased the quality of our packages? -> New packages * http://blends.debian.net/liststats/wnpp_pkg-ruby.png * More people are adding new packages to the archive -> VCS commits * http://blends.debian.net/liststats/commitstat_ruby-team.png * Over time we have more people adding commits and the peak of a single person is lower -> Number of maintainers working on a package * old data (alioth) - http://blends.debian.net/liststats/maintainer_per_package_pkg-ruby-extras.png * new data (salsa) - http://blends.debian.net/liststats/maintainer_per_package_ruby-team.png * We have been increasing the number of maintainers per package - Share workload and responsabilities 8<---8<---8<---8<---8<---8<---8<---8<---8<---8<---8< 3. What all happened since the last BoF? ======================================== -> A lot of stuff! -> Mention the important stuff here: * Ruby 2.7 transition * Rails 6 transition * Sprint in Paris - Got in touch with an upstream developer (hi David o/ o/ o/) * Monthly IRC meetings * Defined a policy to micro transitions (major version bump) 8<---8<---8<---8<---8<---8<---8<---8<---8<---8<---8< 4. The "good" & "bad" Parts of ruby2.7 Transition ================================================= -> I'd like to believe that sprints for ruby2.7 transition was really good! And that we should do it again! * A sprint during transitions always speed-up the process! -> IMO, 5-day sprint was a good idea, it gave us ample amount of time to discuss and fix the key stuff. Anything lesser than that would have been very rush-y. So I liked the idea of 5-day sprints. * Our team is quite spread, a 2/3 days sprint might not worth all the effort (?) -> terceiro was not responsible to handle everything in the interpreter side * Shared the workload with kanashiro * kanashiro is *THE* guy! ;) 8<---8<---8<---8<---8<---8<---8<---8<---8<---8<---8< 5. Rails 6 Transition ===================== -> A big thanks to Praveen for doing almost all the work so incredibly well! This was nicely done! * Thanks for also guiding new people during this process -> Some apps delayed the transition (webpack, diaspora* & babel etc) We should not wait forever on other stuff until we update Rails, we can switch some things to recommend (Mailinglist will get an email) * I am not interested in OBS anymore, if other people are willing to maintain this package I'd be happy to mentor them. I am not sure about Andrew Lee and Héctor. 8<---8<---8<---8<---8<---8<---8<---8<---8<---8<---8< 6. What we want to achieve for the next release? ================================================ -> ruby3.0 is going to be the next release. -> Going to be rolled out this December. -> -preview or -rc release will be out soon-ish. There might be breaking changes kanashiro will try in Exprimental and send an email to the mailinglist debci will test out the autopkgtests -> Do we want to "try" it for bullseye? * Pros: -> ruby3.0 has a lot of amazing features. -> and it'd be nice for bullseye to have them. * Cons: -> given our release cycle, it might get chaotic. -> we might not have enough time to get it done (or can we?) -> kanashiro could lead this transition and spend some time on it * If we decide to not do it until bullseye I will be happy to stage changes in experimental and let people play with it until the next development cycle starts * utkarsh2102 could assist as well! 8<---8<---8<---8<---8<---8<---8<---8<---8<---8<---8< 7. Possible sprints in 2020/21 ============================== -> A sprint would definitely be a good idea. -> Perhaps a dedicated, online sprint in 2020. -> In-person sprints in 2021, when the world becomes a better place. * Anybody is planning to host? -> georg mentioned that he could do so in Germany. Is it still on? (We will discuss this on the list but for this year with Corona its better to have an Online one) -> ... * Depending on our decision regarding the topic above the Ruby 3.0 transition can be the main subject 8<---8<---8<---8<---8<---8<---8<---8<---8<---8<---8< 8. GSoC Project - utkarsh2102 ========================== Goal: The goal was to write some kinda of tooling that can help detect some issues that we face (like `git` in gemspec, require with relative path, and so on..) and report them upstream, hoping that they'd be kind enough to fix that! Things achieved: -> 4 cops written + 4 releases (1 more will be rolled out soon!)(next week) -> Integrated with upstream (packaging.rubystyle.guide + docs.rubocop.org/rubocop-packaging) -> 24 upstream libraries have started using it already! (Gitlab people are interested in using it) Remaining stuff (RFH): -> Forward more patches upstream, including this library as a development dependency. -> But do it the right way - politely and gently -> If you have more generic issues, please feel free to open issues, patches are heartily welcomed as well! -> More documentation, more awareness, more awesomeness! TODO: - look at ruby-combustion 8<---8<---8<---8<---8<---8<---8<---8<---8<---8<---8< 9. Any other business? ====================== > Do we want to continue the monthly meets? * or make it bi-monthly? * move to a video call? (We could always try video meetings) * do LHF (for meetings when we don't have any agenda to discuss) We can use tracker to get things to do -> Make the community more "engaging".. -> Have LHF(s) or something more engaging. -> Terceiro will add more... -> [DebConf19][ACTION NEEDED] Shruth: Create a page (git repo with .md + gitlab) for the newcomers documentation (maybe Gitlab pages) ? (We have a blog there where we can write some documentation up) -> Is the policy to micro transitions (major version bump) working well? 8<---8<---8<---8<---8<---8<---8<---8<---8<---8<---8<