Myths About Open Source: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
=Myths= | =Myths= | ||
#'''If someone says that their project is open source, then the project must really be open source.''' Perhaps the most common myth is that non-commercial (NC) licenses, such as [[Creative Commons Non-Commercial]], or the [[Peer Production License]] - are open source. Just check the [[Open Source Hardware Definition]] to see why NC licenses do not qualify. Yet many people who run NC-licensed projects continue to call their projects open source. Which brings up the second point... | #'''If someone says that their project is open source, then the project must really be open source.''' Perhaps the most common myth is that non-commercial (NC) licenses, such as [[Creative Commons Non-Commercial]], or the [[Peer Production License]] - are open source. Just check the [[Open Source Hardware Definition]] to see why NC licenses do not qualify. Yet many people who run NC-licensed projects continue to call their projects open source. Which brings up the second point... | ||
#'''Open Source is a loosely defined, feel-good term.''' | #'''Open Source is a loosely defined, feel-good term.''' Contrary to common perception, the term open source is a technical term. It has been defined by the [[Open Source Initiative]], and anything that is authentically open source must meet a certain set of conditions which make a product replicable by anyone anywhere in the world. So don't fall into a post-truth error by thinking that open source can be used for anything that looks like it is 'open'. Many people use the term to get the benefit - make their project/product look good - without fulfilling the duties or requirements of actually being open source. See the [[OSI Definition]] for the actual requirements that need to be fulfilled in software, and [[Open Source Hardware Definition]] for the requirements in hardware. Essentially - the product must be documented so you receive 4 freedoms: to examine the design, copy it, modify it, or sell it. | ||
#'''Expired patents, or patents in general, make a design open source.''' Once again, if you examine the open source definition as in the last point - you will observe that patents do not make something open source. To be open source, technical details and blueprints, such as CAD files, must be available. Patents lay out only the concepts, and do not make something replicable - contrary to their intent that 'someone skilled in the art' should be able to built something from the patent. Yes, someone can build something from a patent can replicate what's in the patent - but only if they come up with the design blueprints first. Specific blueprints are NOT included in any patent whatsoever. | #'''Expired patents, or patents in general, make a design open source.''' Once again, if you examine the open source definition as in the last point - you will observe that patents do not make something open source. To be open source, technical details and blueprints, such as CAD files, must be available. Patents lay out only the concepts, and do not make something replicable - contrary to their intent that 'someone skilled in the art' should be able to built something from the patent. Yes, someone can build something from a patent can replicate what's in the patent - but only if they come up with the design blueprints first. Specific blueprints are NOT included in any patent whatsoever. | ||
Revision as of 15:04, 3 June 2020
Myths
- If someone says that their project is open source, then the project must really be open source. Perhaps the most common myth is that non-commercial (NC) licenses, such as Creative Commons Non-Commercial, or the Peer Production License - are open source. Just check the Open Source Hardware Definition to see why NC licenses do not qualify. Yet many people who run NC-licensed projects continue to call their projects open source. Which brings up the second point...
- Open Source is a loosely defined, feel-good term. Contrary to common perception, the term open source is a technical term. It has been defined by the Open Source Initiative, and anything that is authentically open source must meet a certain set of conditions which make a product replicable by anyone anywhere in the world. So don't fall into a post-truth error by thinking that open source can be used for anything that looks like it is 'open'. Many people use the term to get the benefit - make their project/product look good - without fulfilling the duties or requirements of actually being open source. See the OSI Definition for the actual requirements that need to be fulfilled in software, and Open Source Hardware Definition for the requirements in hardware. Essentially - the product must be documented so you receive 4 freedoms: to examine the design, copy it, modify it, or sell it.
- Expired patents, or patents in general, make a design open source. Once again, if you examine the open source definition as in the last point - you will observe that patents do not make something open source. To be open source, technical details and blueprints, such as CAD files, must be available. Patents lay out only the concepts, and do not make something replicable - contrary to their intent that 'someone skilled in the art' should be able to built something from the patent. Yes, someone can build something from a patent can replicate what's in the patent - but only if they come up with the design blueprints first. Specific blueprints are NOT included in any patent whatsoever.