In her keynote Julia will talk about public funding of open source technologies and why we need a European open technology fund.
A few years ago, Heartbleed epitomized a massive open source sustainability problem for critical parts of the internet infrastructure. The bug, which affected the popular OpenSSL cryptographic software library, notably compromised the confidentiality of 4.5 million US patient records and cost the industry an estimated $500M.
It was soon revealed that the root-cause of the issue was that OpenSSL was precariously understaffed. Open source sustainability became a major theme overnight. Stories of maintainer burn-out made the headlines. And tentative solutions started to emerge, most of them donation-based.
In this talk we’ll explore a number of existing strategies to fund open source and make it more sustainable, from patronage to dedicated ad networks. And we’ll defend the idea that the best path to open source sustainability is to help companies understand the tangible business value they can get from contributing to open source.
Since mid 2019 Digital Sovereignty has been promoted by the Government in Germany, for the most of us unexpectedly.
Behind the scenes economical motivations are driving the initiatives. Several new governmental agencies have been created, projects have been started on scale driving the administration to go digital, finally deliver a promise broken for at least twenty years.
The fear of loosing the industrial technology base to the US and Chinese cloud hyperscalers, conflicts with the US administration on political questions have created lots of activities.
Gaia-X and the Corona app are only the most prominent initiatives started directly by the German government.
The talk tries to give an overview what is going on, tries to give an estimation what will come next, how sustainable the initiatives are, where it makes sense to demand further steps.
Open source projects that are controlled by a single company are at a greater risk of changes that are not aligned with community interests, whereas projects that are under neutral foundations have a lower risk both for end users and software vendors. With advantages that include community building, innovation, and wider adoption, we should consider contributing more of our open source projects to neutral foundations.
This talk will cover:
- Challenges of giving up control and why it might be worth it.
- Selecting a foundation and how to determine neutrality.
- Creating a fair and neutral governance structure and processes for your project.
- Tips for contributing and maintaining your project.
The audience will get practical advice about whether they should contribute their projects to neutral foundations along with how and when to do it.
We all wish for the up and coming young generation to get thoroughly and completely immersed in the world of FOSS. They should eat, drink and breath it to become good and loyal members of the community.
But... many of them do not even know that FOSS exists. Their eyes never leave the smartphone screens and they dream of Microsoft Windows, Adobe Photoshop, Apple iPhone and Xbox. So how do we enlighten them? How to we let the everloving glow of FOSS reach in to their dark and dreary lives?
As a teacher in Web development for students who aim to become engineers ("Gymnasieingenjör i Mjukvaruutveckling"), I teach them how modern software development is steeped in FOSS philosophy and try to show them all the posibilitys that rise from the community. This is a short insight in how FOSS can (and should) be a big part of secondary education in Sweden.
Public Money, Public Code… but what are the best practices for public sector bodies to release new projects or share their own projects as FOSS? Why is it not "easy-peasy" (it certainly should be a "no-brainer")? Public sector bodies usually don’t have the staff with FOSS skills (certainly at management level, although they increasingly have developers who do, and are keen to embrace FOSS), they don’t have the time, and it is not a priority… even if there is a legal mandate. Two veteran open source lawyers present their experience in working with two public sector projects in the UK and Spain respectively, for publicly sharing code, with two totally different approaches looking for short term wins and long term sustainability. Governance? Contributions? Community Principles? High level inter-administration agreements? IP Management? Resources and funding? Navigating internal management?
You name, we have … no answers but maybe some hints that will help you work with local governments for freeing up public code.
Presentation describing the open source practices and initiatives being put in place at European Commission including the implementation of the new Open Source Strategy (announced in October 2020).
As a professor, I want to create open source startups with my doctoral (Ph.D.) students. To that end, I have set up courses and a whole program. Frankly, there is no better place than Germany to get started, as public funding can carry you through the research well into Series A territory. In this talk, I'll explain how I try to give my students their Ph.D. and help them turn their research work into a startup.
Our goal is to help people developing public-purpose software understand how the Standard for Public Code can help them collaborate. The Standard is of course applicable to everyone developing open source software, and is especially useful if you want other organizations to be able to contribute to your code.
By applying the Standard, code created for and by governments will not only be reusable and open source on paper, but also in practice. We hope to show that it is not that hard to create genuinely reusable code, and inspire collaboration across public organizations.
The talk will also answer the following questions:
- What is public code?
- Why the need for a Standard for Public Code?
The talk will show how the Foundation for Public Code is already applying the Standard to some codebases, and how this has helped those communities.
Governance is important, but unless you start out with a really clear vision, it might be hard to get everyone on the same page. People join projects at various times and when the project is small, governance is often not a top priority. Governance usually becomes a priority ex-post, or when a project is already in full implementation. So how do you get agreement and a common understanding on the governance of your codebase? If it wasn't already clear, chances are that people will have different views on what the status quo is. And if discussions are started based on different premises, misunderstandings are bound to happen. That is why we created the Governance Game. The Governance Game (https://github.com/publiccodenet/governance-game) is a fun way to explore how organisations can maintain shared and collaborative open content together. It can help you and your community to start talking about various aspects of governance, and highlight potential pitfalls. In this session we'll show you a few different ways of how you can use this game to enhance your project.