Am Freitag, den 04.08.2017, 12:10 +0200 schrieb Ansgar Burchardt:
> Hi,
>
> as a more radical change one could also ask the question where to
> maintain the maintainer information. Currently we handle this in the
> source package via the Maintainer and Uploaders field, and via team
> memberships.
>
> This has several limitations: for teams, Uploaders will often be
> useless (you don't want to list all team members in every team-
> maintained package). The Maintainer field only really applies to
> Debian, in derivatives someone else should be contacted. In stable
> releases, the field can often be outdated (it records who maintained
> the package some time ago, not who currently maintains it).
Having all team members in Uploaders is __NOT__ required. It it also
not required that everyone how ever touched the package needs to be
Uploader.
(somewhat related #630578.)
As this is often brought as argument to remove Uploaders: why doe the
teams think that they need to update Uploaders on every upload?
> So I have been wondering several times whether we should move the
> maintainer information elsewhere. For example, tracker.d.o could be
> extended to record maintainer information. It could also understand
> the concept of "teams" listing team members and whom to send mails
> about individual packages.
This would be best. Having the information in some database, which is
also much more easy to retrieve programmatically a good dataset.
> For legacy purposes, the Maintainer field would then list
> ${source}@tracker.d.o and the Uploaders field could be removed.
Yes. But please not drop Uploaders first and then implement this e.g
database.
> This would also address the fact that various bits of our
> infrastructure don't know about Uploaders (like bugs.d.o only
> contacting the Maintainer).
>
> Ansgar
>
