Was going to mention MongoDB. the day they announced the change, I created a fork (https://github.com/danx0r/mongo). Now, if a client wants mongoDB I just install this version on a cpu somewhere and go from there. If the project really needs more up-to-date versions of the core DB or the cloud tools, we have a discussion about the restrictions that apply to later versions.
I think this does not really constitute pump-and-dump or loss-leader behavior because the code generated during the open license phase has real value to the community.
One thing I think could use more analysis is, does Mongo's license change breach any copyleft provisions of the original license? I recall they started with the permissive Apache license but prior to the last change 4 years ago they were AGPL.
That was a bad explanation on my part, sorry. They are still open source!
But they diverged from keeping fully aligned with MySQL developments AFAIK so are no longer a fork/distribution as they are forging their own path.
So I was being unclear, the "until a couple of years ago" was referring to divergence rather than a change in license.
Thanks for the reply. I followed this quite closely at the time, but not for the last few years. Glad to hear they're still open. Features will get us all in the end, eh? :)
I think this does not really constitute pump-and-dump or loss-leader behavior because the code generated during the open license phase has real value to the community.
One thing I think could use more analysis is, does Mongo's license change breach any copyleft provisions of the original license? I recall they started with the permissive Apache license but prior to the last change 4 years ago they were AGPL.