







Software can be rebuilt, because software is a machine. But a software ecosystem is not a machine. It is a living system.
Regenerative Software - The Phoenix Architecture
Your platform is not an ecosystem
Another day, another exhortation to join an “ecosystem” that’s anything but. I could pick a hundred examples, but one that recently caught my eye was an ad placed in the Financial Times by the Singapore stock exchange, SGX Group, promising “multiple growth avenues, one trusted ecosystem”. SGX wants companies to list on its exchange rather than, say, the Hong Kong one which has more or less the same exclusive offer. SGX promises “access (to) Asia through our trusted ecosystem anchored in Singapore.” Ecosystems can be a lot of things. ‘Trusted’, by which they mean centrally policed to achieve defined, lower-risk outcomes, is not one of them. Calling built environments ‘ecosystems’ is common everywhere from financial services to supply chains to – quite a stretch, here – a retirement living complex. But it’s most often used in the tech world to describe the relations between software, services and hardware typically owned by a single company. For example, it’s how Google describes everything that hangs off the Android operating system. These kinds of proprietary and deterministic architectures are called ecosystems so often that we’ve stopped noticing. And that’s kind of the point. We need to start seeing this metaphor again, and what it’s hiding in plain sight. But first, a reminder of what an ecosystem actually is.
What Happens to Relicensed Open Source Projects and Their Forks? - Slashdot
A Linux Foundation project focused on understanding the health of the open source community just studied the outcomes for three projects that switched to "more restrictive" licenses and then faced community forks. The data science director for the project — known as Community Health Analytic...

No Fork Required - Scott's Thoughts
What if another operating system isn't the solution to anything at all? What if device-level identity could tie into existing systems to help pull users out of walled gardens, rather than creating new gardens?
Fork it! It's time for a Mastodon hard fork (UPDATED)
An opportunity to improve safety, the Mastodon ecosystem, and fediverse software development

Sustainable software manifesto
The systems we build are never neutral. They can magnify harm or support a just and sustainable society. How we build today shapes tomorrow’s possibilities.

Designing and Programming Malleable Software
User needs for software features and interfaces are diverse and changing, motivating the goal of making it as easy as possible for users themselves to change software, or to have it changed on their behalf in response to their developing needs. However, in my opinion, current approaches do not address this issue adequately: software engineering promotes flexible code, but in practice this does not help end-users effect change in their software. End-user and live programming systems help users customize their interfaces by accessing and modifying the underlying source code. I take a different approach, seeking to maximize the kinds of modifications that can take place through regular interactions, e.g. direct manipulation of interface elements. I call this approach malleable software. To understand contemporary needs for and barriers to modifying software, I study how it is produced, maintained, adopted, and appropriated in a network of communities working with biodiversity data. I find that the mode of software production, i.e. the technologies and economic relations that produce software, is biased towards centralized, one-size-fits-all systems. This leads me to propose a long-term, interdisciplinary research program in reforming the tools of software development to create infrastructures for plurality. These tools should help multiple communities collaborate without forcing them to consolidate around identical interfaces or data representations. Malleable software is one such infrastructure, in which interactive systems are dynamic constellations of interfaces, devices, and programs assembled at the site of use. My technological contribution is a reconstruction of the programming mechanisms used to create interactive behavior. I generalize existing control structures for interaction as entanglements, and develop a higher-order control structure, entanglers, which produces entanglements when particular pre-conditions, called co-occurrences, are met. Entanglers cause interactions to be assembled dynamically as system components come and go. I develop these mechanisms in Tangler, a prototype environment for building malleable interactive software. I demonstrate how Tangler supports malleability through a set of benchmark cases illustrating how users can modify systems by themselves or with programmer assistance. This thesis is an early step towards a paradigm for programming and designing malleable software that can keep up with human diversity.
Sustaining Open Source Software
The ‘open source sustainability’ debate continues with yet-another-company relicensing their product away from an open source license to…

Changing Devtools Is Cheap. Owning Them Isn’t.
AI makes devtools cheap to customize, but personalized forks still demand ongoing attention and ownership.



Ecosystem Mapping — Open Tech Strategies | Blog
All the power of open source comes from throwing in with your neighbors, even the neighbors you don't like very much. For most projects, the main reason to get involved in open source is to create productive relations with as many participants as possible, including rivals. Doing this well requires understanding who is in your ecosystem and how they relate to each other.
Explore
Discover independently developed software reimplementations. Everything can be remade.

We need Sustainable Free and Open Source Communities
Sustainable Free and Open Source software is not about business models, it’s about building sustainable communities.

code and tests aren't the moat. they never were. no need for agents to copy a project. forking was always an option. the moat of an oss project is its community, its governance, and its ecosystem connections. agents will never be able to replicate that. don't hide. let's build in the open, together
Why does every platform rebuild the same safety tools from scratch, behind closed doors? Our Head of Product @julietshen.bsky.social joined the Won't Fix pod to talk open-source T&S infrastructure, AI vs. human judgment & safety for the decentralized web: youtube.com/watch?v=RxFV7VwxkLs
Won't Fix Episode 9: With Juliet Shen, Cofounder & HOP at ROOST
www.youtube.com