The website says: > Open-source forever > Transparent code, permissive license, and a community-driven roadmap. Which I was going to mention is contradictory, because the point of permissive licenses is that it does not have to be Free forever. But the license is actually GPLv3 instead. So still contradictory wording, but the "permissive" is the part that isn't correct :-)
> Which I was going to mention is contradictory, because the point of permissive licenses is that it does not have to be Free forever. No, the point of permissive licenses is that third-party derivatives , which have no impact on the licensing of the original, don't have to be free ever, while the point of copyleft licenses is that they do. Neither has any effect whatsoever on what future first-party licensing can be…
> No, the point of permissive licenses is that third-party derivatives, which have no impact on the licensing of the original, don't have to be free ever, while the point of copyleft licenses is that they do.
This should read "Yes, [...]".
The point of permissive licenses is for people to sublicense it. You can use this to sublicense the software using a license that actually enforces it must remain Free (see Redict for an example) but it is almost always the case that someone uses this headlining feature of permissive licenses to lock the code up and extract rent.
Your next paragraph frames single contributor or CLA as the two primary development patterns, when that those are absolutely the exception, especially if we exclude repos for things like AoC our homework, which are mostly single contributor.