Dominik George wrote: >>The right solution is to have a canonical place within the project >>where the list of members of every team is stored and kept up-to-date. >>It is definitely not duplicating that information in every package. I >>don't know whether that already exists. > >How should that work?
It could be a wiki page, a database table, whatever is deemed more useful (the wiki page would probably be better for humans, the database for programs). Every team would be responsible of keeping the list of its members up to date. It doesn't seem a heavy task. > there is no technical way to determine whether a package is team-maintained > or not by looking at Maintainers Isn't there? I was assuming that if a package is team-maintained, the Maintainers field contains the team's name. Are you concerned that one might not be able to distinguish whether a name identifies a team or a human? Even if that could be a real concern (I don't know whether there is any Debian contributor called John Team, Team Smith, or anything like that), having all the team names stored in a canonical place would solve it: if and only if the name matches that list, then it's a team. Gerardo
