From: tille@debian.org   
      
   Dear Debian community,   
      
   This is bits from the DPL for January.   
      
   1. Changes around FTP / DFSG structures   
   2. When stepping back goes unspoken   
      2.1. MIA team   
      2.2. Keeping Packages Approachable   
      2.3. Delegates   
   3. FOSDEM   
      
      
   TL;DR:   
   An update on FTP/DFSG changes, followed by a reflection on handling   
   changes in contributor availability across Debian, including possible   
   implementation work around the MIA team, and a brief FOSDEM note.   
      
      
   1. Changes around FTP / DFSG structures   
   =======================================   
      
   In the past weeks we have discussed changes to the organisation of   
   FTP/NEW and DFSG tasks.  I would like to briefly explain the background,   
   without reinforcing an "old versus new" narrative.   
      
   Related concerns and reflections from the Community Team have been   
   shared in a recent announcement[c01], which provides additional context   
   on how these changes are perceived more broadly within the project.   
      
   Over an extended period of time it became clear that essential work in   
   this area was carried by very few people. This affected day-to-day   
   processing as well as transparency, predictability and communication.   
   Situations like this are unfortunately not uncommon in Debian and can   
   arise not from bad faith, but from long-grown structures, increasing   
   workload and limited opportunities to address problems early.   
      
   Ahead of the recent changes, starting in my first DPL term I made   
   several attempts to engage with the relevant delegates and to solicit   
   feedback.  These efforts did not lead to sufficient shared understanding   
   to develop a sustainable path forward. Under these circumstances,   
   organisational decisions were necessary to ensure continued   
   functionality in an area that is foundational to Debian.   
      
   I want to stress that this reorganisation is not a judgement of the work   
   or commitment of individuals. Much of what works today is the result of   
   years of dedicated effort, often under difficult conditions. At the same   
   time, as a project we need structures that distribute responsibility   
   sustainably and support transparency, collaboration and renewal.   
      
   The new team has already started its work. Its focus is now on   
   stabilising processes, improving communication and building trust.   
      
   A short note on the transition period: following the delegation of the   
   new DFSG team, access to the NEW queue and related operational details   
   was not immediately available. This made it difficult for the team to   
   carry out hands-on training and to prepare workflows ahead of taking on   
   their responsibilities.   
      
   While the upcoming delegation had been announced several weeks in   
   advance, some of the necessary technical and procedural handover steps   
   could only be completed later. As a result, the new team was not able to   
   start working at full capacity from day one.   
      
   This requires time, calm and support from the wider community.   
      
   I therefore ask everyone to view the current situation not as "old   
   versus new", but as a necessary step towards a Debian that remains   
   reliable, open about challenges and mindful of the people doing the   
   work.   
      
      
   Remark regarding the Archive team   
   ---------------------------------   
      
   I would like to explicitly thank Ansgar for the work he did on the   
   SQLAlchemy transition of DAK and its upgrade of the hosts maintained by   
   the archive operations team to Trixie. This was important work for the   
   project, and I very much appreciate that he took care of it.   
      
   [c01] https://lists.debian.org/debian-devel-announce/2026/01/msg00010.html   
      
      
      
   2. When stepping back goes unspoken   
   ===================================   
      
   The following thoughts are not specific to the recent changes around   
   FTPmaster or DFSG, but reflect a more general pattern I have observed   
   across different areas of Debian over time.   
      
   During my time as DPL, an earlier gut feeling has gradually turned into   
   a clearer observation: Debian has a structural challenge that is easy to   
   overlook precisely because we are a volunteer project.   
      
   Debian exists because people freely choose to spend their time on it.   
   That is something I deeply value, and it is a large part of why Debian   
   works as well as it does. At the same time, most of us joined with   
   enthusiasm, not with an explicit agreement to later announce when our   
   available time, energy, or interests change. Life circumstances shift,   
   priorities evolve, interests fade - all of this is normal and entirely   
   legitimate.   
      
   What we largely lack, however, are lightweight and reliable ways to   
   communicate those changes to each other.   
      
   For many volunteers, being asked directly whether they are still active   
   or whether others can rely on their work can feel uncomfortable -   
   especially when the question comes from a friend or colleague. Out of   
   consideration for each other, we often avoid asking. Out of the same   
   consideration, we also avoid proactively stating that we have stepped   
   back. As a result, responsibilities can quietly drift rather than being   
   consciously handed over or concluded.   
      
   This dynamic creates a kind of implicit protection for contributors,   
   which is understandable and well-intentioned. At the same time, it can   
   have real consequences for the project: bugs remain unattended,   
   security-relevant accounts are left without active oversight, or   
   delegated roles continue to exist on paper without clear current   
   ownership.   
      
   This is not about questioning anyone's commitment or goodwill. It is   
   about recognising that, in a long-running volunteer project,   
   availability changes - and that Debian currently has few established   
   ways to make those changes visible in a timely and low-pressure manner.   
      
   Over time, this has led me to think about how Debian could handle such   
   changes in availability more consciously and more consistently. Rather   
      
   [continued in next message]   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)