We all love FOSS. Lately, many of us have expressed their disarray at hearing stories of maintainers quitting due to a variety of factors. One of these is financial.
While donating to your favorite app developer is something many of you already do, the process can be tedious. We're running all sorts of software on our machines, and keeping an exhaustive list to divide donations to projects is somehow more effort than tinkering with arch btw™.
Furthermore, this tends to ignore library projects. Library maintainers have been all over FOSS-centered media rightly pointing out that their work is largely unnoticed and, you guessed it, undervalued.
What can we do about it? Under a recent Lemmy post, some have expressed support for the following idea:
Create a union of open source maintainers to collect donations and fairly redistribute them to members.
How would this work?
Client-side:
- You take some time to list the software you use and want to donate to
- You donate whatever amount you want for the whole
Server-side:
- Devs register their projects to the union while listing their dependencies
- A repartition table is defined by the relevant stakeholders. Models discussed below.
- When a user donates, the money is split according to the repartition table
How do we split the money? It could be:
- Money is split by project. A portion of donations go to maintainers of libraries used by the project.
- Money is split according to need. Some developers don't need donations because they are on company payroll. Some projects are already well-funded. Some devs are struggling while maintaining widely used libraries (looking at you core-js). Devs log their working time and get paid per hour in proportion of all donations.
- Any other scheme, as long as it is democratically decided by registered maintainers.
Think of it like a worldwide FOSS worker co-op. You "buy" software from the co-op and it decided what to do with the money.
We "only" need to get maintainers to know about the initiative, get on board and find a way to split the money fairly. I'm sure it will be easy to agree on a split, since any split of existing money will be more satisfactory than splitting non-existent money.
What are your thoughts on this? Would you as a maintainer register? Would you donate as a user? Would you join a collective effort to build this project? Let's discuss this proposition together and find a way to solve that problem so that FOSS can keep thriving!
That would be a nice option for web-based stuff. I guess the whole difficulty is to get a list of projects and to publicize it widely. I also believe donations should be stupid simple or they will never take off.
The main difference between your idea and mine lies in who decides where the money goes. I do not think end users should decide 100%, because that ignores a lot of critical under-the-hood software. Users must however have a completely transparent report of who gets what. I guess at that point they should be able to adjust it to their whims, which circles back to your point 1.
I think you can still have users decide which projects get funding and have the system/organization/smart contract/etc automatically distribute funds to the libraries those projects depend on. 80% to the project, 20% to the libraries, etc.
If we let devs decide which projects get funding, they're just going to always pick their own project. Since that doesn't align with what users want, users won't want to donate. If you want users to donate, you need to let them have some say in what their projects their donations go to.
Ideally you would let picky users override every setting and provide fair enough defaults. That includes library donation cascading etc. At the end of the day it seems the core part of the project should be providing fair enough defaults
It may not be only for web based stuff. The only things organization would need is the website and a bank account. Which is pretty standard these days.
We could have both systems. There should still be the default setting. I proposed the default distribution should be based on views. But the default setting could also be set by the community. This default distribution would also be used by the people who decide to favorize one project and give them 50% of their donation and leave the rest with the default distribution.
Also I believe it is crucial you can override the decision of this community. There will be bad decisions or decisions that you personally do not agree with. But because of that you should not give up on donations. You can simply pick your own, or blacklist one organization you do not agree with.
It is crucial indeed. That makes the project more of a central donation platform removed from the dev world, but it is simpler as such