On several occasions Here on the blog a topic has been touched upon, which For a long time it has been one of the major problems that faces the free software and its developers. He's the theme of the “financing”, which in turn leads to other problems, such as little or no support for projects, as well as abuse by commercial projects that use free software and do not allocate a portion of their profits or even contribute to the development of the project.
In order to provide a solution to this problem, The creator of WiX, has introduced an innovative initiative called “Maintenance Fee”.
Its goal is to solve one of the most persistent problems in the free software ecosystem: the funding of projects that, despite being widely used, depend almost exclusively on the volunteer work of their developers.
This proposal proposes the implementation of a small monthly contribution, with options starting at $10, intended to ensure the economic viability of projects without resorting to models like Open Core, which typically offer premium paid versions with additional features and limit access to certain functions.
Open source software is free, but maintaining an open source project isn't free. We demand a lot from project maintainers, including:
Triage problems
Answer questions
Keeping build scripts running
Update software dependencies
Follow-up safety reports
Produce new releases
Addressing spam on discussion forums and issue trackers
Maintaining the domain name registration
Renew signature certificates
And many, many other tasks
How the Maintenance Fee Works
The central idea is that users and companies that obtain commercial benefits (directly or indirectly) from an open source project make a regular contribution. Payment would be supported by an end-user license agreement (EULA), which would govern access to key resources such as project infrastructure, official binaries, and pre-compiled packages.
To facilitate transactions, The use of GitHub's sponsorship system is proposed, which would allow a direct transfer of funds to maintainers. This way, subscribers could download official versions, participate in technical discussions, and submit bug reports or feature requests.
One of the most relevant aspects is that Access to the source code would remain completely open, in accordance with the free licenses used. per project. However, companies that don't want to pay the monthly fee won't be able to use the official precompiled versions or integrate them as dependencies in managers like NPM or NuGet.
In practice, these organizations could still clone the repository and compile the software themselves, but without the right to use packages already prepared by the development team.
Combating maintainer burnout
The proposal arises as a response to a widely recognized reality: Open source project maintainers perform constant and demanding work without, in many cases, receiving any financial compensation. Many companies, despite basing entire products on these tools, fail to contribute either time or resources, creating an imbalance that leads to burnout, loss of motivation, and even project abandonment.
For the author of the initiative, This model is not a restriction, but a fair and balanced relationship: Companies that rely on third-party work spend a small portion of their revenue to ensure the tools they use can continue to develop.
With the implementation of the Maintenance Fee, Developers are expected to have more resources and time for essential tasks such as bug fixes, responding to user queries, updating dependencies, managing build infrastructure, detecting and remediating vulnerabilities, moderating communities, and renewing digital signature certificates.
Without a doubt, this proposal seeks to create a more fair, sustainable, and collaborative ecosystem, where open source is not synonymous with unpaid labor, but rather a shared effort between creators and users.
Finally, if you are interested in knowing more about it, you can consult the details in the following link