I read that slightly different, but I think your interpretation of it is accurate to the text.
My first read made me think it was in context to a company open sourcing code, particularly hosted software. If your product is SaaS (particularly infrastructure software), one might think twice about open sourcing it, or building it as open source.
I don't know the history of elastic though, so the above may not be an accurate interpretation given more context.
I am now curious if there is a license that allows people to profit using software, but not profit by selling software that conforms to some API. Basically gating the company to be the only company who can provide the SaaS solution.
However, I don't think that license would apply to the actual API / algorithm, just the actual source.
I think this is when it starts to bleed over into software patients.
My first read made me think it was in context to a company open sourcing code, particularly hosted software. If your product is SaaS (particularly infrastructure software), one might think twice about open sourcing it, or building it as open source.
I don't know the history of elastic though, so the above may not be an accurate interpretation given more context.
I am now curious if there is a license that allows people to profit using software, but not profit by selling software that conforms to some API. Basically gating the company to be the only company who can provide the SaaS solution.
However, I don't think that license would apply to the actual API / algorithm, just the actual source.
I think this is when it starts to bleed over into software patients.