OpenStreetMap’s Post

At Open Source Summit events tend not to allow much time for detailed talks, and the 2025 Open Source Summit Europe did not diverge from that pattern. Even so, Daniel Stenberg, the maintainer of the curl project, managed to cram a lot into the 15 minutes given to him. Like the maintainers of many other projects, Stenberg is feeling some stress, and the problems appear to be getting worse over time. Curl, he began, is "a small project with a big impact". It began in 1996 with all of 100 lines of code; it has since grown to 180,000 lines that have been contributed by 1,400 authors. In any given month, there are 20-25 developers who are actively contributing to curl. The project has exactly one full-time employee — that being Stenberg himself. The program is widely used, having been deployed in at least one-billion devices. Just about anything that occasionally connects to the net, he said, uses curl to do it. But using curl is different from supporting its development. As an example, he put up a slide listing the 47 car brands that use curl in their products; he followed it with a slide listing the brands that contribute to curl. The second slide, needless to say, was empty. https://lnkd.in/dbYg34Dk

A great collaboration with GRNET - Greek Research & Technology Network. Thank you, Themis Zamani, Kostas Koumantaros, and your team for an impressive effort, making a more resilient ecosystem for software source code archival. This effort was funded through an EU project, FAIRCORE4EOSC, and required internal effort from the Software Heritage team, hosted by Inria & Fondation Inria. Deploying a Mirror is not a simple task - this achievement is a second step towards a robust mirror network. Read more about it in the blog post.

Such a informative and enlightening talk from Lilian T.! 

"Use channels that are shared by all trusted committers and potential contributors, that are archived, searchable and linkable for decision making" - what sounds trivial in theory often is very scary in practise. In this talk you will learn why shared async communication channels are vital to make cross team collaboration work, what that means for documentation accruing over time and why async communication alone cannot replace trust building based on personal relationships.

🌍 85% of organizations gained increased influence in open source ecosystems due to their OSPO. From shaping community standards to driving collaboration, OSPOs are amplifying organizational impact. 1 - Do you have an OSPO dedicated to open source community engagement?  2 - Do you prevent proprietary code from leaking out into open source projects? 📊 See all the trends in The 2025 State of OSPOs and Open Source Management Report:   👉 Download the full report - https://lnkd.in/gnhBH5AC

🔀 F is for Forks in open source. Forking might sound like a small technical detail, but it’s one of the most powerful features of the OSS ecosystem. A fork can: Spark innovation (LibreOffice from OpenOffice) Respond to community disagreements (MariaDB from MySQL) Ensure preservation of critical software (think abandoned projects kept alive by their users) But it’s not all upside. Forks split communities, increase maintenance burdens, and require real leadership to succeed. In our latest ABCs of OSS post, we break down: 👉 What forking means in open source 👉 Why projects fork in the first place 👉 The famous forks that shaped the software we use today Watch the full video here: https://lnkd.in/g-p2JDVk What’s the most memorable open source fork you’ve seen?

💡 Did you know the open-source community hit 1 billion contributions in 2024? According to GitHub’s Octoverse 2024 report (as covered by The New Stack), these contributions include code commits, pull requests, and issues across millions of public repositories worldwide. Contributions are growing not only in traditional open-source projects but also in public repositories without a license accepted by the Open Source Initiative, showing a huge global collaboration effort. Open source is more than just code – it’s a vibrant ecosystem where developers share knowledge, fix bugs together, and drive innovation across industries. Hossted is proud to be part of this thriving ecosystem, enhancing open-source software with enterprise-grade support and security. Check the comments for the full article. #OpenSource #Community #Innovation #Hossted #Security #Support #GitHub

Excited to announce the official launch of the Universal DID-Native Addressing (UDNA) Community Group at the W3C! As the newly-elected Chair, I'm thrilled to lead this effort to develop a standard for native addressing of #Decentralized Identifiers (DIDs). This work is crucial for enabling the seamless integration of DIDs into the broader web ecosystem. Our collaboration has begun, and all our work will be happening publicly. You can find our main specification, issue tracking, and all our progress in the new GitHub repository: https://lnkd.in/gRQSwCiZ We invite and encourage anyone interested in decentralized identity and web standards to join us. Your contributions—whether through issues, pull requests, or discussions—are vital to our success. Let's build the future of decentralized identity together! #W3C #DID #UDNA #GitHub #OpenSource #Standards #DecentralizedIdentity #WebStandards

For developers seeking alternatives to US-based tech platforms, check out Tangled - a promising Github alternative. Why Tangled: - Open source - Built on decentralized ATProto - Hosted in EU - Alternative: self-hosting I've recently moved my mcpkg project to Tangled 😊 Check it out: https://lnkd.in/dh-EJ3iQ

𝗢𝗽𝗲𝗻 𝗦𝗼𝘂𝗿𝗰𝗲 𝗕𝗲𝘆𝗼𝗻𝗱 𝘁𝗵𝗲 𝗟𝗶𝗰𝗲𝗻𝘀𝗲: 𝗪𝗵𝘆 𝗘𝘂𝗿𝗼𝗽𝗲 𝗠𝘂𝘀𝘁 𝗟𝗲𝗮𝗿𝗻 𝗳𝗿𝗼𝗺 𝗖𝗵𝗶𝗻𝗮’𝘀 𝗦𝘁𝗿𝗮𝘁𝗲𝗴𝗶𝗰 𝗔𝗽𝗽𝗿𝗼𝗮𝗰𝗵 The open source movement has transformed software development, but its future hinges on more than just licenses. As Jos Poortvliet argues, true open source demands transparency, active community participation, and sustainable funding. Too often, governments and corporations treat open source as a free resource, consuming its benefits without contributing back—a practice that undermines the very projects they depend on. China offers a compelling alternative. With strong government backing and massive investments in projects like OpenHarmony and OpenEuler, China leverages open source as a strategic asset for technological sovereignty. European policymakers and industry leaders should take note. The continent has the talent and values to lead in open source, but only if it shifts from passive consumption to active stewardship. 𝗞𝗲𝘆 𝗟𝗲𝘀𝘀𝗼𝗻𝘀 𝗳𝗼𝗿 𝗘𝘂𝗿𝗼𝗽𝗲: - 𝗙𝗿𝗼𝗺 𝗖𝗼𝗻𝘀𝘂𝗺𝗽𝘁𝗶𝗼𝗻 𝘁𝗼 𝗖𝗼𝗻𝘁𝗿𝗶𝗯𝘂𝘁𝗶𝗼𝗻: Procurement policies must require vendors to give back—whether through code, documentation, or funding. - 𝗜𝗻𝘃𝗲𝘀𝘁 𝗶𝗻 𝗢𝗽𝗲𝗻 𝗦𝗼𝘂𝗿𝗰𝗲 𝗮𝘀 𝗣𝘂𝗯𝗹𝗶𝗰 𝗜𝗻𝗳𝗿𝗮𝘀𝘁𝗿𝘂𝗰𝘁𝘂𝗿𝗲: Establish Open Source Program Offices (OSPOs) and fund critical projects directly, following Germany’s example. - 𝗣𝗿𝗶𝗼𝗿𝗶𝘁𝗶𝘇𝗲 𝗗𝗶𝗴𝗶𝘁𝗮𝗹 𝗦𝗼𝘃𝗲𝗿𝗲𝗶𝗴𝗻𝘁𝘆: Switching from proprietary software isn’t enough. Training, community engagement, and long-term support are essential to avoid repeating failures like Munich’s LiMux project. Open source is not a zero-sum game. It flourishes when all stakeholders—developers, businesses, and public institutions—act as custodians. Europe’s choice is clear: build a sustainable, equitable open source ecosystem or risk ceding ground to those who do. The time to act is now. Let’s create a future where open source is truly open, collaborative, and resilient. https://lnkd.in/eqPkTt4n