XSF Communications Team - 2026-02-01

whoa didn't know you use github. I can't comment there as I don't have an account (and never will as I don't agree with their ToS). It's a shame not to lead by example here into self-hosting and decentralization

> whoa didn't know you use github. I can't comment there as I don't have an account (and never will as I don't agree with their ToS). It's a shame not to lead by example here into self-hosting and decentralization You are probably right. Though, we cannot put the effort to migrate our setup incl. all automation. ↺

Just writing down random thoughts on that self hosting question since it's a question that interests me, not looking to necessarily start a lengthy debate. There's fossil scm as an alternative, a pretty good all in one solution with a built in evented http server, and embedded database (ofc SQLite). It's easier to use in general, ideal for small to medium projects (but not the linux kernel). I wonder what it'd take to integrate fossil and XMPP. It already has a JSON interface (that was chosen over making a libfossil because that would have been too hard), maybe its chat and forum could connect to an XMPP bot. I had already customized fossil to have special tickets for a project that didn't pan out (I turned it into project management for a planned book). I don't know about hooks though, never made one for fossil. It can export to git too and so in theory stay in sync with a readonly github.

Évelyne: did you use Fossil cgi extensions for your customization? There has been previous interest in migrating the XMPP wiki which is hosted by the XSF, so Fossil could be a solution that does not require too much extra maintenance work.

> You are probably right. Though, we cannot put the effort to migrate our setup incl. all automation. classic boiling frog vendor lock-in situation. gotta rip that band-aid sooner or later ↺

Benson: no I wrote some SQL to configure the ticketing system. I think I had html & CSS customization in there too. I did use the wiki a bit too, with its custom markup.

Would you be interested in working on implementing XMPP support?

I was actually looking for an xmpp project to better understand the whole ecosystem (looking at slixmpp's doc helped). Don't know how complex this one would be though, it'd have to be studied more seriously.

Évelyne, Benson: is this the right space for your discussion?

>> You are probably right. Though, we cannot put the effort to migrate our setup incl. all automation. > classic boiling frog vendor lock-in situation. gotta rip that band-aid sooner or later No, classic resource management challenges. ↺

Évelyne: There is interest in migrating the XMPP wiki - but there are stakeholders who would need to explain what would be needed for them to adopt a new system. There is quite a lot in the ecosystem. Some people implement specific XEPs for their needs rather than use a library. For the wiki, there is a muc iteam@muc.xmpp.org For XMPP development there is jdev@muc.xmpp.org and project@joinjabber.org

Benson: thanks, i'll go there and see how things are going in that space!

Benson, I think the second one should be xmpp:future@chat.jabboratory.org?join for discussing XMPP development ✏

It used to be on joinjabber.org but shifted recently if I'm not wrong

There is also the main XSF room of course where we seem to be discussing quite a bit of development too xmpp:xsf@muc.xmpp.org?join

thanks badrihippo (btw jabboratory seems down atm, unless they just ban every autonomous system that also hosts VPSes, like my ISP does)

Works for me

https://piaille.fr/@movim/115995086519172472

edhelas: needs more DI.DAY!

Here we go with more DI.DAY

*XMPP listed as Alternative Chat at DI.DAY Initiative* The German initiative ‘Digital Independence Day’ (DI.DAY) has been kicked off this year to enable users to migrate to open-source software alternatives in various contexts. Besides other services, XMPP is listed as an alternative chat option and XMPP Community members have created so-called switch recipes: Digital Independence Day. https://xmpp.org/2026/02/xmpp-listed-as-alternative-chat-at-di.day-initiative/ https://mov.im/community/news.xmpp.org/News/1742b25f-dd56-4660-8654-82b8e87f0ed9 https://fosstodon.org/@xmpp/115995087036901844 https://bsky.app/profile/did:plc:hhyjgh7zxk33uavujv6hypm3/post/3mds7ep2grn22

Thanks to everyone who worked on the printed news leaflet, it was a success!

Yes!