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
> Code bases are on GitHub

Not a very solid way to move away from American big tech :/

>>WhyNot+EU
If the move away from American big tech is for practical reasons rather than political, there is no harm in using GitHub. The worry with using an American firm is that the US government could force the company to handover confidential information, or shut down access.

For open source code, there is no risk of confidential information being given to the US government (since there is no confidential information), and moving to another forge would be pretty simple if necessary.

>>cortes+i01
tbh I was always of the mind that Github offers nothing over some slight convenience in hosting and some exposure, in exchange for the loss of control

Github had enough mindshare that for a small dev operation it was a form of social networking on top of actual code revision control, and one could get the occasional PR worth looking at; this consideration has essentially gone away as the amount of unreviewed vibecoded slop has skyrocketed

I know I'm biased but I'd run my own git server

but you're right that security is of no object here if you're code is OSS in the first place

>>muyuu+AM3
What control do you lose with github that you want to maintain?

For any code you are sharing, I think you are underselling the hosting + sharing convenience. Everyone looks for projects on github, it is what people expect. Hosting it yourself requires managing user signups/accounts/permissions/etc.

>>cortes+v45
Well, if you're using it like it's supposed to be used, all of it is accessible by a third party and its availability depends on them. It will all be potentially scrapped (meaning it will be). You are essentially outsourcing the hosting as well, with its pros and cons. I'm heavily biased against that, so it's not only a github thing but a "cloud computing culture" thing. I only use other people's computer when using my own is a real problem or it's just not feasible.