On 1. 6. 25 23:15, Timofei Zhakov wrote:
On Sun, 01 Jun 2025 at 7:39 PM, Nathan Hartman<hartman.nat...@gmail.com>
wrote:
On Sun, Jun 1, 2025 at 11:39 AM Daniel Sahlberg <
daniel.l.sahlb...@gmail.com>
wrote:
Den sön 1 juni 2025 kl 16:31 skrev Daniel Sahlberg <
daniel.l.sahlb...@gmail.com>:
Hi,
I like the e-mail notifications from GitHub Actions when a build fails
or
when it starts to work again - saves some time from going into the
website
to check status.
Should we enable this for Serf?
Should it go to dev@ or should we create a separate notifications@
list?
I presume the safe path would be to just create a separate mailing list
and add notifications there, but maybe there is not really need for a
separate list?
Oh, there IS a notifications@ list already, see
https://lists.apache.org/list?notificati...@serf.apache.org. It was last
used in 2020 by BuildBot (I assume it was never migrated to the new
ci2.apache.org, can't find Serf there). The list has TWO subscribers
(actually: three, since I just joined) so I assume there is little harm
in
setting up notifications to that list.
I'm going to assume lazy consensus to do this, if no replies within the
next 72 hours (although it may take longer than that).
+1 for this, similarly to how we've done for Subversion. Since most/all (?)
of the Serf devs are also Subversion devs, there's an advantage in being
consistent!
I'm also going to do a website change to document this list - I will do it
as soon as time permits, easy to revert if we decide this list is not
useful.
Thanks for taking care of this.
Cheers,
Nathan
Also, in relation to this topic, in subversion we have separate mailing
lists for commits and dev. This is very useful to setup filters in mail
client and for example read one list more frequently than another. Would
this make sense to somehow separate those lists in serf as well?
There was almost never enough traffic on this list to warrant having
another one. Filtering should be quite straight-forward, too: "contains
'svn commit: r'" would work.
-- Brane
