License to disallow distribution in closed source software, but allow exceptions made by owner?
Is there a license (similar to the GNU v3 software license) that forbids the usage of an open-source software in closed-source software, but except parties that receive approval by the original owner (NOT other contributors) to do so?
Imagine I write an open-source library, and I am the original owner/creator, and I only want to allow it to be used in open-source projects. But, I (and only I, without consent of other contributors) can allow a company to use the open-source library in their closed-source software in exchange for a fee or other advantages.
Another situation could be when I write an open-source library that I don't want to be distributed in closed-source software, except for closed-source software that I write myself in order to gain an income based on my open-source library, but not close the library to other people that want to create a new open-source project using my library.
license-recommendation distribution closed-source redistribution license
New contributor
add a comment |
Is there a license (similar to the GNU v3 software license) that forbids the usage of an open-source software in closed-source software, but except parties that receive approval by the original owner (NOT other contributors) to do so?
Imagine I write an open-source library, and I am the original owner/creator, and I only want to allow it to be used in open-source projects. But, I (and only I, without consent of other contributors) can allow a company to use the open-source library in their closed-source software in exchange for a fee or other advantages.
Another situation could be when I write an open-source library that I don't want to be distributed in closed-source software, except for closed-source software that I write myself in order to gain an income based on my open-source library, but not close the library to other people that want to create a new open-source project using my library.
license-recommendation distribution closed-source redistribution license
New contributor
add a comment |
Is there a license (similar to the GNU v3 software license) that forbids the usage of an open-source software in closed-source software, but except parties that receive approval by the original owner (NOT other contributors) to do so?
Imagine I write an open-source library, and I am the original owner/creator, and I only want to allow it to be used in open-source projects. But, I (and only I, without consent of other contributors) can allow a company to use the open-source library in their closed-source software in exchange for a fee or other advantages.
Another situation could be when I write an open-source library that I don't want to be distributed in closed-source software, except for closed-source software that I write myself in order to gain an income based on my open-source library, but not close the library to other people that want to create a new open-source project using my library.
license-recommendation distribution closed-source redistribution license
New contributor
Is there a license (similar to the GNU v3 software license) that forbids the usage of an open-source software in closed-source software, but except parties that receive approval by the original owner (NOT other contributors) to do so?
Imagine I write an open-source library, and I am the original owner/creator, and I only want to allow it to be used in open-source projects. But, I (and only I, without consent of other contributors) can allow a company to use the open-source library in their closed-source software in exchange for a fee or other advantages.
Another situation could be when I write an open-source library that I don't want to be distributed in closed-source software, except for closed-source software that I write myself in order to gain an income based on my open-source library, but not close the library to other people that want to create a new open-source project using my library.
license-recommendation distribution closed-source redistribution license
license-recommendation distribution closed-source redistribution license
New contributor
New contributor
New contributor
asked Apr 20 at 12:31
TitulumTitulum
1134
1134
New contributor
New contributor
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
The practice of selling exceptions to the GPL is perfectly commonplace, but you must either be the sole copyright holder, or else have prior permission from all other copyright holders. In order to achieve the latter, you must have other contributors agree to a contributor licensing agreement (CLA) that allows you, specifically, to offer that contributor's copyrighted work under different terms in the future. In order words, it is important that you not receive contributors' work under (exclusively) GPL copyleft terms, but under a much more permissive arrangement in which each contributor gives you latitude to do as you please with their contribution.
You may wish to search for CLA templates that suit your needs. (I cannot recommend one in particular.)
In order for a contributor to agree to such terms, it is either the case that
the contributor doesn't care about GPL copyleft terms and would happily allow anyone to use their work under permissive terms, or
the contributor has some expectations about how they trust you to exercise this privilege over their work. In this case, be forthright with contributors about how you plan you use their contributions. Surprising your contributors by doing something they did not expect, e.g., selling their contributions to a company for your own personal profit, is not likely to garner goodwill for yourself, nor attract future contributors to your project. Therefore, simply be upfront about your intent to do so, and you can still get contributions from anyone for whom that strategy is not a problem.
I know that the website choosealicense.com exists, but is are there any websites that offer similar functionality where you check a series of options and then the website will return to you the most relevant license?
– Titulum
Apr 20 at 13:50
I'd add that one way (and the typical way I know of, but your experience might differ) to hand out a non-GPL version is to simply use another license for that one contract partner. Feel free to incorporate or not as you see fit.
– Frank Hopkins
Apr 20 at 16:51
1
This practice is called "dual licensing" or "multi licensing" and googling that will take you to some pages describing how it works and how to do it.
– davidbak
Apr 20 at 17:52
1
The Harmony Agreements site offers some CLA templates that seem to be well-regarded, as far as a CLA can be well-regarded.
– amon
Apr 21 at 7:57
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "619"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
noCode: true, onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Titulum is a new contributor. Be nice, and check out our Code of Conduct.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fopensource.stackexchange.com%2fquestions%2f8211%2flicense-to-disallow-distribution-in-closed-source-software-but-allow-exceptions%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
The practice of selling exceptions to the GPL is perfectly commonplace, but you must either be the sole copyright holder, or else have prior permission from all other copyright holders. In order to achieve the latter, you must have other contributors agree to a contributor licensing agreement (CLA) that allows you, specifically, to offer that contributor's copyrighted work under different terms in the future. In order words, it is important that you not receive contributors' work under (exclusively) GPL copyleft terms, but under a much more permissive arrangement in which each contributor gives you latitude to do as you please with their contribution.
You may wish to search for CLA templates that suit your needs. (I cannot recommend one in particular.)
In order for a contributor to agree to such terms, it is either the case that
the contributor doesn't care about GPL copyleft terms and would happily allow anyone to use their work under permissive terms, or
the contributor has some expectations about how they trust you to exercise this privilege over their work. In this case, be forthright with contributors about how you plan you use their contributions. Surprising your contributors by doing something they did not expect, e.g., selling their contributions to a company for your own personal profit, is not likely to garner goodwill for yourself, nor attract future contributors to your project. Therefore, simply be upfront about your intent to do so, and you can still get contributions from anyone for whom that strategy is not a problem.
I know that the website choosealicense.com exists, but is are there any websites that offer similar functionality where you check a series of options and then the website will return to you the most relevant license?
– Titulum
Apr 20 at 13:50
I'd add that one way (and the typical way I know of, but your experience might differ) to hand out a non-GPL version is to simply use another license for that one contract partner. Feel free to incorporate or not as you see fit.
– Frank Hopkins
Apr 20 at 16:51
1
This practice is called "dual licensing" or "multi licensing" and googling that will take you to some pages describing how it works and how to do it.
– davidbak
Apr 20 at 17:52
1
The Harmony Agreements site offers some CLA templates that seem to be well-regarded, as far as a CLA can be well-regarded.
– amon
Apr 21 at 7:57
add a comment |
The practice of selling exceptions to the GPL is perfectly commonplace, but you must either be the sole copyright holder, or else have prior permission from all other copyright holders. In order to achieve the latter, you must have other contributors agree to a contributor licensing agreement (CLA) that allows you, specifically, to offer that contributor's copyrighted work under different terms in the future. In order words, it is important that you not receive contributors' work under (exclusively) GPL copyleft terms, but under a much more permissive arrangement in which each contributor gives you latitude to do as you please with their contribution.
You may wish to search for CLA templates that suit your needs. (I cannot recommend one in particular.)
In order for a contributor to agree to such terms, it is either the case that
the contributor doesn't care about GPL copyleft terms and would happily allow anyone to use their work under permissive terms, or
the contributor has some expectations about how they trust you to exercise this privilege over their work. In this case, be forthright with contributors about how you plan you use their contributions. Surprising your contributors by doing something they did not expect, e.g., selling their contributions to a company for your own personal profit, is not likely to garner goodwill for yourself, nor attract future contributors to your project. Therefore, simply be upfront about your intent to do so, and you can still get contributions from anyone for whom that strategy is not a problem.
I know that the website choosealicense.com exists, but is are there any websites that offer similar functionality where you check a series of options and then the website will return to you the most relevant license?
– Titulum
Apr 20 at 13:50
I'd add that one way (and the typical way I know of, but your experience might differ) to hand out a non-GPL version is to simply use another license for that one contract partner. Feel free to incorporate or not as you see fit.
– Frank Hopkins
Apr 20 at 16:51
1
This practice is called "dual licensing" or "multi licensing" and googling that will take you to some pages describing how it works and how to do it.
– davidbak
Apr 20 at 17:52
1
The Harmony Agreements site offers some CLA templates that seem to be well-regarded, as far as a CLA can be well-regarded.
– amon
Apr 21 at 7:57
add a comment |
The practice of selling exceptions to the GPL is perfectly commonplace, but you must either be the sole copyright holder, or else have prior permission from all other copyright holders. In order to achieve the latter, you must have other contributors agree to a contributor licensing agreement (CLA) that allows you, specifically, to offer that contributor's copyrighted work under different terms in the future. In order words, it is important that you not receive contributors' work under (exclusively) GPL copyleft terms, but under a much more permissive arrangement in which each contributor gives you latitude to do as you please with their contribution.
You may wish to search for CLA templates that suit your needs. (I cannot recommend one in particular.)
In order for a contributor to agree to such terms, it is either the case that
the contributor doesn't care about GPL copyleft terms and would happily allow anyone to use their work under permissive terms, or
the contributor has some expectations about how they trust you to exercise this privilege over their work. In this case, be forthright with contributors about how you plan you use their contributions. Surprising your contributors by doing something they did not expect, e.g., selling their contributions to a company for your own personal profit, is not likely to garner goodwill for yourself, nor attract future contributors to your project. Therefore, simply be upfront about your intent to do so, and you can still get contributions from anyone for whom that strategy is not a problem.
The practice of selling exceptions to the GPL is perfectly commonplace, but you must either be the sole copyright holder, or else have prior permission from all other copyright holders. In order to achieve the latter, you must have other contributors agree to a contributor licensing agreement (CLA) that allows you, specifically, to offer that contributor's copyrighted work under different terms in the future. In order words, it is important that you not receive contributors' work under (exclusively) GPL copyleft terms, but under a much more permissive arrangement in which each contributor gives you latitude to do as you please with their contribution.
You may wish to search for CLA templates that suit your needs. (I cannot recommend one in particular.)
In order for a contributor to agree to such terms, it is either the case that
the contributor doesn't care about GPL copyleft terms and would happily allow anyone to use their work under permissive terms, or
the contributor has some expectations about how they trust you to exercise this privilege over their work. In this case, be forthright with contributors about how you plan you use their contributions. Surprising your contributors by doing something they did not expect, e.g., selling their contributions to a company for your own personal profit, is not likely to garner goodwill for yourself, nor attract future contributors to your project. Therefore, simply be upfront about your intent to do so, and you can still get contributions from anyone for whom that strategy is not a problem.
edited Apr 20 at 13:34
answered Apr 20 at 13:28
apsillers♦apsillers
16.5k12954
16.5k12954
I know that the website choosealicense.com exists, but is are there any websites that offer similar functionality where you check a series of options and then the website will return to you the most relevant license?
– Titulum
Apr 20 at 13:50
I'd add that one way (and the typical way I know of, but your experience might differ) to hand out a non-GPL version is to simply use another license for that one contract partner. Feel free to incorporate or not as you see fit.
– Frank Hopkins
Apr 20 at 16:51
1
This practice is called "dual licensing" or "multi licensing" and googling that will take you to some pages describing how it works and how to do it.
– davidbak
Apr 20 at 17:52
1
The Harmony Agreements site offers some CLA templates that seem to be well-regarded, as far as a CLA can be well-regarded.
– amon
Apr 21 at 7:57
add a comment |
I know that the website choosealicense.com exists, but is are there any websites that offer similar functionality where you check a series of options and then the website will return to you the most relevant license?
– Titulum
Apr 20 at 13:50
I'd add that one way (and the typical way I know of, but your experience might differ) to hand out a non-GPL version is to simply use another license for that one contract partner. Feel free to incorporate or not as you see fit.
– Frank Hopkins
Apr 20 at 16:51
1
This practice is called "dual licensing" or "multi licensing" and googling that will take you to some pages describing how it works and how to do it.
– davidbak
Apr 20 at 17:52
1
The Harmony Agreements site offers some CLA templates that seem to be well-regarded, as far as a CLA can be well-regarded.
– amon
Apr 21 at 7:57
I know that the website choosealicense.com exists, but is are there any websites that offer similar functionality where you check a series of options and then the website will return to you the most relevant license?
– Titulum
Apr 20 at 13:50
I know that the website choosealicense.com exists, but is are there any websites that offer similar functionality where you check a series of options and then the website will return to you the most relevant license?
– Titulum
Apr 20 at 13:50
I'd add that one way (and the typical way I know of, but your experience might differ) to hand out a non-GPL version is to simply use another license for that one contract partner. Feel free to incorporate or not as you see fit.
– Frank Hopkins
Apr 20 at 16:51
I'd add that one way (and the typical way I know of, but your experience might differ) to hand out a non-GPL version is to simply use another license for that one contract partner. Feel free to incorporate or not as you see fit.
– Frank Hopkins
Apr 20 at 16:51
1
1
This practice is called "dual licensing" or "multi licensing" and googling that will take you to some pages describing how it works and how to do it.
– davidbak
Apr 20 at 17:52
This practice is called "dual licensing" or "multi licensing" and googling that will take you to some pages describing how it works and how to do it.
– davidbak
Apr 20 at 17:52
1
1
The Harmony Agreements site offers some CLA templates that seem to be well-regarded, as far as a CLA can be well-regarded.
– amon
Apr 21 at 7:57
The Harmony Agreements site offers some CLA templates that seem to be well-regarded, as far as a CLA can be well-regarded.
– amon
Apr 21 at 7:57
add a comment |
Titulum is a new contributor. Be nice, and check out our Code of Conduct.
Titulum is a new contributor. Be nice, and check out our Code of Conduct.
Titulum is a new contributor. Be nice, and check out our Code of Conduct.
Titulum is a new contributor. Be nice, and check out our Code of Conduct.
Thanks for contributing an answer to Open Source Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fopensource.stackexchange.com%2fquestions%2f8211%2flicense-to-disallow-distribution-in-closed-source-software-but-allow-exceptions%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown