Repository navigation
2026/07/14/polly-osmf-announcement #1
Replies: 4 comments 4 replies
|
how can it be free and open when you have to pay money after a while, so if it is still in free and open license how do you enforce payment of the fee ??? so after looking a bit in the FAQ of the program it says
so does that mean the source code is free and open but binary releases are licensed under non-free licenses ?? it is the only way i can see this being enforced, where you do vscode like open core model and do propirety binary releases. also if the binary releases are identical to the build someone creates from the free and open licensed source code can you even enforce your non-free payment license since the binary is available with free and open license, is copyright even enforcable when almost same (or same if builds are bit by bit reprodicable as they should be see (https://reproducible-builds.org/docs/why/) ) binary is available under a free and open license also i would guess arguing about infra use could be hard to enforce too since nuget isnt run by the projects tho i am definitly not a lawyer so i would love to be enlightened about how exactly this can work while still being free and open while being forced to pay after some profit. tho dont get me wrong i think maintainers should be companseted but personaly i find strict copyleft + propriety license (like AGPL + license or QT like model for client libraries) more transparent where if you are in open source ecosystem you can still be sure to stay with free and open licenses all the way, and if you are corporate you can just pay for it. |
|
Because "free" in FOSS means "freedom" as in "free speech"--the freedom to download, modify, and redistribute the code, not free as in "free beer". Most, if not all, open-source licenses allow the maintainer to charge money for the product. For example, see the GNU FAQ: https://www.gnu.org/licenses/gpl-faq.html Copyleft licenses are not good for companies, because it requires they opensource their source code as well (that includes LGPL). Less restricted licenses like MIT, Apache2, and BSD3 are better suited for libraries. I support Joel in his decision. It takes time and money to maintain any project, but especially one like Polly. |
|
Will this only apply to future versions released after Nov 16? What if we are using an older package that we do not plan to upgrade? Will this retroactively affect our company? Our org supports and maintains previous versions of our software for a promised length of time. We do not introduce breaking changes in these versions. It would likely be a few hundred hours of dev to rip Polly out of these previous versions to avoid the fee. |
|
Just curious, what if I use Microsoft wrapper https://learn.microsoft.com/en-us/dotnet/core/resilience/?tabs=dotnet-cli will it also count and the org needs to pay? |
Uh oh!
There was an error while loading. Please reload this page.
2026/07/14/polly-osmf-announcement
News, releases, and deep dives from the team behind Polly, the .NET resilience and transient-fault-handling library.
https://thepollyproject.org/2026/07/14/polly-osmf-announcement.html
All reactions