Den sön 1 juni 2025 kl 19:39 skrev Nathan Hartman <hartman.nat...@gmail.com
>:

> 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 went ahead with this.First notification was received earlier tonight [1].

For the record, this is controlled by the ghactions.py script in ASF
Infra's git repo infrastructure-gha-notifier[2]. I made a pull request
which was kindly merged by Humbedooh [3].

Feel free to subscribe to notificati...@serf.apache.org if you want to
receive those notifications.

Cheers,
Daniel

1: https://lists.apache.org/thread/w45rgbr5fk1m3zbv8hl9p8c3y9osrlm9
2: https://github.com/apache/infrastructure-gha-notifier
3:
https://github.com/apache/infrastructure-gha-notifier/commit/4c4416bd1ee49442b0f8105433e17d5ef90d583a

Reply via email to