[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: appropriate Maintainer addresses for collectively-maintained packages



Hi,

On Thu Aug 21, 2025 at 3:23 PM CEST, Simon McVittie wrote:
On Thu, 21 Aug 2025 at 11:22:57 +0200, Simon Josefsson wrote:
Uploaders: Debian <debian-devel@lists.debian.org>

I think *this* (Uploaders, not Maintainer!) would be a good way to spell "anyone can do a 'Team upload' of this package" without generating a lot of extra email to debian-devel.

Wouldn't emails to packagename@packages.debian.org still go to devel?

A package-specific address like PACKAGENAME at tracker.debian.org would seem better to me; or maybe debian-qa (which is already a high-traffic list that gets bug reports against orphaned packages), or a new list, but I think those options are actually both worse than a package-specific address.

Tracker emails are for teams, not single packages, right? If so, would one have to create a team for each package? Why not using @packages.d.o?

I think that putting the team address in Uploaders would be a better way to collect packages into buckets for the purposes of services like DMD.

Yes. But I think we're discussing about packages which do not already belong to a specific group. For those, the issue of signaling collaborative maintenance does not arise -- they are already maintained in a team.

For packages not part of any specific team, maybe we can start recommending setting the maintainer field to packagename@packages.d.o, with regular human uploaders in the Uploaders field, to signal that there's no strong ownership for the package. I think I've seen that somewhere already.

Does it make sense? Bye :)

Attachment: signature.asc
Description: PGP signature


Reply to: