Re: Q: delegation refresh and uncovered teams

[Sruthi Chandran]

On 17/03/26 18:54, Andreas Tille wrote:

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.

I like the idea. I have seen some delegated teams where the people delegated have long stopped contributing and new people who contribute are not delegated. A regular refresh of delegation is a good thing for all, we can be up-to-date with the delegated members and delegation texts. Whenever a new DPL takes charge, they review all the teams and refresh delegation if required.

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?

While some teams remaining informal is good, I can think of some of the teams you mentioned above benefiting from becoming a delegated team. I would consider talking to the existing members of the teams to check if they are OK with becoming a delegated team.

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.

I like this idea too. The Git-repository is well organized. For an incoming DPL, being able to find important information organized at one place, would definitely make life easier.

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

:)

It is my pleasure to be able to contest for DPL position. And thank you too for serving two DPL tenures :)

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

OpenPGP_signature.asc
Description: OpenPGP digital signature