Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Assign software, data, and figures a permissive open source license #7

Open
gwaybio opened this issue Jul 24, 2019 · 1 comment
Open
Labels
Rule Discussing possible rule

Comments

@gwaybio
Copy link
Member

gwaybio commented Jul 24, 2019

Open source licenses are required for others (developers and end-users) to rapidly build upon and improve current research.

However, open source licenses come in many different flavors. Dual-licensing is possible too.

Make sure to consider how the license will require your work to be attributed but also how it will restrict others in using your research.

@gwaybio gwaybio added the Rule Discussing possible rule label Jul 24, 2019
@allaway
Copy link

allaway commented Jul 25, 2019

My gut reaction is to always opt for the most permissive license. But what are the cons of a permissive license?

Related to that, why do people pick licenses such as CC-BY-NC? What's the rationale?
If a company makes a better (or worse) commercial fork of software, what does the original developer lose?
If a company develops a drug based on data and commercializes it? Who loses? Certainly not the patients, because they end up with one more therapeutic option.

This is something that might be worth exploring - why people pick these more restrictive licenses and how we can incentivize permissive licensing?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Rule Discussing possible rule
Projects
None yet
Development

No branches or pull requests

2 participants