Hi Lucas, thanks a lot for your comments. Unfortunately it slipped through my attention - sorry about this.
Am Tue, Oct 21, 2025 at 11:23:02AM +0200 schrieb Lucas Nussbaum: > > I think that it would be useful to try to phrase delegations in a way > that states what teams are ultimately responsible for (that is, which > powers are delegated by the DPL) in addition to stating what their daily > activities are. > > For example, it looks to me that the DFSG Team essentially does two > things: > > * Decide on the interpretation of the DFSG that is applicable to the > Debian archive, that is, decide which packages are acceptable in the > Debian archive. > > * Decide on the content of the Debian archive (review new packages, > remove packages that do not match our intepretation of the DFSG). That's a very good hint. I will respect this in a future delegation. > Regarding the Archive Team, I'm not sure if it formally requires a > delegation, as I understand that its activities are mainly about > supporting other teams (DFSG team, release team, packaging teams) by > managing the archive and the associated tooling. IMHO the tasks are connected to certain permissions on the archive. Shouldn't this be backed up by a delegation? Sorry for spotting this mail to late and thank you for the hints Andreas. -- https://fam-tille.de
