Q: delegation refresh and uncovered teams

Hi Sruthi,

as part of preparing the transition to the next DPL, I have been
thinking about how to make delegations easier to review and maintain.

One idea I am considering is to explicitly confirm their willingness to
continue, and to treat existing delegations as time-limited until they
are reconfirmed by the incoming DPL (for example within the first six
months of the new term). The goal would be to provide a clear and
well-defined starting point, ensure active consent, and make it easier
to refresh delegation texts where needed. I would be interested to hear
whether you would consider such an approach helpful or appropriate.

In addition, while looking at the organisation page[0], I noticed that
some areas appear to lack an explicit delegation despite having ongoing
responsibilities. Examples include:

  * Web Pages
  * Planet Debian
  * Partner Program
  * Hardware Donations Coordination
  * Bug Tracking System
  * Mailing Lists Administration and Mailing List Archives
  * Security Team
  * Mirrors Team
  * MIA Team

Do you think it would make sense to formalise delegations for some of
these areas, or do you prefer to keep certain teams intentionally less
formal?

To support the transition, I have prepared a list of current delegations
as well as draft texts in Git[1] including a draft I might sent before
my term ends to make all existing delegations time-limited[2].

My intention with this idea is to make things easier for the future DPL
and to improve transparency, not to create additional process or
pressure.

Thank you for your thoughts, and thank you for standing as candidate.

Kind regards
   Andreas

[0] https://www.debian.org/intro/organization
[1] https://salsa.debian.org/debian-dpl/dpl-helpers/-/tree/master/delegations?ref_type=heads
    (every dir with active delegations has a draft named new_delegation
     with delegates names to activate)
[2] https://salsa.debian.org/debian-dpl/dpl-helpers/-/blob/master/delegations/delegation_changes?ref_type=heads