I maintain many open source projects on GitHub and elsewhere (over 160 as of this writing). I have merged and/or closed thousands of Pull Requests (PRs) and patches in the past few years, and would like to summarize here many of the reasons I don't merge many PRs. A few of my projects have co-maintainers, but most are just me. The bus factor is low, but I offset that by granting very open licenses and encouraging forks. I also devote a set amount of time (averaging 5-10 hours/week) to my OSS project maintenance, and have a personal budget of around $1,000/year to devote to infrastructure to support my projects (that's more than most for-profit companies who use my projects devote to OSS, sadly).
The Missing Middle of Open Source
Why serious, maintainer-driven projects struggle to sustain themselves—and what it will take to fix it.
Keep Your Friends Close — Open Tech Strategies | Blog
One of the insider secrets of free and open source software (FOSS) is that most of the rules a project uses on a day-to-day basis are not found in the software’s license. There are contribution guidelines, which are enforced by the project only taking contributions that meet them. There are codes of conduct, which are a condition of community participation. There are endorsements, official membership, a voice in setting the project roadmap, and all kinds of other benefits that attach to varying types of community participation. In each case, entirely external to the license, there are official rules and unwritten norms that govern how participants gain the benefits of joining the civic life of a project.
Sustainable Open Source: The Maintainers Perspective or: How I Learned to Stop Caring and Love Open Source
How to set up a new Programme | The Commons Conservancy
So you are responsible for some ‘free and open’ project or effort that is in the public interest. This could be free software/open source, open hardware, open science, open content, etcetera. With open, we mean that you are sharing not just the final end result as something immutable, but you’ve made it part of the ‘Commons’ by explicitly allowing anyone to build and extend on what you’ve created. In legal terms this is normally done through a ’license’, and each incremental author actually needs to license his or her part. However, once different people start contributing, managing who can license what becomes cumbersome - especially if you need to make upgrades to a license. Mix in the need to collectively raise funds for promotion, development and maintenance, and you’ve just experienced why people that are involved with larger projects sometimes feel victim to their own success. None of this matters when a project is young, but as soon as it is about to outgrow the original creator it becomes urgent - there is a window of opportunity for quick and effective repair which slowly starts to close once you’ve passed a certain scale, The critical fase of scale up is where we aim to help out.
What it feels like to be an open-source maintainer
Outside your door stands a line of a few hundred people. They are patiently waiting for you to answer their questions, complaints, pull requests, and feature requests. You want to help all of them,…
What it feels like to be an open-source maintainer
Outside your door stands a line of a few hundred people. They are patiently waiting for you to answer their questions, complaints, pull requests, and feature requests. You want to help all of them,…
Open Source Maintainers Owe You Nothing
This post is heavily inspired by my experience over the last ten years participating in the open source community and eight years as a maintainer of Homebrew (which I’ve maintained longer than anyone else at this point).
Open Source Maintainers Owe You Nothing
This post is heavily inspired by my experience over the last ten years participating in the open source community and eight years as a maintainer of Homebrew (which I’ve maintained longer than anyone else at this point).
The struggles of an open source maintainer - <antirez>
The Rise of Open Source Challengers
A look at how OSS takes over the application layer + the potential end of closed source software categories
A plan for open source software maintainers
It seems to me that this is a case where problems are in fact solutions to other problems. To wit:
Reimagining OSS Licensing and Commercialization with Fair Source - Adam Jacob, System Initiative
Professional maintainers: a wake-up call
Open Source software runs the Internet, and by extension the economy. This is an undisputed fact about reality in 2021. And yet, the role of Open Source maintainer has failed to mature from a hobby into a proper profession.
It's time to pay the maintainers
Or, what Voltron can teach us about improving open source development.
Balancing Makers and Takers to scale and sustain Open Source
To scale and sustain Open Source ecosystems in a more efficient and fair manner, Open Source projects need to embrace new governance, coordination and incentive models.
