4 ms·

> It isn't clear what restrictions will be allowed and still qualify as a "Fair Source" license We called that out on the website though: Fair Source Software

> It isn't clear what restrictions will be allowed and still qualify as a "Fair Source" license We called that out on the website though: Fair Source Software (FSS): * is publicly available to read; * allows use, modification, and redistribution with minimal restrictions to protect the producer’s business model; and * undergoes delayed Open Source publication (DOSP). The delayed open source publication part is explicit.

ezekg 2y ago
In addition, underneath the definition, we touch on that even more: > The intention is for the first point to be a bright line, and for the second to invite exploration. We expect Fair Source licenses to emerge and evolve and shake out into a few clear winners over time, as companies apply Fair Source within their own particular business context. The third point is also intended as a bright line, and a key differentiator of Fair Source from Open Core and other approaches. The key line is to "invite exploration."
- ensignavenger 2y ago
  Thank you for pointing that out, I did a quick read through of that part and missed the intention behind it. I also found the Readme which helps explain the direction things are going. (https://github.com/fairsource/fair.io/blob/main/README.md https://github.com/fairsource/fair.io/blob/main/README.md)
ensignavenger 2y ago
"minimal restrictions to protect the producer’s business model" That isn't very clear to me. Does every license author or licensor get to decide for themselves whether or not a license is Fair Source, or whether or not a limitation is "minimal"? Honestly, I don't think the limitations in the Functional Source License are "minimal". But others clearly believe they are. The delayed part is explicit... but could a license that delays release to open source for 1,000 years be considered "fair source"? It is a DOSP as you say? I understand that the Fair Source branding movement is still young and is likely evolving policies and procedures, but those are some of the questions I already see coming up when discussing whether or not a license is Fair Source. It may take a while for the definition to mature.
- the_mitsuhiko 2y ago
  And it's important that we have these conversations. I would however like to understand why you believe the limitations on the FSL are too strict and what exactly they prevent which you believe they should not.
  - ensignavenger 2y ago
    Lets say there is an FSL licensed SaaS app. And that the company behind it offers two tiers, a lower monthly fee that is "self service" with no integration assistance, and a higher monthly fee with a long contract term that offers integration assistance. I decide I want to self host the product. I reach out to the company about integration assistance. They tell me they don't provide any support for the self hosted product and aren't interested in providing me with integration assistance if I don't use their hosted version. Now, I decide to hire a local contractor I know to help me integrate the self hosted version. They don't touch the code or do anything with it, they just work on integrating it into my existing business stack. Now, the SaaS company offers a competing product and service- the hosted SaaS with integration assistance. Is my contractor violating the license by offering a a service that substitutes for the service offered by the SaaS company? I think many such SaaS companies would be fine with it, it wasn't a job they were interested in... but it rides up against the license really closely. And there are many variations of this scenario that could play out that could easily cross the line. (Perhaps SaaS company puts in a bid to do the work, but I decide a local contractor I have used many times in the past and is thus familiar with my stack and what they would be integrating would be better, or maybe the contractor does have to make changes to the FSL licensed code in order to make it work with something I need. Those things can be negotiated and clarified, but generally only if you know they are an issue up front. If business needs change after you have adopted the software, you are in a tough negotiating spot. One big benefit to the well worn and simple permissive open source licenses is simply knowing very early what exactly I can and can't do. The FSL is trying to get as close to this as possible, but it is inherently more complicated that "take this code and use it, just credit me and don't expect any warranty from me, oh, and by the way, if you want my help I offer my service for $$$ so reach out" style open source licenses (not all open source licenses are simple like that, though).

ezekg 2y ago

In addition, underneath the definition, we touch on that even more: > The intention is for the first point to be a bright line, and for the second to invite exploration. We expect Fair Source licenses to emerge and evolve and shake out into a few clear winners over time, as companies apply Fair Source within their own particular business context. The third point is also intended as a bright line, and a key differentiator of Fair Source from Open Core and other approaches. The key line is to "invite exploration."

ensignavenger 2y ago
Thank you for pointing that out, I did a quick read through of that part and missed the intention behind it. I also found the Readme which helps explain the direction things are going. (https://github.com/fairsource/fair.io/blob/main/README.md https://github.com/fairsource/fair.io/blob/main/README.md)

ensignavenger 2y ago

"minimal restrictions to protect the producer’s business model" That isn't very clear to me. Does every license author or licensor get to decide for themselves whether or not a license is Fair Source, or whether or not a limitation is "minimal"? Honestly, I don't think the limitations in the Functional Source License are "minimal". But others clearly believe they are. The delayed part is explicit... but could a license that delays release to open source for 1,000 years be considered "fair source"? It is a DOSP as you say? I understand that the Fair Source branding movement is still young and is likely evolving policies and procedures, but those are some of the questions I already see coming up when discussing whether or not a license is Fair Source. It may take a while for the definition to mature.

the_mitsuhiko 2y ago
And it's important that we have these conversations. I would however like to understand why you believe the limitations on the FSL are too strict and what exactly they prevent which you believe they should not.
- ensignavenger 2y ago
  Lets say there is an FSL licensed SaaS app. And that the company behind it offers two tiers, a lower monthly fee that is "self service" with no integration assistance, and a higher monthly fee with a long contract term that offers integration assistance. I decide I want to self host the product. I reach out to the company about integration assistance. They tell me they don't provide any support for the self hosted product and aren't interested in providing me with integration assistance if I don't use their hosted version. Now, I decide to hire a local contractor I know to help me integrate the self hosted version. They don't touch the code or do anything with it, they just work on integrating it into my existing business stack. Now, the SaaS company offers a competing product and service- the hosted SaaS with integration assistance. Is my contractor violating the license by offering a a service that substitutes for the service offered by the SaaS company? I think many such SaaS companies would be fine with it, it wasn't a job they were interested in... but it rides up against the license really closely. And there are many variations of this scenario that could play out that could easily cross the line. (Perhaps SaaS company puts in a bid to do the work, but I decide a local contractor I have used many times in the past and is thus familiar with my stack and what they would be integrating would be better, or maybe the contractor does have to make changes to the FSL licensed code in order to make it work with something I need. Those things can be negotiated and clarified, but generally only if you know they are an issue up front. If business needs change after you have adopted the software, you are in a tough negotiating spot. One big benefit to the well worn and simple permissive open source licenses is simply knowing very early what exactly I can and can't do. The FSL is trying to get as close to this as possible, but it is inherently more complicated that "take this code and use it, just credit me and don't expect any warranty from me, oh, and by the way, if you want my help I offer my service for $$$ so reach out" style open source licenses (not all open source licenses are simple like that, though).