"please GPL, feel free to take my source code, slap the GPL on it and nanana at me when new changes are made that I now can't incorporate"
Look at the whole OpenBSD wireless drivers fiasco that happened. Really us BSD guys have not much to worry about when it comes to corporations (I've had my BSD licensed source code used by big business, and they have donated money to my little dinky project because it was useful for them), we have to worry our source code is not taken by the GPL crowd as they slap the GPL on any changes and suddenly any improvements made I am not able to use eventhough it is still technically Open Source.
From personal experience, BSD becomes GPL hurts WAY more than some corporation taking the code and using it and letting me know either by email or by donating money to my small project.
(The code for the BSD project is no longer online after I found some flaws in it that I didn't want to fix, so please don't ask)
> "please GPL, feel free to take my source code, slap the GPL on it
Does it really feel better when it's a multi-billion dollar making that? Does it feel better when they withhold their improvements (if any) from you and their users?
BTW, BSD allows that and BSD proponents insist that's perfectly fine to make proprietary forks of their software, that they don't care about what you make with the software. If you feed offended by what those people are doing - forking your software and giving users extra assurances you don't - maybe BSD should not be your choice anyway.
BSD is for when you don't care what people do with your code. If you wanted corporations to pay for your code, you could have gone GPL and offered a double license option. You cannot build a business on expecting donations from happy generous for-profit corporations. In their position, if I really wanted to pay for your work, I would not donate to your project - I would hire you.
And, personally, I too feel bad about you not being able to incorporate improvements made under the GPL to your code. If I ever made such contribution, I would make sure I also made it to your upstream BSD codebase, under BSD. The license of the project is your choice.
"please GPL, feel free to take my source code, slap the GPL on it and nanana at me when new changes are made that I now can't incorporate"
Look at the whole OpenBSD wireless drivers fiasco that happened. Really us BSD guys have not much to worry about when it comes to corporations (I've had my BSD licensed source code used by big business, and they have donated money to my little dinky project because it was useful for them), we have to worry our source code is not taken by the GPL crowd as they slap the GPL on any changes and suddenly any improvements made I am not able to use eventhough it is still technically Open Source.
From personal experience, BSD becomes GPL hurts WAY more than some corporation taking the code and using it and letting me know either by email or by donating money to my small project.
(The code for the BSD project is no longer online after I found some flaws in it that I didn't want to fix, so please don't ask)