Am 04.01.2018 um 12:54 schrieb Raphael Hertzog: > On Tue, 26 Dec 2017, W. Martin Borgert wrote: >> In case of packaging plugins or additional programs to some kind of >> "main" program, that are all maintained by the same team, it might >> make sense to use the name of then main program, not the name of the >> plugin or additional tool. > > This might create more problems... getting BTS emails for two different > source packages at the same @packages.debian.org alias might create > problems at the package tracker level. It will see bug reports for "foo" > received at an email address tagged for "bar" and it might be > misclassified. > > Really $source@packages.debian.org should be used for single packages. As > soon as you have a set of related packages, you need to use the concept of > a packaging team. I see. So for now, there's no good way to give one similar packages.debian.org address as maintainer contact to different source packages under a team umbrella? > I will work on offering a team-based email address at the package tracker > level for this kind of need. That would be very helpful indeed. Cheers jonas
Attachment:
signature.asc
Description: OpenPGP digital signature