







binding a philosophy to oss projects
smol machines — ship and run software with isolation by default
Run any workload in a fast, hardware-isolated Linux VM. The same SDK and the same .smolmachine artifact run identically:
Nominate OSS for Funding — Open Source Endowment
Nominate critical, underfunded open source projects for OSE grant funding through our open, community-developed model.


The Philosophy of Open Source in Community and Enterprise Software
Open Source Initiative (OSI) Logo The idea behind open source software is a simple one. Developers decide to make the source c...

Reimagining OSS Licensing and Commercialization with Fair Source - Adam Jacob, System Initiative
“Open Source” Is Nobody’s Property
if OSI owned it, they wouldn’t be so touchy about it

Histomat of F/OSS: We should reclaim LLMs, not reject them
A few days ago, I came across a blog post titled On FLOSS and training LLMs that articulates a growing frustration within the free and open source software…
smol farm
smol farm is an independent entertainment studio making books, games and apps. Home of Xorientation, Four Corners and more.


The Community Corrosive Effects of CLAs | James Bottomley's random Pages
As one of the kernel DCO advocates, I’ve written many times about using the DCO instead of a CLA for copyright and patent contributions under open source licences. In spite of my obvious biases, I’ll try to give a factual overview of the cases for the DCO and CLA system. First, it should be noted that both the DCO and any CLA are types of Contribution Agreements (a set of terms by which contributors are agreeing to be bound). It should also be acknowledged that the DCO is a far more recent invention than CLAs. The DCO was first pioneered by the Linux kernel in 2004 (having been designed by Diane Peters, then of OSDL) and was subsequently adopted by a broad range of open source projects. However, in legal terms, the DCO is much less well understood than a standard CLA type agreement between the contributor and some entity, which is largely the reason you find a number of lawyers still advocating for the use of CLAs in various open source projects: because they’d like to stick with something that has more miles on it, or because they’re invested in the older model of community, largely pioneered by Apache. The biggest problem today is that the operation of most CLAs is asymmetrical: they take from the contributor more rights than the open source code actually needs, so lets begin with a summary of each type of Contribution Agreement.
Something Big Happened in 1998
It is reasonable to accept that OSI founded Open Source with the Open Source Definition.

A Revised “Ostrom’s Design Principles for Collective...
A Revised “Ostrom’s Design Principles for Collective Governance of the Commons” The traditional economic definition of “the commons” are those resources...
Open Source is Broken
The Open Source movement, as championed by the OSI, prizes absolute openness above all other concerns...

Open Source is Broken
The Open Source movement, as championed by the OSI, prizes absolute openness above all other concerns...

A Practical Framework for Applying Ostrom’s Principles to Data Commons Governance
How do stakeholders govern themselves? What drives their endeavour? How do they make decisions? How do they make sure conflict does not tear them apart? The answers to these questions will look different for every data commons. Learn more in this week's data governance blog.

The just-announced Open Source Endowment is now on Bluesky, and we're open to your ideas on how to identify critical OSS projects 🙏
Open Source Endowment
We heard the Bluesky community cares about Open Source, so we showed up 👋 Our endowment dedicated to supporting Open Source maintainers is already at $729k, and we're developing a model for distributing our first funding round. Have ideas on how to identify critical OSS projects? We're listening.