On 02/08/2019 22.55, Michał Górny wrote: > Add two new maintainer types: 'proxied' for proxied maintainers, > and 'watcher' for people who wish to be CC-ed on bugs but are not > maintainers (e.g. upstream developers).
Can't we solve this simply in the bug tracker? The monitor setting of a user does not belong into the tree. The upstream maintainer and all other "watchers" have no write access to the tree so they will consume manpower in adding and removing their contacts to packages. The perfect solution would be that any user can add a watch filter to my-cat/mypkg in the bugtracker. Between 2018-01-01 and 2018-12-31 we received and assigned 31280 bugs. I am no fan of the descriptions in the form "please CC: If the bug is about x but not y and the moon is in the third house of the lion" This consumes extra time for every assignment and prevents automagic assignment in future. We should rather keep it simple instead of extending the options. > +There are four defined maintainer types: > + > +person > + Indicates a maintainer that is not a project, and has commit access > + to the repository. > + > +proxied > + Indicates a proxied maintainer, i.e. a maintainer that does not have > + direct commit access and needs a proxy to commit the changes. > + > +watcher > + Indicates a non-maintainer that wishes to be CC-ed on bug reports, > + e.g. a upstream developer. > + > +project > + Indicates a maintainer that is a project defined in ``projects.xml``. I think different "objects" should not be stored in one variable. "Person" or "Proxied" means here write_access=TRUE/FALSE "Project" means a group of developers "Watcher" means let Bugzilla send notifications "Person": We should name people without write access persons too... at least in public ;-) We should not introduce "watchers" as long our upstream fields in the metadata are out of date or not set at all. > +Previously, proxied maintainers were distinguished by not having a Gentoo > e-mail > +address. However, nowadays we have developers without direct Gentoo > repository > +commit access as maintainers. (formerly known as staffers) these few can use their non gentoo mail, if they do not want to do the quiz. But I think, if someone has done the staffer quiz and is very active on the ebuilds it makes most sense to go for the write access. > +There is also no reason to assume that > +in the future we would not have developers using non-Gentoo e-mail addresses. > +Adding explicit notation for proxied maintainers resolves that problem. This would make it impossible to see outside of Gentoo, who is who. I think users have a slightly higher trust in a maintainer with f...@gentoo.org than superhero1...@maildrop.cc
signature.asc
Description: OpenPGP digital signature
