On Thu, Jun 27, 2024 at 01:41:25PM +0000, Jeremy Stanley wrote:
> [...]
> > Um, citation needed.
> [...]
>
> I'll need to do some digging to confirm, but as for the approximate
> timeframe my addled memory recalls this came up during the
> dissolution of Alioth, when it was proposed to recreate all the team
> aliases as mailing lists, and a listmasters representative said
> something along the lines of "please don't do that." It's not clear
> to me that they meant no package teams should have mailing lists or
> set them as package maintainers, but were rather concerned that
> creating hundreds of new lists just to receive BTS messages was a
> poor use of resources. If the topic also came up at another time, I
> don't remember.
Either way, there are currently 2300 distinct source packages listing
53 distinct lists.debian.org addresses in the Maintainer field. The
claim that this configuration is not allowed is not backed up by
reality.
root@42fc115690e5:/etc/apt# grep-aptavail -F Maintainer -s Source
lists.debian.org | awk '{print $2}' | sort | uniq | wc -l
2300
root@42fc115690e5:/etc/apt# grep-aptavail -F Maintainer -s Maintainer
lists.debian.org | awk '{print $NF}' | sort | uniq | wc -l
53
Given this context, we should not be making any changes to the
configuration of the debian-cloud packages at this time. If listmaster
decides to start campaigning project-wide against this pattern, then we
can obviously reconsider.
noah
