Bits from the DPL

--ad0pjlpjGPeehx+5
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Dear Debian community,

This is bits from the DPL for March.

1. Elections
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

I made it clear early on that I would not run again in order to
encourage others to step forward as candidates for DPL, as I believe
that a broader field of candidates strengthens the role and the project
as a whole. I am therefore particularly pleased that Sruthi Chandran
decided to run, and I trust her to do a good job in this position. It is
not the first time that I have ranked her highest on my ballot. I am
confident that I am handing over my duties into responsible hands.

Separately, regarding some past contributions on debian-vote, I intend to
propose an adjustment to the list policy to permit only signed mails.


2. Age declaration laws affecting Debian
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

Recent discussions have started around new age verification legislation
that may affect free software operating systems. In particular, the
California Digital Age Assurance Act (AB 1043), expected to take effect
in 2027, raises questions about whether operating systems and package
distribution mechanisms could be required to provide age-related
information to applications. In parallel, a recently adopted law in
Brazil appears to introduce similar requirements and is already in
force, with initial interpretations suggesting it could apply to
components such as package management tools. These developments are
currently under discussion within Debian and other projects, and SPI has
initiated efforts to obtain legal guidance. At this stage, the situation
remains unclear, and further analysis is ongoing.

=46rom a non-lawyer perspective, it is not yet clear how such regulations
apply to a non-commercial, volunteer-driven project like Debian, which
does not sell software and provides it in a highly decentralized way. It
seems plausible that obligations, if any, may primarily affect
redistributors or commercial entities building products on top of
Debian. In such cases, Debian would as usual be open to contributions
that help downstreams meet their requirements, while keeping such
features optional and respecting the needs of users in other
jurisdictions. However, this is an area where proper legal analysis is
still required.


3. Chemnitzer LinuxTage
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

At the end of March, I attended the annual Chemnitzer Linux-Tage, an
event I have been regularly visiting for over 20 years.

During the conference, I led a packaging workshop[1], where we worked
on practical aspects of Debian packaging with participants.

In addition to staffing the Debian booth, I gave several interviews. One
of them was with the German computer magazine c=E2=80=99t magazine.  I also
recorded a video interview with the Tuxflash Podcast[2], as well as an
interview with Mitteldeutscher Rundfunk. Both are expected to be
published soon.

[1] https://chemnitzer.linux-tage.de/2026/de/programm/beitrag/142
[2] https://tuxflash.de


Kind regards
    Andreas.


--ad0pjlpjGPeehx+5
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAABCAAdFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmnRWuIACgkQV4oElNHG
RtH5qQ//ft4b4uZwzwgd/zHyJOHwxCwaZK00WbHzXkbK0qpYxz8oCDnNlxu2KLeK
bXBxiKck0/9Lh0C+8naP8tXdKFeIhvzWlZD+RBQ7+6kxUxe+rtf7ht9DHyWU9n/5
DUv8ZFfGfgFrlx/FDqVGIM80zbD/qY0dQy25DPL3SOzz9lgVXdY/zAnyBH64Fwg7
Xk5ZG2E4YhR4gSsdsbz1eaoqkvoXfV+L7HDYwU6RdSaOvHWkZYng3CjiDaip31gI
2yI1xV1l34jJ2wMT1KY/83JvB4z0qznmjIsvmCf9PAnV57T3N0aQiAXKE/8hwGV7
MbrfbFjCYa6BV56u+6TdhbVVVKiilQ5B4qieVupJidj8zly9xaxlxWQ+DUI5zVRe
XdcgwqdEDRcAGMVDC0hDGCc0I2o98m6QXF3b/xhATht8HJtH24tpk86yzqZH2IFG
MioIjCqWpEyapqqJmCpungGjoiRq7A+Sd48fazXwhzc/W46WpY0Yd6lDiv1d6Dt9
Gb0XwOhxRPBcz36GyzhNYTo06Uq5HAxyFynNJ0qKKR81Sb9x3TO5Js+9lEI678F8
iIB66zCQ009Uh8FR7nilk/RJ3iD9ZcA8MnGDgoKZe4N45CKwjDbElqIFQYbQMnAk
xCuAzRgTQ9kRYdw0Vwao7/doCNdeUj+OA3QaiSc3v3gbKUEY4VM=
=DJTG
-----END PGP SIGNATURE-----

--ad0pjlpjGPeehx+5--