On 15 February 2018 at 09:17, Paul Howarth <paul@city-fan.org> wrote:
[..]
Same here. Whilst I don't mind this change, as it stands I'm getting no
notifications when the packages I maintain are changed by other people,
and that's supposed to be one of the safeguards against potential
errors by provenpackagers.

Looks like here it is some technical glitch .. :-/
I'm not 100% sure how it is here with current default git settings but looks like package maintainers have not enabled watch settings on git repos which they own or to which they have RW access.
If it is true I think that repo watch should be *by default enabled for all main and secondary maintainers* and it would be good if someone will execute some oneliner to enable such watches on all git repos on all git accounts with RW access to exact git repo.
Lack of enabled watches seems is only reasons why some git PRs are not handled by package maintainers ASAP.

Just check do you have enabled watch on your package git repo (web page upper right corner -> small icon with eye -> Watch issues, PRs, and Commits).

Another part of default settings should be what is in bugzilla.
IMO any changes about git repos maintainers should be AUTOMATICALLY propagated to bugzilla as well.

I think that it would be good introduce policy stripping down RW git repo access if someone will have disabled watch for some period (half year?) and/or if email address registered in FAS settings will be rejecting send email for some period of time (half year and/or +10 rejects?).
I have impression that many FAS accounts are already dead. Every 2-3 months is done all packages mass rebuild so within half year will be at least 2-3 opportunities to check email communication with every package maintainer which have RW access to +1 git repo.
Performing such check about disabled watch enough long time or not updated email address one time a week and publishing list of repos which could be taken over by other active maintainers could allow keep as much as possible packages in healthy state.

kloczek
-- 
Tomasz Kłoczko | LinkedIn: http://lnkd.in/FXPWxH