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

use Perl; # Annual meeting of the Debian Perl Group

Room: Ereniku

Time: Jul 20 (Wed): 17:00 - 17:45 CEST aka UTC+2 (≈ 3 p.m. UTC)

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


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

Who takes notes? Who monitors (which) IRC channels/pads?
notetaker/IRC monitor: dam


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

Introduce yourself if you like!

emollier> hm, looks like I didn't make it; will try to share thoughts via gobby.
emollier> Hi, I'm Étienne, I joined in 2020 when needing to pull perl deps to a
          package I was introducing in the Debian Med team, then stayed around.


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

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

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

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

* Members/committers
* LHF sessions

General discussion?
Future of LHF?
Usual question: do we keep the date + time (17:00 UTC and 19:00 UTC alternatively)?
Jitsi was used once

emollier> regarding lhf, I suppose I'll stand on my opinion it is nice to have
          a regular meeting at a known point in time, especially to fit in an
          otherwise busy schedule.
emollier> no problem for me on the time, but they might be deemed too Europe/
          Africa/America centric perhaps?

AI: dates in wiki

Perl 5.36
=========

in experimental
http://perl.debian.net
http://perl.debian.net/rebuild-logs/perl-5.36/report.html
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=perl-5.36-transition;users=debian-perl@lists.debian.org

Only one open bugreport of a package that FTBFS on various architectures anyway

Timeline?

ntyni on IRC:
> hey, can't join the bof on wed but status update on perl 5.36: looking good, no known 
> blockers, aiming for a transition in September or so but we'll see


# 3 next topics copied from debconf21/bof/pkg-perl
# and: we should discuss this earlier …


dgit
====

From BoF 2019:
	We (?) feel it's too early to discuss whether we should use this
	consistently across the team.

Anything to discuss?

emollier> it has been a bit delicate to get started with dgit, trying stuff
          often involves package upload and modifications in the git tree:
          changes not always obvious to undo (YMMV).
emollier> day to day work /seems/ to boil down to dgit --gbp push-source,
          with an eventual --overwrite if previous upload went with dput.
          Not sure of adversarial effects so far if I'm doing something wrong.

Conclusion: (?) try it if you like, perhaps arrange a session with switton
who can share more about the possible positive effects

salsa-ci
========

From Bof 2019:
	1. It is OK if some of us enable it for some packages, for which they
	would like to take benefit from the Salsa CI pipeline, as long as they
	keep an eye on the results and take care of it. If this harms the work
	of other team members, please say so and we'll adjust/disable/whatever.

Reports in #debian-perl-changes

https://salsa.debian.org/salsa-ci-team/pipeline/-/blob/master/README.md
"recipes/debian.yml@salsa-ci-team/pipeline"

Anything to discuss?

emollier> if enabled on a large number of packages, I believe it's important
          that bulk changes do not trigger thousands of batches of salsa-ci
          at once.

Non-action: not enabling CI for all packages. Individual developers are free to
experiment (and watch for the results)

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

Was planned for DebCamp 2020.
Action item: explicit TODO item in the open tasks list in the wiki


Sprints
=======

* 1 (unofficial) sprint at DebianReunionHamburg:
  https://perl-team.pages.debian.net/docs/sprint-hh2022/report-hh2022.html
* Sprint 2022/23?

emollier> likely to be present for BSP at Karlsruhe in October,
          hope to be around Hamburg next year in May.

No separate sprint on the horizon. Other events where at least two group
members are present can be blessed to be "sprints".

SnowCamp may not happen because of the pandemic


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

* git warns about master
* DEP-14 suggests debian/unstable or debian/latest
* 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"

Decided: it is "debian/latest"
AI: dam is going to "drive" the effort

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

embedded devices mentioned as a way to bring people starting with programming
"adafruit circuit playground express". it would be great if it could use Perl
instead of Python :D