Building a bridge over hungry monsters for open source sustainability
Launching next week: Open Source Wishlist
Every open source security incident teaches us something new; but more often than not we are reminded of past lessons. Projects and maintainers need help, succession plans, modern security practices, trusted governance as well as moderation and funding strategies. Minimally.
Despite years of experiments and well-intentioned initiatives, most maintainers of critical projects still receive little or no sustained support, leaving them to shoulder enormous responsibility in their personal time. Open Infrastructure is not Free - a Joint Statement on Open Source Sustainability
Although projects and funders would both nod their heads in agreement - that solving these problems for sustainability are worthy and achievable goals, that's where the conversation hits a wall. There is no standard and discoverable way for projects to ask for support, and even then, there's no standard way to evaluate the success of such interventions making funders uncertain (educated guesses).
It sometimes feels like projects and funders are on opposite sides of a canyon filled with hungry (bad actor) monsters, each side unsure how to bridge the distance, each desperately wanting to. Monsters ready to eat us all.

Enter the Open Source Wishlist
I mentioned that there is no standard way to ask for and measure impact of sustainability support, but there are a lot of established best practices, metrics, resources and people who can bridge that canyon. There is a way to operationalize sustainability support in a way that's highly visible, built on those standards, NOT dependent on any one foundation or company; one which provides not only funds to maintainers, but actual human help from established open source practitioners
Really!

Catalogue of services and resources (Open Source Wishlist catalogue!)

- Project maintainers choose from set of known 'sustainability' levers as 'wishes'. These are 'services' like Governance and moderation strategy but also resources like Infrastructure.
- Those wishes are discoverable by 'Wishlist Sponsors' in a few different ways including a analysis of their SBOM and through the dependency FUNDING.yml.
- Wishlist sponsors can fund one or more of those wishes.
- Open source practitioners (paid or pro-bono) are dispatched to help maintainers implement the wish according to a rubric for success.
- Sponsor reports are generated based on the rubric score, and crossed off the wishlist
- Sponsors can report back on 'impact' (that wish will no longer in their dependencies).
Launching as a pilot next week!
This project has been a creative outlet for me as I recovered from layoffs, and find new inspiration. It is entirely open source, open content and volunteer - run. Contributions to format, content, playbooks will all be warmly welcomed. We will have up to 10 practitioners for the first pilot and as many maintainer wishes as we can muster.
Thanks to everyone, especially Christos Bacharakis who has taken time to give to contribute their ideas, insights and support. If you are interested in being part of the pilot either as a maintainer, sponsor or practitioner please get in touch at info at oss-wishlist.com .