However, you are right that the Open Source Definition's "Free Redistribution" clause doesn't require an open source license to be a copyleft license.
This is misleading in a way that contributes to misunderstanding IMO. Copyleft means specifically preserving the same license when redistributing. OSI’s license might not be copyleft per se, but it does in fact limit what the redistribution license can do, and requires the source to stay “open”. Public domain does not require the redistribution license to remain open. OSI is very clear about this, contradicting @seba_dos1’s claim that public domain is OSI open source compatible. https://opensource.org/faq#permissive
OSI’s license might not be copyleft per se, but it does in fact limit what the redistribution license can do, and requires the source to stay “open”.
"OSI's license"? Which one? There's no requirement for the license to require the source to "stay open" for it to be called Open Source, and you have already linked to the page that confirms that.
Public domain does not require the redistribution license to remain open.
Neither do some Open Source licenses, like MIT, which I already mentioned above. Which is even clearly stated by the page you just linked:
Most copyleft licenses are Open Source, but not all Open Source licenses are copyleft. When an Open Source license is not copyleft, that means software released under that license can be used as part of programs distributed under other licenses, including proprietary (non-open-source) licenses. For example, the BSD license is a non-copyleft Open Source license. Such licenses are usually called either "non-copyleft" or "permissive" open source licenses
OSI is very clear about this
It sure is, I don't know why you choose to not read what they write. Heck, you've even got links to 0BSD and MIT-0 licenses earlier, which are recognized as Open Source licenses and which you can both read in their entirety in 3 minutes and that would be enough for you to realize that you're wrong.
OSI’s license might not be copyleft per se, but it does in fact limit what the redistribution license can do, and requires the source to stay “open”.
Please stop spreading misinformation.
It is not a condition of OSI approval for a license to require that downstream projects be reciprocally open source. You can absolutely take MIT licensed code and put it in Microsoft Windows or some closed source app, for example.
If you're unclear or have questions about something, then it's fine to say so and ask questions in the appropriate forum. What you're doing, though—which involves saying something and then waiting for someone to challenge or correct you—is harmful and contributes to even more outlandish and untrue beliefs about open source than what already exist.
To reiterate: the clauses you're quoting do not mean what you are interpreting them to mean, and claiming otherwise, especially so confidently, is actively harmful.
Comments
This is misleading in a way that contributes to misunderstanding IMO. Copyleft means specifically preserving the same license when redistributing. OSI’s license might not be copyleft per se, but it does in fact limit what the redistribution license can do, and requires the source to stay “open”. Public domain does not require the redistribution license to remain open. OSI is very clear about this, contradicting @seba_dos1’s claim that public domain is OSI open source compatible. https://opensource.org/faq#permissive
"OSI's license"? Which one? There's no requirement for the license to require the source to "stay open" for it to be called Open Source, and you have already linked to the page that confirms that.
Neither do some Open Source licenses, like MIT, which I already mentioned above. Which is even clearly stated by the page you just linked:
It sure is, I don't know why you choose to not read what they write. Heck, you've even got links to 0BSD and MIT-0 licenses earlier, which are recognized as Open Source licenses and which you can both read in their entirety in 3 minutes and that would be enough for you to realize that you're wrong.
Please stop spreading misinformation.
It is not a condition of OSI approval for a license to require that downstream projects be reciprocally open source. You can absolutely take MIT licensed code and put it in Microsoft Windows or some closed source app, for example.
If you're unclear or have questions about something, then it's fine to say so and ask questions in the appropriate forum. What you're doing, though—which involves saying something and then waiting for someone to challenge or correct you—is harmful and contributes to even more outlandish and untrue beliefs about open source than what already exist.
To reiterate: the clauses you're quoting do not mean what you are interpreting them to mean, and claiming otherwise, especially so confidently, is actively harmful.