Re: Changes to Phabricator review subscriptions
- Date: Wed, 9 May 2018 22:18:20 +1200
- From: Ben Cooksley <bcooksley@xxxxxxx>
- Subject: Re: Changes to Phabricator review subscriptions
On Wed, May 9, 2018 at 9:47 PM, Milian Wolff <mail@xxxxxxxxxx> wrote:
> On Mittwoch, 9. Mai 2018 10:08:28 CEST Ben Cooksley wrote:
>> Hi all,
>> To improve the user experience around email and in-application
>> notifications from Phabricator, sysadmin have made some changes to the
>> configuration of our Herald rules.
>> Going forward, instead of subscribing projects to reviews, we will
>> only be subscribing mailing lists now. For those reviews which have
>> already been created, they will be updated to reflect the new practice
>> the next time they are changed.
>> This means that individual project members will no longer receive
>> notifications and emails for every single review or task change that
>> affects their project. Instead, they will only receive notifications
>> and emails for reviews they have been individually subscribed to.
>> To help this change take full effect, it would be appreciated if
>> people refrain from adding Projects as reviewers, as that will have
>> the effect of subscribing the Project to the review as well
>> (Phabricator does not require you specify a reviewer)
>> Should anyone have any questions regarding this, please open a thread
>> on the kde-devel@xxxxxxx mailing list.
> Is there a way to opt-in to the old behavior somehow? Or I can somehow
> manually register myself on phabricator to be notified about $anything that
> affects a given repo?
> I ask mainly for smaller projects like heaptrack, which don't even have a
> mailing list afaik.
Please note that anyone who hasn't had a Herald rule explicitly setup
for them is unaffected by this (this includes Heaptrack, as well as
Krita and GCompris)
The changes I made a few hours ago were only to Herald rules.
For projects which lack mailing lists (like Kile) we will continue to
subscribe Projects (as the level of traffic should be much lower and
there is no other option for notifying those involved).
This change was principally made for larger projects (who have mailing
lists) and whose activity levels and number of people involved make
notifications and email to everyone and the mailing list unusable.
> Milian Wolff