LibreOffice release builds should offer to send a crash report. Ideally, you should then create a bug report referencing the crash report. Besides that, you can do your own build with debug symbols and get backtraces or debug the program.

At The Document Foundation we are always interested in helping deployments. It is also nice to do writeups for our blog. Let me know, if your organisation needs help: [email protected]

I recommend to consider our certification program: https://www.documentfoundation.org/certification-program/

I asked about the Maven artifacts and our release engineer will update them later this week.

I think if we're to move to away from these US products to open source ones, then governments should also provide resources or funding to develop them using the licensing fees they save. Is the Danish government contributing back to libreoffice?

> sometimes libreoffice crashes and you can't figure out why > why libreoffice stopped publishing artefacts to mvn repo

I think both questions would be a perfect fit for the paid support bugtracker of LibreOffice maintainers. Hopefully paid by some hospital funds that are not spent on MS Office licenses.

Switching from Word/Excel to LibreOffice is comparably easy. A lot of other Microsoft Products are much harder to get rid of.

I've never seen a European corporation that doesn't do user management with ActiveDirectory. Some still have it on their own Windows servers, but most browser based applications still go through Entra (Azure Cloud based AD). Just shut off their Entra/AAD and most of their software is blocked because nobody can log in.

> But I don't think they will be switching away from Teams as quickly.

I'm interested to know why Teams is so sticky for the team. Are there not good replacements available? I've used it a little, but am by no means a power user.