Earlier quoted context omitted.
Hm, you can mix GPL code with your previously BSD-licensed project, and release the result under the GPL. However, I'll grant that that's strictly an exception there as I worded things. The only thing that could be done with the hypothetically-still-bsd combined work that couldn't be done with the perfectly allowed GPL combined work is to add more restrictions, though, so I think my general point still stands. That s…
>The only thing that could be done with the hypothetically-still-bsd combined work that couldn't be done with the perfectly allowed GPL combined work is to add more restrictions, though, so I think my general point still stands. That's true, but if I'm a person whose only goal in life is to maximize free software, I may still be rationally motivated to license my project BSD instead of GPL. A BSD-licensed project can…
"If they use my project, it makes my project's ecosystem stronger, which is good for free software."
Maybe. If they run with your code and build a proprietary fork with a few features on you, and users migrate over, your project's ecosystem may be weaker despite the code being used by more people, and it would be bad for free software. It's hard to say.