On Sun, 19 Jun 2016 19:43:45 +0200 Kristian Fiskerstrand wrote: > On 06/19/2016 07:38 PM, Michał Górny wrote: > > I understand that the maintainer bugs are supposed to be much like > > developer bugs. However, I would like to point out that developer bugs > > are mostly supposed to handle two big deals -- recruitment > > and retirement, while maintainer bugs look like they are supposed to > > track every move of the proxied maintainer. > > > > To find packages maintained by a maintainer we can look metadata.xml > > files up. To find changes we can look git up / archives / specific > > bugs. Why do we need all the extra structure, except for the common > > idea of 'it looks more pro'? > > There are also cases of maintainers changing email addresses in > bugzilla, making the metadata entry erroneous. For gentoo developers we > have centralized records in ldap, for proxied maintainers we need to > replicate some structure in bugzilla. In particular since proxied > maintainers are otherwise spread out and unstructured, we need to > enforce the structure in the project. Keeping track of e-mail changes is a matter of one bug, with one comment for each e-mail change. Not 20 bugs with 80 bugspam links. -- Best regards, Michał Górny