Re: GitHub Activity Summary failures

Thanks Emilia, for looking after the summary bot!

I noticed no activities from the ActivityPub API TF were included in the
summaries, so I’ve just submitted a PR for that.

Regards,
Django


On Sun, Dec 7, 2025 at 8:36 AM Emelia S. <emelia@brandedcode.com> wrote:

> Okay, have it sending again, now on a VPS, but I did have to modify
> github-notify-ml for python 3.13, which is why the email didn't send at
> noon as expected.
>
> Hopefully next weekend it'll just "work"
>
> Improve debugging experience · Issue #86 · dontcallmedom/github-notify-ml
> <https://github.com/dontcallmedom/github-notify-ml/issues/86>
> github.com <https://github.com/dontcallmedom/github-notify-ml/issues/86>
> [image: apple-touch-icon-180x180-a80b8e11abe2.png]
> <https://github.com/dontcallmedom/github-notify-ml/issues/86>
> <https://github.com/dontcallmedom/github-notify-ml/issues/86>
>
> — Emelia
>
> On 2 Dec 2025, at 00:06, Emelia S. <emelia@brandedcode.com> wrote:
>
> Hi all,
>
> Okay, once again, GitHub broke the weekly summary bot, I'm working with a
> Fediverse host to migrate it from GitHub Actions to running on a VPS in
> their infrastructure using a cron job, so it should be more reliable and
> not break randomly.
>
> Apologies for the interruption to the service. There will be a note added
> to the readme with the details of the organization sponsoring the
> infrastructure for it (I didn't have the funds available to spend on a
> server just for this, and they could cheaply provision me a VPS).
>
> Yours,
> Emelia Smith
>
> On 31 Aug 2025, at 17:03, emelia <emelia@brandedcode.com> wrote:
>
> Hi all,
>
> To follow up on this, the failure this time was that I'd accidentally been
> using the public-swicg@w3c.org email addresses instead of
> public-swicg@w3.org
>
> This has now been fixed, and the weekly activity summary emails should
> happen as expected.
>
> Yours,
> Emelia Smith
>
> On 15 Aug 2025, at 16:02, emelia <emelia@brandedcode.com> wrote:
>
> Hi all,
>
> Just wanted to let you know that the reason we've not had the github
> activity summaries in a while isn't because nothing has been happening, but
> rather the emails were failing to send. I'm trying to investigate this, but
> I suspect it may be something on the W3C side blocking us again, even
> though we've communicated with the W3C about this sender and why it exists.
>
> The emails come from activitybot@socialcg.org <mailto:
> activitybot@socialcg.org> and are a summary of the events of that week on
> our various GitHub repos (the two official W3C ones, and the many taskforce
> ones on the swicg organisation). We're using the same tool that the W3C
> itself uses for sending activity emails, but unfortunately we can't use
> their instance as it's pretty locked down.
>
> The repo is here: https://github.com/swicg/activity-summary-bot/
>
> I'm not sure what next steps are for resolving this, but I am in contact
> with the email provider (mailgun) to try to gather the logs for the recent
> failures (though they seem to have very poor log retention).
>
> Yours,
> Emelia
>
>
>
>
>
>
>