I don't see how EU can develop a thriving software industry with its love for control and regulation.
I think this was disused a few days ago in a similar HN comment thread. Turns out, the US has way more data-tapping anti-privacy laws than the EU - only that the US more or less secretly adopted them and forbids any company from telling their end-users. Whereas you hear more about "data regulation-attempts" in the EU because it actually still has very strong privacy-rules and when trying to alter them there is a real…
European Commission issues call for evidence on open source
41–50 of 380 posts
Re: European Commission issues call for evidence on open source
#42https://ec.europa.eu/newsroom/dae/redirection/document/11798...
The document is also known as "The “Open Source Way to EU Digital Sovereignty & Competitiveness” thematic roadmap".
Earlier discussion (in French): https://linuxfr.org/news/la-commission-europeenne-publie-une...
---
Here is the complete list of proposals from the roadmap, translated into English and organised by pillar.
### Pillar 1: Technological Development
- Define technical specifications as open standards for European Open Source cloud, edge and IoT environments.
- Fund interoperability pilot projects that prioritise the use of European Open Source technologies.
- Require all EU-funded digital infrastructure projects to adhere to these interoperability standards.
- Promote and enforce the implementation of open standards throughout the EU.
- Create a ‘European Open Source Sovereignty Fund’ (EOSSF) dedicated to essential projects. [NB: this would now be called the EU-STF].
- Offer targeted grants for the security, maintenance and strengthening of the sovereignty of Open Source projects.
- Foster in-depth collaboration with European academic institutions and Open Source Programme Offices (OSPOs).
- Develop a practical guide for public procurement managers to evaluate European Open Source solutions.
- Create sector-specific reference architectures based on European Open Source technologies.
- Launch large-scale demonstration projects to illustrate the practical benefits of European Open Source solutions.
- Produce and distribute comprehensive ‘playbooks’ for the deployment of European Open Source solutions.
- Implement policies to actively encourage the adoption of these reference implementations in public procurement.
### Pillar 2: Skills Development
- Organise industry-focused training workshops with a European emphasis on Open Source tools and platforms.
- Offer targeted training grants to SMEs and public sector organisations for European Open Source skills development.
- Launch certification programmes for mastery of European Open Source technologies and standards.
- Establish EU-funded retraining programmes to help professionals transition into European Open Source roles.
- Collaborate with industry partners to create hands-on learning and placement opportunities in Open Source.
- Offer financial incentives to companies that participate in retraining programmes and use European Open Source.
- Develop a European Open Source resource platform that brings together training materials, best practices, and case studies.
- Integrate European Open Source principles into STEM (Science, Technology, Engineering, and Mathematics) curricula from secondary school to university.
- Support the creation of European Open Source ‘centres of excellence’ in universities.
- Develop EU-wide coding competitions and hackathons focused on European Open Source solutions.
- Introduce training on European Open Source business models into vocational training.
- Create vocational training modules for European Open Source project management.
- Establish certification for mastery of European Open Source business skills.
### Pillar 3: Public Procurement Practices
- Launch a consultation with public sector bodies and Open Source providers to identify challenges related to public procurement.
- Make ‘Public Money, Public Code, Open Source First, European Preference’ policies mandatory in public procurement.
- Develop comprehensive guidelines for public procurement to evaluate and select European Open Source solutions.
- Fund demonstration projects showing the success of replacing proprietary systems with European Open Source.
- Establish clear criteria for defining what constitutes a ‘European’ Open Source solution.
- Provide a practical guide for public procurement managers to evaluate Open Source solutions.
- Collaborate with industry and standardisation bodies to develop accessible evaluation criteria for Open Source.
- Create a public directory of recommended European Open Source solutions.
- Encourage public sector organisations to adopt solutions developed under the Next Generation Internet (NGI) initiative.
- Launch cross-border pre-commercial procurement (PCP) projects focused on European Open Source.
- Create knowledge-sharing platforms for feedback on PCP initiatives and Open Source best practices.
- Actively involve European Open Source providers in the co-design of solutions in the PCP process.
- Publish guidelines to help public sector organisations manage and support European Open Source.
- Promote the active participation of public sector representatives in European Open Source communities.
- Support training programmes for public sector staff on project management and Open Source compliance.
- Engage stakeholders to collaboratively refine and simplify procurement practices for Open Source.
### Pillar 4: Growth and Investment
- Create a European Open Source Investment Platform (EOSIP) to centralise information on funding.
- Organise information workshops for European SMEs and start-ups on how to obtain investment.
- Establish partnerships with private investors to form a network of venture capital funds focused on European Open Source.
- Expand the Next Generation Internet (NGI) initiative with a focus on Open Source cloud, edge and IoT.
- Regularly assess the impact of funding programmes on community growth and market adoption.
- Allocate dedicated funding to high-impact European Open Source projects that meet strategic needs.
- Develop co-investment models that combine public funds with European private sector investments.
- Launch accelerators and incubators specifically designed for European Open Source technologies.
- Develop an EU-wide branding strategy to highlight the quality and sovereignty of European Open Source.
- Showcase European Open Source successes on international platforms through marketing campaigns.
- Form strategic partnerships with European industry organisations to increase project visibility.
- Establish public-private R&D consortia on European Open Source for high-priority projects.
- Offer incentives for private sector contributions to critical European Open Source initiatives.
- Develop platforms for knowledge exchange and cross-sector collaboration within the European ecosystem.
### Pillar 5: Governance
- Conduct vulnerability assessments for critical European Open Source projects.
- Collaborate with European cybersecurity agencies to develop threat models for Open Source environments.
- Publish findings and best practices from security assessments to the European ecosystem.
- Offer tailored compliance advice to help European Open Source projects navigate EU regulations.
- Facilitate accessibility to Cyber Resilience Act (CRA) certification for European Open Source projects.
- Provide resources and support for the documentation and auditing of European projects.
- Ensure stable, long-term funding for core European Open Source infrastructure.
- Establish mentoring programmes focused on developing European talent for critical projects.
- Create a European Open Source Advisory Board to oversee project funding and direction.
- Require EU-supported European projects to adhere to transparent governance and accountability practices.
- Support European community involvement in Open Source project governance.
- Facilitate community input into European Open Source policy development.
- Publish guidelines on best practices for managing the lifecycle of European Open Source projects.
- Provide resources for responsible maintenance and end-of-life support for European projects.
- Encourage comprehensive documentation and knowledge sharing within the European ecosystem.
Re: European Commission issues call for evidence on open source
#43Earlier quoted context omitted.
Just because it's free? Let's talk again when all open source projects are funded and controlled by the state with zero competition between them and no consumer choice. Only one Linux distro, only one database, only one web framework, etc. And it's decided top-down from the state what to work on. I doubt though that these projects would have started in the first place in a communist setting.
There is no reason such a state would have to set things up this way. As an example: you probably know that germany has socialized healthcare. It is, however, not implemented as a single-payer model. Instead there are tons of different insurances competing with each other, while having a highly regulated floor of what they MUST offer. Is the model perfect? Hell no, it has tons of issues - though overall it's pretty s…
Re: European Commission issues call for evidence on open source
#44Europe does not need more open source, it needs its own healthy and competitive software industry. It doesn't matter if the email platform a government uses is open source, but it should be able to pick a local alternative. It does not matter if the e-ID or payments app is running on an open source mobile OS, but it should be possible to run it on a non-US one. Policy may help the European software industry, at least…
Because it struggles to compete with the US monopolies doesn't mean that it doesn't have a software industry. It's hard to compete with TooBigTech when they are being anti-competitive, and whenever the EU tries to apply antitrust laws, they get bullied by the US.
> It does not matter if the e-ID or payments app is running on an open source mobile OS, but it should be possible to run it on a non-US one.
I don't think they are talking about creating a mobile OS? But I do think that e-ID and similar government apps should be open source, so that people can trust them.
> Open source may be one of the options, but it is not the right model for all types of software.
Agreed, it does not necessarily have to be open source. But my opinion is that if the taxpayer's money is used to pay for software, then that software should be open source.
Re: European Commission issues call for evidence on open source
#45Earlier quoted context omitted.
"The" state, with no competition, like there's only one state? Belgium isn't big enough to realistically have its own linux, but France and Germany are.
Of course it's big enough. Why would it not be big enough??
Re: European Commission issues call for evidence on open source
#46Earlier quoted context omitted.
> software that is funded by public means, such as from universities or institutions, ought to be made fully public, including ability to tweak Anyone who agrees with this should sign this petition made by Free Software Foundation Europe: https://publiccode.eu
While I agree with the sentiment I'm not sure this is actually viable. For example here in Poland the previous govt invested in huge amount of software for digital govt services. From company formation, social insurance/heathcare (things like electronic prescriptions and patient data) to tax submission at all levels. All of this is implemented using publicly documented open standards so anyone can write a client for…
Re: European Commission issues call for evidence on open source
#47Earlier quoted context omitted.
"The" state, with no competition, like there's only one state? Belgium isn't big enough to realistically have its own linux, but France and Germany are.
North Korea has its own Linux. Google has its own Linux. There are Linux distributions maintained by a single person. Belgium will do fine.
The hypothetical specifically precludes that.
Re: European Commission issues call for evidence on open source
#48We'll see how it goes this time. If they once again go for creating their own forks, instead of financing development of existing software then I'll know the initiative failed. Also imho their 'questions' mentioned in the comment kinda feel like they have answer baked in - like it's foregone conclusion. Still - I hope EU will just have a decent program financing or contributing in any shape or form to development of…
I think at this point we're beyond that, we already have these programs and they seem to be expanding. EU-STF is one such example, then there are other organizations supported by the EU in various ways, that also helps fund OSS, like NLnet Foundation.
Re: European Commission issues call for evidence on open source
#49Earlier quoted context omitted.
Codeberg and Forjeo have a foundation in Germany
There was a grant in 2023 which was supported by the European Comission. So I think the topic itself isn't entirely unknown. https://nlnet.nl/project/Forgejo/
> We are seeking project proposals between 5.000 and 50.000 euro's — which should get you on your way.
Am I the only one to think this is completely ridiculous amount of money?
So, you want me to leave my very well paid job to innovate for the sake of EU competitiveness but you don't to invest more than 50k EUR (max grant). And as an individual you don't even stand a chance so this 50k EUR has to be distributed across several people. Did I get this right?
Ah, and I almost forgot about the double standards ... the same EU commission is on a spending spree when it comes to the development of a fkn EU website which you use to apply for these funds. Each Brussels-based developer doing that very innovative work is paid ~100k EUR. What a blasphemy.
Re: European Commission issues call for evidence on open source
#50Earlier quoted context omitted.
> software that is funded by public means, such as from universities or institutions, ought to be made fully public, including ability to tweak Anyone who agrees with this should sign this petition made by Free Software Foundation Europe: https://publiccode.eu
While I agree with the sentiment I'm not sure this is actually viable. For example here in Poland the previous govt invested in huge amount of software for digital govt services. From company formation, social insurance/heathcare (things like electronic prescriptions and patient data) to tax submission at all levels. All of this is implemented using publicly documented open standards so anyone can write a client for…
The government - and taxpayers - should care that having closed-source software means they are tied to the company that wrote it forever, so changes and bugfixes will be much more expensive.