- cross-posted to:
- [email protected]
- cross-posted to:
- [email protected]
No more open source.
Vendors who provide competitive services built on our community products will no longer be able to incorporate future releases, bug fixes, or security patches contributed to our products.
Where I don’t disagree with anything you say here, someone who contributes to a project with a license like this should already be aware and have accepted that it may ultimately be taken out of their hands, and that’s fine if that’s what they want to do. In fact, I prefer it for some types of software (I can’t think of a better way to promote adoption of reference designs such as TCP/IP). That said, if the idea of working with a group and losing control or access to it is a problem for you, then by all means don’t do so and tell others of the risks.
Yep my go to is MIT for libraries/frameworks and GPL for full applications. I don’t want to restrict the use of my libraries to only GPL code unless I have a specific reason to do so.