Is the Maximum Use License for Everybody (MULE) a FOSS license?For what reasons should you make the user...
Is there any danger of my neighbor having my wife's signature?
In a post apocalypse world, with no power and few survivors, would Satnav still work?
How can changes in personality/values of a person who turned into a vampire be explained?
How do I avoid the "chosen hero" feeling?
Taking an academic pseudonym?
Identical projects by students at two different colleges: still plagiarism?
Is the UK legally prevented from having another referendum on Brexit?
How do I purchase a drop bar bike that will be converted to flat bar?
Create a line break in a subscript-position term
Was the Spartan by Mimic Systems a real product?
What is wrong with my use of "find -print0"?
How do I narratively explain how in-game circumstances do not mechanically allow a PC to instantly kill an NPC?
How can I prep for the Curse of Strahd adventure effectively?
What does @ mean in a hostname in DNS configuration?
Why does a single AND gate need 60 transistors?
Isn't a semicolon (';') needed after a function declaration in C++?
Two oatmeal pies a day keep the doctor away?
Protagonist constantly has to have long words explained to her. Will this get tedious?
What is an explicit bijection in combinatorics?
Why aren't passengers instructed how to lift aisle armrests?
Why is Shelob considered evil?
How to deal with an underperforming subordinate?
Is Developer Console going to be deprecated?
What does "don't have a baby" imply or mean in this sentence?
Is the Maximum Use License for Everybody (MULE) a FOSS license?
For what reasons should you make the user agree to a FOSS licence during installation?Can I create and use my own license or do I need to publish it somewhere?How to read the license for EDSDK?How to apply MIT license in the GitHub repo for fully free project?Who is responsible for code being in the public domain?Can I change the copyright license, with this text in the CLA?Recursive license implications for third party FOSS components?Is declaring something one made as “free software” legally binding?What license has jai_imageio ? (jai imageio)How should I identify myself in a copyright notice / license?
I encountered an obscure software license called the Maximum Use License for Everybody (MULE). (I have used text from version 4 below, but my concerns also apply to version 3.) The license first states:
- This software is "free" or "open source" software. It doesn't matter which of these names you call it. […]
but subsequent sections then state (emphasis added):
- You may use this software in any way you wish, subject to all applicable laws and to the provisions of this Maximum Use License for Everyone. You may copy and distribute all or part of this software, without cost, at will.
[…]
- You may give away, or sell at cost, an aggregate software distribution containing this software and software from other sources, without remunerating the copyright holder. If you give away, or sell at cost, a fully functional and readily available aggregate software distribution containing this software and software from other sources, then you may also include this software in an enhanced version of the same aggregate software distribution which may be sold for profit, without remunerating the copyright holder. However, if you sell copies of all or part of this software under any other circumstances, either alone or together with other works, you must reach an agreement with the copyright holder as to a reasonable rate of remuneration per copy (or a waiver of remuneration).
[…]
You may copy and distribute other software containing all or part of this software, in modified or unmodified form, without cost under this Maximum Use License for Everyone, or under any other "free" or "open source" software license consistent with the Open Source Definition promoted by the Open Source Initiative http://opensource.org/. However, if you sell any copies of such software (except as part of an aggregate software distribution under the circumstances specified in paragraph 4 of this license), you must reach an agreement with the copyright holder of this software as to a reasonable rate of remuneration per copy (or a waiver of remuneration).
You may also copy and distribute other software containing all or part of this software, in modified or unmodified form, under any software license that is not among the "free" or "open source" licenses to which paragraph 6 of this license refers, but only after reaching an agreement with the copyright holder as to a reasonable rate of remuneration per copy (or a waiver of remuneration).
I'm inclined to think this is not a legitimate FOSS (free or open source software) license due to contradictions with FOSS definitions, which prohibit licenses from restricting the sale of the software by any party. Overall, I think the author of this license is interpreting "free software" and "open source software" too broadly if not incorrectly throughout this license.
I also think that ability to relicense under a (recognized) FOSS license in paragraph 6 is impossible in practice, because recognized FOSS licenses will not allow the "without cost" provision to be enforced; the copyright holder of a MULE-licensed project would essentially have to allow sale by anybody without remuneration.
licensing relicensing restrictions crayon-licenses
add a comment |
I encountered an obscure software license called the Maximum Use License for Everybody (MULE). (I have used text from version 4 below, but my concerns also apply to version 3.) The license first states:
- This software is "free" or "open source" software. It doesn't matter which of these names you call it. […]
but subsequent sections then state (emphasis added):
- You may use this software in any way you wish, subject to all applicable laws and to the provisions of this Maximum Use License for Everyone. You may copy and distribute all or part of this software, without cost, at will.
[…]
- You may give away, or sell at cost, an aggregate software distribution containing this software and software from other sources, without remunerating the copyright holder. If you give away, or sell at cost, a fully functional and readily available aggregate software distribution containing this software and software from other sources, then you may also include this software in an enhanced version of the same aggregate software distribution which may be sold for profit, without remunerating the copyright holder. However, if you sell copies of all or part of this software under any other circumstances, either alone or together with other works, you must reach an agreement with the copyright holder as to a reasonable rate of remuneration per copy (or a waiver of remuneration).
[…]
You may copy and distribute other software containing all or part of this software, in modified or unmodified form, without cost under this Maximum Use License for Everyone, or under any other "free" or "open source" software license consistent with the Open Source Definition promoted by the Open Source Initiative http://opensource.org/. However, if you sell any copies of such software (except as part of an aggregate software distribution under the circumstances specified in paragraph 4 of this license), you must reach an agreement with the copyright holder of this software as to a reasonable rate of remuneration per copy (or a waiver of remuneration).
You may also copy and distribute other software containing all or part of this software, in modified or unmodified form, under any software license that is not among the "free" or "open source" licenses to which paragraph 6 of this license refers, but only after reaching an agreement with the copyright holder as to a reasonable rate of remuneration per copy (or a waiver of remuneration).
I'm inclined to think this is not a legitimate FOSS (free or open source software) license due to contradictions with FOSS definitions, which prohibit licenses from restricting the sale of the software by any party. Overall, I think the author of this license is interpreting "free software" and "open source software" too broadly if not incorrectly throughout this license.
I also think that ability to relicense under a (recognized) FOSS license in paragraph 6 is impossible in practice, because recognized FOSS licenses will not allow the "without cost" provision to be enforced; the copyright holder of a MULE-licensed project would essentially have to allow sale by anybody without remuneration.
licensing relicensing restrictions crayon-licenses
I apologize if the obscurity of this license makes it off-topic; my hope is that any answer is rather straightforward. Others raised similar concerns about version 3 of this license a long time ago. I understand there's likely nothing stopping someone from calling something "free" or "open source" even if it isn't. And even if software projects have legitimate concerns about users or redistributors unfairly profiting from their work, my impression is that FOSS disagrees or at least refuse its licenses be used to address that.
– chrstphrchvz
3 hours ago
add a comment |
I encountered an obscure software license called the Maximum Use License for Everybody (MULE). (I have used text from version 4 below, but my concerns also apply to version 3.) The license first states:
- This software is "free" or "open source" software. It doesn't matter which of these names you call it. […]
but subsequent sections then state (emphasis added):
- You may use this software in any way you wish, subject to all applicable laws and to the provisions of this Maximum Use License for Everyone. You may copy and distribute all or part of this software, without cost, at will.
[…]
- You may give away, or sell at cost, an aggregate software distribution containing this software and software from other sources, without remunerating the copyright holder. If you give away, or sell at cost, a fully functional and readily available aggregate software distribution containing this software and software from other sources, then you may also include this software in an enhanced version of the same aggregate software distribution which may be sold for profit, without remunerating the copyright holder. However, if you sell copies of all or part of this software under any other circumstances, either alone or together with other works, you must reach an agreement with the copyright holder as to a reasonable rate of remuneration per copy (or a waiver of remuneration).
[…]
You may copy and distribute other software containing all or part of this software, in modified or unmodified form, without cost under this Maximum Use License for Everyone, or under any other "free" or "open source" software license consistent with the Open Source Definition promoted by the Open Source Initiative http://opensource.org/. However, if you sell any copies of such software (except as part of an aggregate software distribution under the circumstances specified in paragraph 4 of this license), you must reach an agreement with the copyright holder of this software as to a reasonable rate of remuneration per copy (or a waiver of remuneration).
You may also copy and distribute other software containing all or part of this software, in modified or unmodified form, under any software license that is not among the "free" or "open source" licenses to which paragraph 6 of this license refers, but only after reaching an agreement with the copyright holder as to a reasonable rate of remuneration per copy (or a waiver of remuneration).
I'm inclined to think this is not a legitimate FOSS (free or open source software) license due to contradictions with FOSS definitions, which prohibit licenses from restricting the sale of the software by any party. Overall, I think the author of this license is interpreting "free software" and "open source software" too broadly if not incorrectly throughout this license.
I also think that ability to relicense under a (recognized) FOSS license in paragraph 6 is impossible in practice, because recognized FOSS licenses will not allow the "without cost" provision to be enforced; the copyright holder of a MULE-licensed project would essentially have to allow sale by anybody without remuneration.
licensing relicensing restrictions crayon-licenses
I encountered an obscure software license called the Maximum Use License for Everybody (MULE). (I have used text from version 4 below, but my concerns also apply to version 3.) The license first states:
- This software is "free" or "open source" software. It doesn't matter which of these names you call it. […]
but subsequent sections then state (emphasis added):
- You may use this software in any way you wish, subject to all applicable laws and to the provisions of this Maximum Use License for Everyone. You may copy and distribute all or part of this software, without cost, at will.
[…]
- You may give away, or sell at cost, an aggregate software distribution containing this software and software from other sources, without remunerating the copyright holder. If you give away, or sell at cost, a fully functional and readily available aggregate software distribution containing this software and software from other sources, then you may also include this software in an enhanced version of the same aggregate software distribution which may be sold for profit, without remunerating the copyright holder. However, if you sell copies of all or part of this software under any other circumstances, either alone or together with other works, you must reach an agreement with the copyright holder as to a reasonable rate of remuneration per copy (or a waiver of remuneration).
[…]
You may copy and distribute other software containing all or part of this software, in modified or unmodified form, without cost under this Maximum Use License for Everyone, or under any other "free" or "open source" software license consistent with the Open Source Definition promoted by the Open Source Initiative http://opensource.org/. However, if you sell any copies of such software (except as part of an aggregate software distribution under the circumstances specified in paragraph 4 of this license), you must reach an agreement with the copyright holder of this software as to a reasonable rate of remuneration per copy (or a waiver of remuneration).
You may also copy and distribute other software containing all or part of this software, in modified or unmodified form, under any software license that is not among the "free" or "open source" licenses to which paragraph 6 of this license refers, but only after reaching an agreement with the copyright holder as to a reasonable rate of remuneration per copy (or a waiver of remuneration).
I'm inclined to think this is not a legitimate FOSS (free or open source software) license due to contradictions with FOSS definitions, which prohibit licenses from restricting the sale of the software by any party. Overall, I think the author of this license is interpreting "free software" and "open source software" too broadly if not incorrectly throughout this license.
I also think that ability to relicense under a (recognized) FOSS license in paragraph 6 is impossible in practice, because recognized FOSS licenses will not allow the "without cost" provision to be enforced; the copyright holder of a MULE-licensed project would essentially have to allow sale by anybody without remuneration.
licensing relicensing restrictions crayon-licenses
licensing relicensing restrictions crayon-licenses
asked 3 hours ago
chrstphrchvzchrstphrchvz
1384
1384
I apologize if the obscurity of this license makes it off-topic; my hope is that any answer is rather straightforward. Others raised similar concerns about version 3 of this license a long time ago. I understand there's likely nothing stopping someone from calling something "free" or "open source" even if it isn't. And even if software projects have legitimate concerns about users or redistributors unfairly profiting from their work, my impression is that FOSS disagrees or at least refuse its licenses be used to address that.
– chrstphrchvz
3 hours ago
add a comment |
I apologize if the obscurity of this license makes it off-topic; my hope is that any answer is rather straightforward. Others raised similar concerns about version 3 of this license a long time ago. I understand there's likely nothing stopping someone from calling something "free" or "open source" even if it isn't. And even if software projects have legitimate concerns about users or redistributors unfairly profiting from their work, my impression is that FOSS disagrees or at least refuse its licenses be used to address that.
– chrstphrchvz
3 hours ago
I apologize if the obscurity of this license makes it off-topic; my hope is that any answer is rather straightforward. Others raised similar concerns about version 3 of this license a long time ago. I understand there's likely nothing stopping someone from calling something "free" or "open source" even if it isn't. And even if software projects have legitimate concerns about users or redistributors unfairly profiting from their work, my impression is that FOSS disagrees or at least refuse its licenses be used to address that.
– chrstphrchvz
3 hours ago
I apologize if the obscurity of this license makes it off-topic; my hope is that any answer is rather straightforward. Others raised similar concerns about version 3 of this license a long time ago. I understand there's likely nothing stopping someone from calling something "free" or "open source" even if it isn't. And even if software projects have legitimate concerns about users or redistributors unfairly profiting from their work, my impression is that FOSS disagrees or at least refuse its licenses be used to address that.
– chrstphrchvz
3 hours ago
add a comment |
2 Answers
2
active
oldest
votes
Oh, good; yet another attempt by the crayon-wielding world to mesh free software ideology with the idea of non-commercial use. How well they all work.
IANAL/IANYL, but I agree with you that the licence is non-free, for the reasons you have stated.
However, I notice that s6, the section that allows re-distribution under any OSI-approved licence provided it is done at no cost, does not require a similar condition to be imposed on the recipient. So if you absolutely had to use some code licenced under MULE, my advice is to have a friend download it, and (per s6) convey it to you under GPLv3 (or, if (s)he must, some non-copyleft licence) without charge. At this point you have a properly-freely-licenced copy with no weird commercial restrictions, and life can proceed. However, it's probably best to avoid using this code if you can.
add a comment |
Forbidding sale of the software has precedent in OSI-approved licenses, for example SIL-OFL 1.1 says:
Neither the Font Software nor any of its individual components, in Original or Modified Versions, may be sold by itself.
But there is reason to believe the OFL is an outlier and wouldn't be OSI-approved if submitted today. Also, the OFL is only intended for fonts, not for software in general.
Back to the license at hand:
- MULE has never been put before the OSI for approval. Calling it an open source license is therefore a bit premature.
- MULE's author disagrees with the Debian Free Software Guidelines. However, the DFSG are the root of the Open Source Definition, and continue to be relevant in license evaluation. I would expect OSI to be hesitant to approve a license that would be shunned by Debian.
- MULE's royalty sharing provisions violate the DFSG's desert island test: How could a seller be able to reach a royalty agreement with the copyright holder unless they have communication channels and money transfer channels available? This is not necessarily a given, e.g. consider a potential seller in an isolated dictatorship.
- MULE's royalty sharing provision requires an agreement to be reached with the copyright holder. But there can be many copyright holders, because any contributor is a copyright holder as well. Reaching a royalty agreement with all of them would be unworkable.
- The author's references to the OSD try to lawyer around its particular phrasing (e.g. regarding “aggregate”), without taking into account the intention of this definition.
- MULE's relicensing provision is badly thought out. For example, MULE is clearly GPL-incompatible. Since the anti-monetization clause is supposed to stick around after relicensing, this relicensing mechanism is not sufficient to save the license from being non-open.
I therefore believe that it is incorrect to consider the MULE license to be open source, believe that it would never be approved as open source by the OSI, and believe no one should ever use this license.
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
});
}
});
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%2f7989%2fis-the-maximum-use-license-for-everybody-mule-a-foss-license%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
Oh, good; yet another attempt by the crayon-wielding world to mesh free software ideology with the idea of non-commercial use. How well they all work.
IANAL/IANYL, but I agree with you that the licence is non-free, for the reasons you have stated.
However, I notice that s6, the section that allows re-distribution under any OSI-approved licence provided it is done at no cost, does not require a similar condition to be imposed on the recipient. So if you absolutely had to use some code licenced under MULE, my advice is to have a friend download it, and (per s6) convey it to you under GPLv3 (or, if (s)he must, some non-copyleft licence) without charge. At this point you have a properly-freely-licenced copy with no weird commercial restrictions, and life can proceed. However, it's probably best to avoid using this code if you can.
add a comment |
Oh, good; yet another attempt by the crayon-wielding world to mesh free software ideology with the idea of non-commercial use. How well they all work.
IANAL/IANYL, but I agree with you that the licence is non-free, for the reasons you have stated.
However, I notice that s6, the section that allows re-distribution under any OSI-approved licence provided it is done at no cost, does not require a similar condition to be imposed on the recipient. So if you absolutely had to use some code licenced under MULE, my advice is to have a friend download it, and (per s6) convey it to you under GPLv3 (or, if (s)he must, some non-copyleft licence) without charge. At this point you have a properly-freely-licenced copy with no weird commercial restrictions, and life can proceed. However, it's probably best to avoid using this code if you can.
add a comment |
Oh, good; yet another attempt by the crayon-wielding world to mesh free software ideology with the idea of non-commercial use. How well they all work.
IANAL/IANYL, but I agree with you that the licence is non-free, for the reasons you have stated.
However, I notice that s6, the section that allows re-distribution under any OSI-approved licence provided it is done at no cost, does not require a similar condition to be imposed on the recipient. So if you absolutely had to use some code licenced under MULE, my advice is to have a friend download it, and (per s6) convey it to you under GPLv3 (or, if (s)he must, some non-copyleft licence) without charge. At this point you have a properly-freely-licenced copy with no weird commercial restrictions, and life can proceed. However, it's probably best to avoid using this code if you can.
Oh, good; yet another attempt by the crayon-wielding world to mesh free software ideology with the idea of non-commercial use. How well they all work.
IANAL/IANYL, but I agree with you that the licence is non-free, for the reasons you have stated.
However, I notice that s6, the section that allows re-distribution under any OSI-approved licence provided it is done at no cost, does not require a similar condition to be imposed on the recipient. So if you absolutely had to use some code licenced under MULE, my advice is to have a friend download it, and (per s6) convey it to you under GPLv3 (or, if (s)he must, some non-copyleft licence) without charge. At this point you have a properly-freely-licenced copy with no weird commercial restrictions, and life can proceed. However, it's probably best to avoid using this code if you can.
answered 1 hour ago
MadHatterMadHatter
8,9971836
8,9971836
add a comment |
add a comment |
Forbidding sale of the software has precedent in OSI-approved licenses, for example SIL-OFL 1.1 says:
Neither the Font Software nor any of its individual components, in Original or Modified Versions, may be sold by itself.
But there is reason to believe the OFL is an outlier and wouldn't be OSI-approved if submitted today. Also, the OFL is only intended for fonts, not for software in general.
Back to the license at hand:
- MULE has never been put before the OSI for approval. Calling it an open source license is therefore a bit premature.
- MULE's author disagrees with the Debian Free Software Guidelines. However, the DFSG are the root of the Open Source Definition, and continue to be relevant in license evaluation. I would expect OSI to be hesitant to approve a license that would be shunned by Debian.
- MULE's royalty sharing provisions violate the DFSG's desert island test: How could a seller be able to reach a royalty agreement with the copyright holder unless they have communication channels and money transfer channels available? This is not necessarily a given, e.g. consider a potential seller in an isolated dictatorship.
- MULE's royalty sharing provision requires an agreement to be reached with the copyright holder. But there can be many copyright holders, because any contributor is a copyright holder as well. Reaching a royalty agreement with all of them would be unworkable.
- The author's references to the OSD try to lawyer around its particular phrasing (e.g. regarding “aggregate”), without taking into account the intention of this definition.
- MULE's relicensing provision is badly thought out. For example, MULE is clearly GPL-incompatible. Since the anti-monetization clause is supposed to stick around after relicensing, this relicensing mechanism is not sufficient to save the license from being non-open.
I therefore believe that it is incorrect to consider the MULE license to be open source, believe that it would never be approved as open source by the OSI, and believe no one should ever use this license.
add a comment |
Forbidding sale of the software has precedent in OSI-approved licenses, for example SIL-OFL 1.1 says:
Neither the Font Software nor any of its individual components, in Original or Modified Versions, may be sold by itself.
But there is reason to believe the OFL is an outlier and wouldn't be OSI-approved if submitted today. Also, the OFL is only intended for fonts, not for software in general.
Back to the license at hand:
- MULE has never been put before the OSI for approval. Calling it an open source license is therefore a bit premature.
- MULE's author disagrees with the Debian Free Software Guidelines. However, the DFSG are the root of the Open Source Definition, and continue to be relevant in license evaluation. I would expect OSI to be hesitant to approve a license that would be shunned by Debian.
- MULE's royalty sharing provisions violate the DFSG's desert island test: How could a seller be able to reach a royalty agreement with the copyright holder unless they have communication channels and money transfer channels available? This is not necessarily a given, e.g. consider a potential seller in an isolated dictatorship.
- MULE's royalty sharing provision requires an agreement to be reached with the copyright holder. But there can be many copyright holders, because any contributor is a copyright holder as well. Reaching a royalty agreement with all of them would be unworkable.
- The author's references to the OSD try to lawyer around its particular phrasing (e.g. regarding “aggregate”), without taking into account the intention of this definition.
- MULE's relicensing provision is badly thought out. For example, MULE is clearly GPL-incompatible. Since the anti-monetization clause is supposed to stick around after relicensing, this relicensing mechanism is not sufficient to save the license from being non-open.
I therefore believe that it is incorrect to consider the MULE license to be open source, believe that it would never be approved as open source by the OSI, and believe no one should ever use this license.
add a comment |
Forbidding sale of the software has precedent in OSI-approved licenses, for example SIL-OFL 1.1 says:
Neither the Font Software nor any of its individual components, in Original or Modified Versions, may be sold by itself.
But there is reason to believe the OFL is an outlier and wouldn't be OSI-approved if submitted today. Also, the OFL is only intended for fonts, not for software in general.
Back to the license at hand:
- MULE has never been put before the OSI for approval. Calling it an open source license is therefore a bit premature.
- MULE's author disagrees with the Debian Free Software Guidelines. However, the DFSG are the root of the Open Source Definition, and continue to be relevant in license evaluation. I would expect OSI to be hesitant to approve a license that would be shunned by Debian.
- MULE's royalty sharing provisions violate the DFSG's desert island test: How could a seller be able to reach a royalty agreement with the copyright holder unless they have communication channels and money transfer channels available? This is not necessarily a given, e.g. consider a potential seller in an isolated dictatorship.
- MULE's royalty sharing provision requires an agreement to be reached with the copyright holder. But there can be many copyright holders, because any contributor is a copyright holder as well. Reaching a royalty agreement with all of them would be unworkable.
- The author's references to the OSD try to lawyer around its particular phrasing (e.g. regarding “aggregate”), without taking into account the intention of this definition.
- MULE's relicensing provision is badly thought out. For example, MULE is clearly GPL-incompatible. Since the anti-monetization clause is supposed to stick around after relicensing, this relicensing mechanism is not sufficient to save the license from being non-open.
I therefore believe that it is incorrect to consider the MULE license to be open source, believe that it would never be approved as open source by the OSI, and believe no one should ever use this license.
Forbidding sale of the software has precedent in OSI-approved licenses, for example SIL-OFL 1.1 says:
Neither the Font Software nor any of its individual components, in Original or Modified Versions, may be sold by itself.
But there is reason to believe the OFL is an outlier and wouldn't be OSI-approved if submitted today. Also, the OFL is only intended for fonts, not for software in general.
Back to the license at hand:
- MULE has never been put before the OSI for approval. Calling it an open source license is therefore a bit premature.
- MULE's author disagrees with the Debian Free Software Guidelines. However, the DFSG are the root of the Open Source Definition, and continue to be relevant in license evaluation. I would expect OSI to be hesitant to approve a license that would be shunned by Debian.
- MULE's royalty sharing provisions violate the DFSG's desert island test: How could a seller be able to reach a royalty agreement with the copyright holder unless they have communication channels and money transfer channels available? This is not necessarily a given, e.g. consider a potential seller in an isolated dictatorship.
- MULE's royalty sharing provision requires an agreement to be reached with the copyright holder. But there can be many copyright holders, because any contributor is a copyright holder as well. Reaching a royalty agreement with all of them would be unworkable.
- The author's references to the OSD try to lawyer around its particular phrasing (e.g. regarding “aggregate”), without taking into account the intention of this definition.
- MULE's relicensing provision is badly thought out. For example, MULE is clearly GPL-incompatible. Since the anti-monetization clause is supposed to stick around after relicensing, this relicensing mechanism is not sufficient to save the license from being non-open.
I therefore believe that it is incorrect to consider the MULE license to be open source, believe that it would never be approved as open source by the OSI, and believe no one should ever use this license.
answered 19 mins ago
amonamon
11.8k11531
11.8k11531
add a comment |
add a comment |
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%2f7989%2fis-the-maximum-use-license-for-everybody-mule-a-foss-license%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
I apologize if the obscurity of this license makes it off-topic; my hope is that any answer is rather straightforward. Others raised similar concerns about version 3 of this license a long time ago. I understand there's likely nothing stopping someone from calling something "free" or "open source" even if it isn't. And even if software projects have legitimate concerns about users or redistributors unfairly profiting from their work, my impression is that FOSS disagrees or at least refuse its licenses be used to address that.
– chrstphrchvz
3 hours ago