OpenSource.net

If you're here at the #OSSummit in Amsterdam, I'm on a panel with Ruth Ikegah, Leslie Hawthorn, and Stephen Walli about educating the next generation of open source project contributors at 11:20: https://sched.co/25Vmi I hope you'll join us! I'll be around all week, so you can also find me if you want some CHAOSS / OpenUK stickers, and I have a few earrings!

Excited to have the opportunity to speak at OSPOs for Europe, a Brussels-based event hosted by Dirk Schrödter, Minister and Head of the State Chancellery of Schleswig-Holstein. I will go into the depths and breadths on how Europe can grow Digital sovereignty through open source, and leverage the strategic opportunity it provides. Also looking forward to hearing the success stories on how this is achieved in practice:  * The digital workplace of the future – Schleswig-Holstein's path to greater sovereignty by Sven Thomsen, CIO SH * Bridging Borders with X-Road: Open Source for Seamless Public Data Exchange by Ville Sirviö, the CEO of NIIS * Open Source, Open Voices: How Decidim Enables Transparent Citizen Engagement by Marta Anducas, President of the Decidim Association Registration @ https://lnkd.in/dfappTCs

A welcome addition to Open Source Initiative (OSI)'s list of supporters and a recognition of the valuable work being done by our team.

Our latest in the #AI orchestration series demonstrates how #jBPM integrates AI-powered features into a clinical setting. See it in action with #OpenEMR for stroke prediction.

My friend Konstantin Vinogradov is launching something new — an Open Source Endowment (OSE), a US-based nonprofit that will fund open-source work that silently powers the world. I've joined in. Maybe you should, too 🤷🏻 Over the last 12 months, I have reached out to several tech companies worth billions/trillions — ones that use my open-source code in production — to explore more sustainable options for working on open-source projects. On one hand, some top AI labs had offered me 8-digit contracts to work on their internal infrastructure. On the other hand, I was asking for just $20,000–$50,000 from each of 5-10 organizations to help maintain the code they already use in production. I thought it would be a no-brainer. But everyone politely passed. Moreover, the cognitive load of those conversations was very distracting from the actual R&D. Individual efforts didn't scale. And built-in features, like "GitHub Sponsors", don't work either. A more organized approach is needed! An endowment? Conveniently, the contributions don't have to be huge. Countless developers I know would pay $200/month or $2,000/year for each of their LLM subscriptions for coding. The output of those LLMs is very emotionally supportive for me when debugging complex issues, but from a practical perspective, 90% of LLM-generated code is an ugly & broken mess, 5% is a pure replica of somebody else's open-source work, and 5% involves novel interpolation between (again!) existing public examples. With such a weak baseline, many techies should be open to donating $1,000 per year. With a million individuals, even excluding corporate donations, that's a total of $1 billion — enough to pay 5,000 developers $200,000 per year. Almost double the headcount of OpenAI. A sizable budget that can make a huge difference. Dreamy, but not impossible! My preference lies with the forgotten art of building compact low-level infrastructure projects, such as the Tiny C Compiler, OpenBLAS, and JeMalloc. The current draft of the distribution plan doesn't fully align with such preferences, but it's a good start, and I'd love to see this succeed! There are already some other amazing people involved, including Chad Whitacre (Sentry), Maxim Konovalov (NGINX), and Jonathan Starr (NumFocus). OSE is also advised by Amy Parker, CFRE (OpenSSL Foundation, former Wikimedia) and Vlad-Stefan Harbuz (Open Source Pledge). What other names do you think should be on that list? https://endowment.dev https://lnkd.in/gQ8NHjTA

🚀 Just launched: maintaine.rs—Unveiling the Open Source heroes that power our digital infrastructure The maintaine.rs book is a curated collection of 50+ stories from top #opensource #maintainers. Maintainers not only write code, review issues, and merge pull requests—they also navigate community dynamics, mentor new contributors, and increasingly adopt security best practices to protect their code and users. They literally keep the digital infrastructure up and running for the benefit of all. Download the book and discover the passion, challenges, and insights behind the code that powers the world. https://maintaine.rs/

Building MCP servers the easy way with Apache OpenServerless

Final part of our series on #jBPM and #AI: This time, we dive into integrating AI-powered features in a clinical setting, demonstrating stroke prediction with OpenEMR. Details here:

Orchestrating AI in clinical settings with jBPM