apt-get

Worth noting the vote for this law passed 11 to 10, and it's an amendment to the budget which is 100% likely to be thrown out anyway.

World Wide Web, huh?

Those hyperlinks ain't free, you know.

Location: Paris, France

Remote: Yes

Willing to relocate: No

Technologies: End-to-end Devops/SRE -- general POSIX sysadmin stuff, modern systemd slash linux, Docker/Podman/Virtualization/etc, CI/CD (mostly Gitlab), managing different kinds of private software forges & repositories, DB clusters (Postgresql & co.), observability (Grafana stack), everything k8s. Software Engineering -- Python, Web Stack (I enjoy both Vue & SvelteKit), Java (Spring and its ecosystem), Ruby + Clojure + Rust as hobby occupations. (+ AI)

Languages: FR / EN

Résumé/CV: Available on request.

Email: see profile.

I'm a swiss knife software engineer, with 5 years of professional experience and 15 years of handling computers and code in general. My dayjob's developing tools to better manage public infrastructure, which has given me the opportunity to grind my gears against a lot of obtuse edge cases between legacy systems, deploying software in weird environments, and doing all that on a shoestring maintenance budget!

I've got the chops to run all the internal tooling a dev team might need -- software forge and repository, private container repos, bare-metal servers for VM provisioning, company VPNs, authentication systems, etc. I've also done a lot of (proper) k8s work, setting up CI pipelines, GitOps continuous deployment (ArgoCD), configuring (and testing) high availability modes for required middlewares, developed my own k8s controllers when the need arose, etc. Most importantly, I know when to use the right tool for the job, and when the extra complexity isn't actually needed.

I've also done a lot of proper software engineering, with a focus on distributed & fault-tolerant systems, RBAC, multitenant support, performance optimization, and integrating software bricks together that were never meant to match! I love thinking about the boundary between systems and making sure no important information is ever lost or slips through the cracks. This includes a rather paranoid cybersecurity mindset as well.

I'm looking to work freelance a few hours a week with someone who needs that kind of help (either on the weekend or on CET evenings), preferably in an ethical context; I'd love to work with nonprofits and the likes. I'm probably cheaper than you think! Don't hesitate to contact me if you're interested.

I'm referring to telecom cables in nordic and baltic waters, not nordstream.

> One thing that logic would dictate though is that Russia would be extremely low on the list of suspects since they gain nothing and are negatively affected in every manner possible by being in any way behind such actions.

Or one could choose not to take this in isolation from all the acts of brazen and identified sabotage Russia does, slashing deep-sea cables in international waters with their shadow fleets, organizing psyop campaigns throughout the entire continent that can be traced back right to their government units, and so on :-)

Not asserting this is definitely a Russian op (given the amount of simultaneous farmers' protests and all in NL today), but their modus operandi for foreign operations of this kind involves paying random thugs a few hundred to a couple thousand euros to carry out acts of sabotage using whatever items they have on hand. The items don't need to match, the people involved don't need to know each other.

Worth noting that the "escape hatch" clauses in the EUPL that allow converting it into other licenses mean it's only ever as strong as the weakest license it names for such an operation, AKA EPL/MPL/LGPL.

Any actor that wants to mess around with providing a closed extension on a network service can exercise that option with an EUPL codebase, so if you care about that, you're better off explicitly naming the AGPL or whatnot.

EUPL is built for government agencies first, and most of the focus is ensuring that nobody has to worry about mix-and-matching it with other copyleft licenses, plus legal language that covers and harmonizes variations in notions of copyright/patents/intellectual property across EU countries, not so much waging war against hyperscalers. (But it's still great to have around!)