Re:Is It Even Worth Working on FOSS Anymore?
by McWobbleston on Friday December 24, 2021 @10:35AM
(#29674408)
It's fun to see someone else describe the tokens for votes model. I've been working on my first 3D game trying to think of how I would support it if it's OSS while giving players direct input about the direction and what's implemented. Definitely a pipe dream for me right now but I'm really hoping I can manage to get to a state where that's a problem I have and people to collaborate with on solving
Re:Is It Even Worth Working on FOSS Anymore?
by rs999gti on Friday December 24, 2021 @10:25AM
(#29674314)
> Criticism aside, how does one provide freedom to learn and explore while curtailing the free rider problem?
Make FOSS free for individuals. Developers can download, read, integrate, etc. the code or package for free at home on their personal PCs.
The moment FOSS software enters the corporate or academic space, it becomes a licensed product requiring fees and statements of work to be paid for licensing, use, and changes.
However, there is another axis to consider: In English, "free" also means gratis. This means that no one with recognized authority is enforcing a shift of resources in exchange for using the code as written. Yes, you can ask for resources, and there are many ways to do so, but without enforcement, you get the most common behavior of "thank you, I will" and all the attendant problems, be that of pushing the license to limits, finding loopholes, to lack of funding, dead projects, to (possibly) self-interested actors placing features in open source that they can later exploit because no one really audits the code (See also log4j. I am not saying that a government placed something exploitable in the code. I am not saying that a private actor did so. I am saying it is interesting that a piece of widely used infrastructure has had an exploitable feature for so long).
Criticism aside, how does one provide freedom to learn and explore while curtailing the free rider problem?
A first-generation solution: Sell copies of your source code for the resources you need to maintain it. One example would be to make the source available once money has changed hands. You cannot stop the buyer from turning around and giving the source away for free: Once you have made a sale, you have made a sale. That particular copy of your source has created all the profit it will create.
A second-generation solution: Sell future updates. This is an idea I have been playing with, in terms of a business plan. Your source is free (both gratis and freedom) and you sell tokens. The tokens are capable of being purchased separately. Tokens can be exchanged for votes to determine which new features are developed and which bugs are fixed. They key is in selling the tokens.