"Open Source" can also become "Source Available" overnight. See Redis, Terraform, etc. In the same vein, "Open Source" can also become "Closed Source" overnight.

In neither case does the change apply retroactively. It only applies to new contributions after the license change.

▲

Imustaskforhelp 2 hours ago | parent [-]

Well technically Redis had a fork before it became source available known as valkey which is still in bsd license

Terraform was forked to create opentofu if I remember correctly

I think the most recent example is kind of minio for this type of thing no?

Also I am interested what are some open source projects which became closed source since it seems that you haven't named any and I am curious how they can do that. There must be some legal laws protecting it.

	▲	bloppe 2 hours ago \| parent [-]
		If a project switches from an open-source to a closed-source license, then from the outside, it just looks like the project was abandoned. The final commit that was published under the open-source license will always be open source. It's the future commits that are now closed source. So no, I don't have any specific examples of that happening. In the case of both Redis and Terraform, the forks were announced after the license change, not before. Indeed, the forks were motivated by the license change. The community didn't get a warning "hey, we're about to change the license, fork it while you still can!". It just changed. That's what I mean when I say the license change does not apply retroactively. The commit of Terraform that existed before the license change is still open-source. I could create a fork branching off that commit today if I wanted to.