Le Thu, Feb 19, 2026 at 07:31:44AM +0100, Tobias Frost a écrit : > > the information in the Uploaders field is less about determining activity and > more about enabling action once inactivity has been established. > > If team membership is not clearly documented, we cannot easily determine > which team should be contacted when someone goes missing.
Le Thu, Feb 19, 2026 at 10:41:51PM +0100, Tobias Frost a écrit : > > Do you have some concrete query in mind that you could share with me, which > would tell (quickly and with accuracy) that someone stopped working on a > package and we need to tell someone, e.g a team? Hi Tobias, this is the whole point of making the Uploader field optional. When absent, it means that every team member is equally in chage for the package, and that when one member of the team leaves or becomes inactive, nobody changes for that package. If a team member does not list themselves in the Uploaders field of of a team-maintained package, then there is no need to notify the team that the member is inactive. With that point of view I still do not understand how making the Uploaders field makes your work harder. I do get the point that if an Uploader-optional policy were abused, with people agressively removing the field, especially when the package mainainer is not a formal team, it would be bad for you, but maybe the solution is to carefully word the policy change to make it clear that antisocial behaviour is not welcome? Have a nice day, Charles -- Charles Plessy Nagahama, Yomitan, Okinawa, Japan Debian Med packaging team http://www.debian.org/devel/debian-med Tooting from home https://framapiaf.org/@charles_plessy - You do not have my permission to use this email to train an AI -
