https://debconf23.debconf.org/talks/85-use-perl-annual-meeting-of-the-debian-perl-group/

use Perl; # Annual meeting of the Debian Perl Group

Room: Kuthiran

Time: Sep 15 (Fri)
      18:00 - 18:45 (Asia/Kolkata timezone)
      12:30 - 13:15 (UTC timezone)

Pad (someone might post questions): https://pad.dc23.debconf.org/p/85-use-perl-annual-meeting-of-the-debian-perl-gr
IRC: #debian-perl (and maybe #debconf-kuthiran)


Intro, part 1: Organisation
===========================

Welcome people

We need volunteers to help run this discussion:

- Who takes notes? We're using Gobby: gobby.debian.org/debconf23/bof/pkg-perl
  → TDB

- Who monitors other communication channels?
   - pad: https://pad.dc23.debconf.org/p/85-use-perl-annual-meeting-of-the-debian-perl-gr
     → TBD
   - IRC #debconf-kuthiran
    → TBD
   - IRC #debian-perl
    → TBD
   - We won't monitor the Gobby chat.

Intro, part 2: Welcome, who's here?
===================================

Introduce yourself if you like!


Intro: Agenda
=============

Anything to add to/scratch from the agenda? Order of topics?


Team status
===========

Statistics
----------

https://wiki.debian.org/Teams/DebianPerlGroup/Statistics

* Members/committers
* LHF sessions

Discussion of the general situation?

Is it sustainable?
(If not, for today we can focus on identifying and naming problems.
And later on, maybe the team could ask itself where it wants to go, strategically. For example: keep doing as much? Reduce scope to have more capacity to invest into making it easier to join the team?
We don't have time today to dive into such a deep discussion, but perhaps
this could be suited for the next in-person team sprint?)





Future of LHF?
--------------

Question to those who attended LHF sessions in the last year or so:
Are LHF still giving us more benefits than problems?

- emollier: gives some frame to do work on this team;
- ntyni: did not attend much but likes the concept
- joenio: attended 2-3 sessions recently

If we keep LHF:

Current date + time: 17:00 UTC and 19:00 UTC alternatively
Is the current timeslot very problematic for some people who would like to attend?



Perl 5.38
=========

in experimental
http://perl.debian.net
http://perl.debian.net/rebuild-logs/perl-5.38/report.html (automatic binNMUs for arch:any packages to update perlapi-5.xx and libperl5.xx dependencies)
http://perl.debian.net/rebuild-logs/perl-5.38-throwaway/report.html (rebuild tests for all perl reverse dependencies including arch:all packages)
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=perl-5.38-transition;users=debian-perl@lists.debian.org
https://udd.debian.org/cgi-bin/bts-usertags.cgi?user=debian-perl%40lists.debian.org&tag=perl-5.38-transition

Timeline?

 - October should be doable

TODOs?

 - A few bugs are open, some are not filed yet, nothing major.
 - A few packages cannot be fixed but no big blocker at the moment.

@ntyni:

- Do we need to create a gobby doc Perl-5.38-QA like the previous transitions?

  - In the past Gobby was used to classify issues
    arising from test rebuilds done with the new candidate
    packages.
  - Did not use it this year since ntyni was doing the work
    by himself.

- Is there a doc somewhere about the 5.36 upgrade, that we could link to from
  https://wiki.debian.org/Teams/DebianPerlGroup/OpenTasks#Transitions?

   - answer: not really. It would be good to have some doc about
     such transitions, there's some stuff on the wiki.
     ntyni will try to write something.

Tooling for inactive group members
==================================

Was planned for DebCamp 2020 → cancelled because pandemic
Action item 2022: explicit TODO item in the open tasks list in the wiki → didn't happen

We do have a procedure, what's not working any more is getting the last activity from alioth.

* Do we want this? If not: don't rehash each year :)
  - Is there another goal than Principle of least privilege?
    - get a realistic view about team numbers
  - How do other teams with tons of members handle this problem?
    - We don't know. But we should maybe work with them
* If yes: plan (who what when)
  - Since we apparently don't have tons of capacity to solve this ourselves, one way forward could be to work with other large teams.
  - joenio volunteers to try to contribute on this.

Sprints
=======

* 1 (unofficial) sprint at DebianReunionHamburg
  - 4 attendees
  - updated packages, improved our tooling
  - Details: https://gobby.debian.org/export/Teams/Perl/Team-Sprint-Hamburg-2023

* Sprint 2023/24?
  - https://wiki.debian.org/DebianEvents/de/2024/MiniDebconfBerlin ?
    2024, May 14-21, Berlin (Germany)
    - sounds good for ntyni; usually May is OK for ntyni wrt. upstream
      perl schedule (a bit later would be even better though in that respect)
      also good to have it together with a mini-DebConf rather than a separate event
    - sounds good to gregoa
    - emollier +1
    - joenio would like to but not sure he can make it



Git branch names
================

* DEP-14
* BoF 2021: we should be consistent across packages,
  and if we change, this needs coordination and probably helpers
  (remote repos, local repos, tools, …) and an "owner"
* BoF 2022:
  Decided: it is "debian/latest"
  AI: dam is going to "drive" the effort
* Since then: some notes and research,
  https://gobby.debian.org/export/Teams/Perl/new-branch-layout

→ plan (who what when)


Any other business?
===================