zlacker

>>AareyB+(OP)
Worth pointing out: France is not adopting existing open source software, they're building their own software and releasing it under the MIT licence. Most of it (or all of it?) is Django backend + React frontend (using a custom-built UI kit).

Home page for the entire suite (in French) with some screenshots: https://lasuite.numerique.gouv.fr/

Code bases are on GitHub and they use English there: https://github.com/suitenumerique/

Dev handbook (in English): https://suitenumerique.gitbook.io/handbook

Not French and I can't say I personally tried deploying any of them, but I've been admiring their efforts from afar for a while now.

>>input_+1F
I work at Grist, the "tableur collaboratif" (collaborative spreadsheet) listed on the La Suite homepage. We're in the interesting situation of being both a NYC-based company, and open source software the French gov has adopted and is helping to develop. Grist is mostly a node backend. So it is a complicated story. The key is having code the gov can review and trust and run it on sovereign infrastructure.

Grist https://www.getgrist.com/

A write-up of how the French gov uses it https://interoperable-europe.ec.europa.eu/collection/open-so...

>>paulfi+wM
Your position is fantastic because it immediately puts to death all of that nationalistic nonsense about the EU becoming "anti-American" by enforcing privacy laws on US Big Tech etc, when in fact they are just protecting their citizens' rights against unethical business models regardless of origin. I might be naive, but your company to me represents a win for free/open software and cross-country collaboration.

That being said, I should ask: to what extent do you see being US-based an advantage or a problem in the current state of things? For example, in regards to exports controls, or any other such thing that may potentially limit your business scope depending on $current_admin.