Feedback received: choosealicense.com is fine for clear-cut situations, but hard to understand implications if chooser wants to do something else later. Examples given:
- make a proprietary version
- offer support
First maybe could be addressed by noting explicitly which licenses allow proprietary derivatives, though that's a mouthful. Second there are no direct implications, but existence of question perhaps hints it would be useful to explain what a license covers and does not.
One approach would be a FAQ, but not sure such would be maintainable or in scope for site.
Feedback received: choosealicense.com is fine for clear-cut situations, but hard to understand implications if chooser wants to do something else later. Examples given:
First maybe could be addressed by noting explicitly which licenses allow proprietary derivatives, though that's a mouthful. Second there are no direct implications, but existence of question perhaps hints it would be useful to explain what a license covers and does not.
One approach would be a FAQ, but not sure such would be maintainable or in scope for site.