An interesting problem! :) I have no idea how to do this but since there is a chance to migrate to gitlab, I think we should wait for things to clear out.

Is there tracking bug for gitlab migration? :)

Me and my big mouth :)

Stelios is working on that. No ticket as far as i know.

I believe this issue relates not to the OS we develop, but instead to the infrastructure we use for developing it - and therefore should instead be tracked at https://code.puri.sm/Purism/Systems-Tasks

At least in the past, we tracked all infrastructure stuff in public here as well (except for concrete machine requests), so I think having this issue here makes sense.

It' here:

https://code.puri.sm/Purism/Systems-Tasks/issues/58

In T375#6988, @theodotos.andreou wrote:

https://code.puri.sm/Purism/Systems-Tasks/issues/58

That 404s for me?

Sorry @chris.lamb. Gogs silliness. You need to be added as a collaborator to see it. Can you check now?

Ah, it's on code.puri.sm. Getcha. Wfm now!

This is now here: https://source.puri.sm/Purism/Systems-Tasks/issues/58

@chris.lamb Gives me an error 404...

@mak You'll have to ping the sysadmins for access … sorry.

Hi, any update for this? It's been many months and I would still dearly love this feature.

It's on my todo list and will likely be added after the current refactoring is over. The tricky thing here is that Laniakea delegates most archive actions to dak, and I would need to hook into dak to make this feature work properly (which means without email parsing) and integrate it with the generic Laniakea messaging.
This feature will also require our sysadmins to allow bots in some way on our Matrix instance (at the moment, I have no way to actually register a Matrix bot).

How far away do you think we are with this? I'm sure it would be a total boon for implicit communications within the PureOS team, @jeremiah.foster :)

Gentle ping on this?

@chris.lamb For the Laniakea changes, I now put my own status-tracking document into the repository, so it is more obvious on why making such a change takes so long: https://github.com/lkorigin/laniakea/blob/master/docs/porting-status.md#status
I won't extend the existing codebase much (except for bugfixes) and instead just work on the new component versions for now, which unfortunately means very slow progress for a while.
As for the room itself, I can't comment on that, that's sysadmin business.

I now put my own status-tracking document into the repository

Thanks and is appreciated but I think this off-topic for this issue (which is to show changes/updates that have happened, not for the longer-term / future planning...)

@chris.lamb Ah, so you just want Git commit updates? That's a way easier thing to do, I assumed you wanted notifications about any archive changes and bugtracker changes.

(Oh, I want that too but the page you linked is a high-level and textual status tracking document.)

I fear this issue will soon reach its 1 year anniversary. :(

There is an RSS bot that reposts Purism blog posts in the #community-general:talk.puri.sm room. I'm afraid I don't have any details, and the person that implemented it is away. But if you can generate RSS output that might be a start!

FWIW this has inspired me to get https://source.puri.sm/liberty.atom showing up in Matrix somewhere. Low priority for our team, but I'll come back to this ticket if/when we succeed.