Someday we'll get there, someday.
The moat on that is non existant.
If I'm working in software development, the last thing I want to do is trust my coding workflow to an alpha-state platform.
Im personally down to try alpha software usually, i just havent found the need to retrain all my muscle memory to not use GH yet, as much as I hate it's owned by microsoft nowadays.
They also do offer pretty good "free tier" services for CI via Actions that otherwise you'd need to pay yourself
Also, I moved about 10 repos to a private Forgejo installation with pretty average (non-trivial) GH actions workflows. Zero repos has workflows running oob (java, .net, node). The moat is a bit there.
A feature, not a bug. If I go to a website meant to distribute source repos (git, etc), I expect them to be FOSS. Also, the title mentions 'EU Open Sources [...]' so this is irrelevant to the topic at hand.
Either way, perfect is the enemy of good, and this is good. You can find hypocrisy or lack of perfectionism anywhere.
I guess if the github UI becomes critical to their continued development or PR then they expose themselves to a potential rug pull by github/microsoft.
I do not know much about the project so I can not tell if that is concern or if there is some other concern at play here or if those concerns apply to this project or not.
Those are the types of details I wanted to see in the comment.
e.g. Right now the UK grid is running on just over 80%+ renewable. But when the wind isn't cooperating french nuclear helps.
Broad reliance on renewables just doesn't work without interconnects across large geo regions
Yay, sustainability!
The repo linked “seeks to complement the tools currently used in the TYNDP cycles, especially for Scenario Building (SB) and Cost-Benefit Analysis (CBA). This approach is designed to enhance transparency and lower barriers to stakeholder participation in European energy planning. Beyond Europe, the project aspires to demonstrate the viability of open-source (OS) frameworks in energy planning, encouraging broader global adoption.
To build trust in and ensure reproducibility with the new open-source toolchain, the project first focuses on replicating key figures from the 2024 TYNDP cycle, before aligning with the current 2026 TYNDP cycle. This process involves developing new features within the open-source domain to address existing gaps, integrating tools for data interoperability and dynamic visualizations, and publishing best practices to encourage the adoption of open energy models.”
Why this report is shared appears to be an application of PyPSA for others to reference and become inspired by its implementation.
Why it’s open source I think is clear from the above paragraph. Open source standards make it drastically easier to harmonise and collaborate while allowing as much engagement as possible to scrutinise the framework.
What's the downside of open-sourcing this?
We should commend bureaucracies on the rare instance that they open-source their software, not ridicule them for it.
Let’s zoom in on your reply, the people who are interested and look at it and use it. What will they be able to do with it?
I think a good example is the Norwegian Meteorological Institute: https://github.com/metno (EEA, though, not real EU, but still)
It's not like all of it is useful for someone else, but it's the principle of it, and allowing people to see what their tax money (sometimes) goes to.