# Open Source Wishlist **URL:** \ **Category:** 📣 Sustainer Talk\ **Created:** [January 5, 2026, 10:36pm UTC](https://discourse.sustainoss.org/t/open-source-wishlist/1784 "2026-01-05T22:36:15Z")\ **Posts on this page:** 7\ **Page:** 1

**Author:** ![emmairwin](https://yyz2.discourse-cdn.com/flex032/user_avatar/discourse.sustainoss.org/emmairwin/32/443_2.png) [@emmairwin](https://discourse.sustainoss.org/u/emmairwin)\ **Post date:** [January 5, 2026, 10:36pm UTC](https://discourse.sustainoss.org/t/open-source-wishlist/1784/1 "2026-01-05T22:36:15Z")

Hi everyone! My name is Emma. For those I haven’t met before: I’ve spent 20+ years in open source at Benetech, Mozilla, and Microsoft’s OSPO including several years in education technology at Royal Roads University. After being laid off last year, I started **[Open Source Wishlist](https://oss-wishlist.com/)**, a project focused on making sustainability risk _visible, actionable with paid and attributed support._ This solves a few problems I have experienced as a **funder** : - Difficult to know, who and where in my dependencies sustainable risk is present and what type of risk it is - Impossible to know, what help would change that risk even if it’s clear - Impossible (unless specifically a grant program) to track impact of dollars on that risk As a community leader and **maintainer/community leader** , it solves problems I have experienced in that role as well: - How to ask for help in a way that resonates with funders - How to get human help in addition to funds (more new work, even paid mean I am stretched even further) - Compensation for my time mitigating risk that my users care about (even if working with another person its more time) Open Source Wishlist works this way: 1. Maintainers created a [wishlist](https://oss-wishlist.com/wishlists), from a pre-defined list of av[ailable resources and services](https://oss-wishlist.com/catalog) with known impact on sustainability. 2. Product teams and funders discover wishlists in their dependencies via the website, or [GitHub Action](https://oss-wishlist.com/dependency-action) (which uses SBOM and [Ecosyste.ms](https://ecosyste.ms/) to match wishes with projects). 3. We also proactively reach out to users of projects with wishlists to advocate for these one-time investments (increasing the chance of fullfillment) 4. Funders can fulfill one or more wishes on a wishlist, and indicate whether they would like to assign employee help, or pay one of our expert[open source practitioners](https://oss-wishlist.com/practitioners). 5. Fullfilled wishes are managed by a PM (me at the moment) to ensure milestones are met outcomes are measured (rubric). This helps funders a lot (showing impact means more budget). 6. Attribution for the wish is given to a person, company, or organization which will be part of a bigger effort around attribution in OSS ([blog post for context](https://sunnydeveloper.com/open-source-needs-an-attribution-standard/)). I am doing this on my own time right now (unpaid labor working on the unpaid labor problem :D) , but minimally want to show how this might work end to end to solve some of the problems I encountered. **[My goal (by the end of FOSDEM) is to obtain 200 wishlists from maintainers](https://oss-wishlist.com/).** Appreciate visibility to maintainer audiences who may want this type of support - once I have that 200, I will shift into 'get funding’ mode which I am most excited about. Note: I am working at the intersection of other projects like CycloneDX standard for sustainability, Open Source Economy, and others. No one does this on their own. In that light, we are also holding some[Open Source Practitioner calls](https://oss-wishlist.com/calendar)to explore touch points on things we all care about (independently of tech companies or products) - you are welcome to join the next one of course! ---

**Author:** ![abitrolly](https://yyz2.discourse-cdn.com/flex032/user_avatar/discourse.sustainoss.org/abitrolly/32/845_2.png) [@abitrolly](https://discourse.sustainoss.org/u/abitrolly)\ **Post date:** [January 11, 2026, 7:04pm UTC](https://discourse.sustainoss.org/t/open-source-wishlist/1784/2 "2026-01-11T19:04:45Z")

> [@emmairwin](#): > > unpaid labor working on the unpaid labor problem 😃 I understand that corporate way of looking at Open Source might be like this, but I treat Open Source code as an art. Not commercial art like Michelangelo paintings, but the idealistic itch to make things the way they should be done. Just what you’re doing with this project. For me the gameplay that starts with`unpaid labor`is not fun. It is like I am begging for money. Yes, I don’t have motivation to continue maintaining my projects, and money could solve me. Only if corporate knew what I need. Then they will be able to help me. I doubt that. They don’t. The consensus or agreement between people in commercial companies is that they all gather to earn money, not to spend them. The beauty of Open Source as an art is in the Eye of Beholder, and there are no beholders in corporate. If we want this kind of Open Source gameplay with money, we need to do market making for that. Wishlists? I don’t have one. Or maybe I do, but over years nobody bought anything from it including myself. Do wishlists work for streamers? If they do, they might work for Open Source too. But what is this “Open Source” - for me it is specific people I met, through commits, messages and in person. It is not something that corporate sees as a “risk”, but also as “unpaid labor”. If corporate could pay, they would hire Congnizant and other humongous “IT consulting” companies to just do things. And if we are lucky, there might be some people who maintain Open Source projects.. I am not saying you project is not going to work. I am just trying to explain my narrow point of how I see things work from here. ---

**Author:** ![emmairwin](https://yyz2.discourse-cdn.com/flex032/user_avatar/discourse.sustainoss.org/emmairwin/32/443_2.png) [@emmairwin](https://discourse.sustainoss.org/u/emmairwin)\ **Post date:** [January 11, 2026, 7:32pm UTC](https://discourse.sustainoss.org/t/open-source-wishlist/1784/3 "2026-01-11T19:32:49Z")

I don’t disagree with anything you’ve said. I’m a long time contributor and maintainer, open source communities are where I always go to be a part of something, and to give back. I spent a lot of years pleading for people to connect with and care about open source in the way communities do; as we do but it honestly never worked. What worked is drawing a line between what communities need, and what funders want to see. This is my attempt to see if we can make that easier. I don’t know if this will be successful, I’m not sure success is even my goal - rather it will teach us something. Maybe it will tell us - actually funders don’t care about leadership continuity, governance etc (even if xz proved they should), maybe it will show maintainers only want stable income and not help, or nothing at all -maybe companies will look at declared need as its own risk and have AI build an alternative (they have dollars, that’s not debatable). There’s only one way to find out. I only mention my unpaid status so people will know this comes from a sincere place of wanting to bridge the conversation. It’s not gameplay, at all. Best of luck to you, thanks for the note. ---

**Author:** ![abitrolly](https://yyz2.discourse-cdn.com/flex032/user_avatar/discourse.sustainoss.org/abitrolly/32/845_2.png) [@abitrolly](https://discourse.sustainoss.org/u/abitrolly)\ **Post date:** [January 12, 2026, 6:51am UTC](https://discourse.sustainoss.org/t/open-source-wishlist/1784/4 "2026-01-12T06:51:40Z")

> [@emmairwin](#): > > What worked is drawing a line between what communities need, and what funders want to see. This is my attempt to see if we can make that easier. Okay. Let’s see if we can strip that to bare bones. Because as a maintainer (and also as a funder on Gratipay/Liberapay and Gitcoin platforms) I couldn’t immediately see what is the final benefit for me. Maybe the design is targeted for corporates, and implies a bit of human touch to explain and introduce people doing their jobs to platform. That’s perfectly fine. However, for the individuals/hackers (who might be employed by the same company), it might be good to have a hatch to click through too. > [@emmairwin](#): > > Maybe it will tell us - actually funders don’t care about leadership continuity, governance etc (even if xz proved they should), maybe it will show maintainers only want stable income and not help, or nothing at all When I read words like “they should care”, I have a picture in my head that a corporate person always reply “of course we care”. Because what is a responsibility if they really don’t? Apologize maybe.. They only way I could see it can work is metrics. Company profile, listing its involvement on platforms like OpenCollective. A profile that will make me think if I want to join these guys, or more important - if as a government official I want to give this company contract, because the company amplifies the impact of Open Source, and the contract would do more good. For example, outsourcing company Epam made [https://opensourceindex.io/](https://opensourceindex.io/) Open Source Contributors Index, where it ranks enterprise commits under Open Source license. Forking and refactoring it can be a good start to get more human-centric metrics for funders vs maintainers gameplay. > [@emmairwin](#): > > I only mention my unpaid status so people will know this comes from a sincere place of wanting to bridge the conversation. It’s not gameplay, at all. I don’t use words like “politics” and “economics”, because they are generalized to the point of being useless. But I use “gameplay” to refer to specific activities that people do or could to do. Daily job, for example, is a gameplay of exchanging time to money, which is then enhanced by various mechanics (not always human friendly, but that’s how it works). People outplay any rules. They have their goals. Originally Economics was designed to watch and look what people do, but with time it became speculative media manipulative term. Now it is useless, but game design will never became old. > [@emmairwin](#): > > maybe companies will look at declared need as its own risk and have AI build an alternative I would say AI is quite mature today to be included in the loop too. 👍 Somebody just need to ask the models - who wants to participate? 😁 Thanks for your effort. Even if it is a long road, I seriously think it might be a step in the right direction. ---

**Author:** ![wolftune](https://yyz2.discourse-cdn.com/flex032/user_avatar/discourse.sustainoss.org/wolftune/32/1091_2.png) [@wolftune](https://discourse.sustainoss.org/u/wolftune)\ **Post date:** [January 12, 2026, 12:59pm UTC](https://discourse.sustainoss.org/t/open-source-wishlist/1784/5 "2026-01-12T12:59:05Z")

I suggest you listen to the latest podcast from the Center for Humane Technology: > **[What Would It Take to Actually Trust Each Other? The Game Theory Dilemma](https://www.humanetech.com/podcast/what-would-it-take-to-actually-trust-each-other-the-game-theory-dilemma)** > > We're a nonprofit exposing the negative effects of persuasive technology and social media and empowering people to take action. Discover The Social Dilemma, our podcast, course, and more. Key framing is that game-theory _itself_ is a _paradigm_ with all sorts of unhealthy features, and we do _not_ need to accept it, we _can_ have different paradigms. game-design is a real thing of course, but we don’t need to use that framing to see the world, and it is limiting in its own ways, just as it is to see everything as economics or politics. ---

**Author:** ![emmairwin](https://yyz2.discourse-cdn.com/flex032/user_avatar/discourse.sustainoss.org/emmairwin/32/443_2.png) [@emmairwin](https://discourse.sustainoss.org/u/emmairwin)\ **Post date:** [January 12, 2026, 6:09pm UTC](https://discourse.sustainoss.org/t/open-source-wishlist/1784/6 "2026-01-12T18:09:33Z")

> [@abitrolly](#): > > When I read words like “they should care”, I have a picture in my head that a corporate person always reply “of course we care” You’re right “they should care” is weak framing, because everyone says they care. It’s like DEI a few years back: ‘everyone said they cared’, but now we can see who actually meant it based on who’s still doing the work. So let me reframe: drawing a line between risk, need and the ‘[service](https://oss-wishlist.com/catalog)’ to resolve both doesn’t make funders _care_ it helps answer “how does this help me”: - show which products/services of theirs would be impacted by risk/need (it could hurt me or my customers!) via dependency tree/SBOM - show which services, [\* with (options for) expert paid humans can fix](https://oss-wishlist.com/practitioners)it, and how we will know its fixed/rubric (I can tell my boss, that I helped our product/service be more reliable/secure etc for our customers) - Brand recognition (take the pressure of our company as an OSS user, by showing we’re helping) There’s a whole other host of reasons people fund projects (directly or via foundations), and I wouldn’t describe those as ‘caring’ either. What I would say FOR SURE, is there are l **ots and lots of people working in companies, and as funders who DO authentically and personally CARE** (a lot) and giving them the tools to advocate is really a gap that I experienced. I would have really loved something like this to take to budget-holders (and why I built this)). My goal again for FOSDEM is 200 wishes, if I achieve that - I will engage with funders/companies/individuals - if not then that’s its own signal, and I will park it (leave up, but not actively run). Again, I see it as a chance to learn (and already am, thanks again). ---

**Author:** ![lina](https://avatars.discourse-cdn.com/v4/letter/l/bb73d2/32.png) [@lina](https://discourse.sustainoss.org/u/lina)\ **Post date:** [January 21, 2026, 6:58am UTC](https://discourse.sustainoss.org/t/open-source-wishlist/1784/7 "2026-01-21T06:58:02Z")

That’s right—businesses don’t “care”; they react to real risks, effects, and brand visibility. It is clear how OSS funding helps both sides when you use SBOMs/dependency trees and get help from an expert if you want it. Add a contribution dashboard and suddenly funders see the return on investment and security impact, while maintainers see recognition and stability. a lot more useful than appealing to “care.”