Replies: 2 comments 4 replies
-
|
@Meir017 my understanding is that in the case of the OSMF EULA it only applies to the projects explicitly taking the dependency (so in this case it would potentially apply to Aspire itself) and not down-level consumers. Here is that point being made by @robmen (the creator of the license) himself: https://www.reddit.com/r/dotnet/comments/1ql41jb/comment/o1ir7h5/ |
Beta Was this translation helpful? Give feedback.
-
|
Also, I wouldn't say that JsonPatch.Net is "going commercial". Unlike many other solutions, under the Open Source Maintenance Fee (OSMF), the license of the JsonPatch.Net project remains the same: MIT. It's still a fully Open Source project; source code access, modification, and redistribution rights are unchanged. The OSMF EULA applies only a small fee for using the binary releases to support its sustainability. The term "going commercial" implies a loss of freedom that has not occurred. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
aspire/src/Aspire.Hosting/Aspire.Hosting.csproj
Line 55 in 3f15281
See https://www.reddit.com/r/dotnet/comments/1ql41jb/jsoneverything_to_start_charging_a_maintainance/
My concern here is that aspire itself is completely open-source, but users of aspire will be getting the JsonPatch.Net dependency, and many users of aspire are building internal apps for profit
Beta Was this translation helpful? Give feedback.
All reactions