[James_K]

Yeah, but my point is that they are the typical example. They are a company who wants to release their software to give users a peek inside without opening it up to competition. Hence they invented a license to let them do that, and provide the additional guarantee that users can service the software themselves if Sentry ever stops supporting it (after two years). Their motivation is literally the exact thing that motivates every other source available company. If anything, the FSL is closer than the BSL to the platonic ideal of a source available license.

EDIT: having read through the two licenses, I'm actually convinced that the FSL might be less permissive than the BSL in its intended use-cases. The BSL effectively becomes open source whenever owner stops providing the software commercially (rather than 2 years after) which guarantees that there will never be a time where the service is unavailable (if I'm interpreting it correctly). BSL includes a provision saying that a product is defined as competing based on the date of its release, rather than FSL which might allow the licencor to release new services that make someone else's retroactively competitive. It also isn't clear about free offerings, where the BSL expressly permits any non-paid services.

[networked]

The business goal of FSL seems typical enough. The reason I brought up the typical and atypical distinction was something other than the company's motivation.

It seems the_mitsuhiko rejects the label "source-available" because FSL software becomes free. That's different from most other source-available product licenses. (I don't have statistics; this is my impression.) In this sense FSL and BSL are similar enough to each other and both atypical. So, if this is the_mitsuhiko's objection to the label, he can credibly claim FSL to be different from a regular source-available license where it matters to him. (As I said, IMO a better approach than disputing the label.)

> without opening it up to competition.

I wonder about that. In many markets you can probably compete using a competent fork tracking a two-year-old version of a market leader. Even integrations shouldn't be too much of a problem if the market leader naturally avoids breaking the API.