Changes for page 3. Free Software and Open Source Software

Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -45,9 +45,12 @@
45	45	* Another problem is that vendors can reuse permissive code without any obligation to share improvements. The vendor writes new proprietary or closed source code based on the open source code and keeps those improvements for himself. This means that the work of the open source community can be used for the vendor's financial benefit without anything being given back. Worse, the proprietary product may outcompete the original open source project, reducing its impact and harming the open source ecosystem. This is called "proprietary capture" or "open core hijacking".
46	46	* There is also the problem of fragmentation. Multiple vendors may each create their own proprietary product based on the same permissive code. Instead of collaborating and contributing back to the common core project, they are inefficiently duplicating their efforts.
47	47
48		-**Copyleft Licenses**To address the problems with proprietary software, the FSF primarily promotes copyleft licenses, which require that any derivative works of the software be licensed under the same terms as the original code. The term "derivative work" is legally vague, but a common understanding is that it means a new work based on the original copyleft code that incorporates it at the source level. This ensures that when contributions are made to a copyleft project, or when copyleft code is reused in another project, the resulting work must also be released under the same copyleft license. This prevents ve
49		-ndors from incorporating copyleft code into proprietary products, and ensures that any derivative works remain open source. In addition, copyleft licenses require that the source code be made available to users so that they can modify, build, and control the software themselves.**OSI Position**
	48	+**Copyleft Licenses**
50	50
	50	+To address the problems with proprietary software, the FSF primarily promotes copyleft licenses, which require that any derivative works of the software be licensed under the same terms as the original code. The term "derivative work" is legally vague, but a common understanding is that it means a new work based on the original copyleft code that incorporates it at the source level. This ensures that when contributions are made to a copyleft project, or when copyleft code is directly reused in another project, the resulting work must be released under the same copyleft license. This prevents vendors from incorporating copyleft code into proprietary products, and ensures that any derivative works remain open source. In addition, copyleft licenses require that the source code be made available to users so that they can modify, build, and control the software themselves.
	51	+
	52	+**OSI Position**
	53	+
51	51	The OSI aims to maximize the contributions and impact of open source by being open to a variety of open source licenses. Permissive licenses have become very popular in recent years, especially in commercial contexts, but open source developers also choose copyleft licenses when they want to ensure that derivative works remain open and free.
52	52
53	53	**User Behavior**
...	...	@@ -58,12 +58,12 @@
58	58
59	59	**Do permissive or copyleft licenses provide the most freedom?**
60	60
61		-* The answer depends on your definition of freedom. Permissive licenses emphasize freedom of choice, allowing you to do whatever you want with the code, including reusing it in proprietary products. Copyleft licenses emphasize user freedom by ensuring that derivative works remain free and open, and by protecting users from proprietary restrictions that could violate the four essential software freedoms. Thus, both permissive and copyleft licenses provide freedom, but they focus on different aspects of it.
	64	+* The answer depends on your definition of freedom. Permissive licenses emphasize freedom of choice, allowing you to do whatever you want with the code, including reusing it in proprietary products. Copyleft licenses emphasize user freedom in a more political sense by ensuring that derivative works remain free and open, and by protecting users from proprietary restrictions that could violate the four essential software freedoms. Thus, both permissive and copyleft licenses provide freedom, but they focus on different aspects of it.
62	62
63	63	**Does a permissive or copyleft project lead to more contributions?**
64	64
65	65	* Permissive licenses might attract more users, especially vendors, and lead to more voluntary contributions. Copyleft licenses, on the other hand, force improvements to be open sourced and shared with the community. Which effect is greater depends on the situation.
66	66
67		-**Why should people with no technical expertise care about open source? People who cannot even read the source code.**
	70	+**Why should people with no technical expertise care about open source? Speaking of people who cannot even read the source code.**
68	68
69	69	* Even if you cannot read or modify the source code yourself, open source gives you the ability to hire experts to customize or improve the software to meet your needs. You can also benefit from the contributions and improvements made by the open source community. In contrast, proprietary software limits your control and often makes you dependent on the vendor for updates and changes. Managers should consider the long-term benefits of open source software, such as flexibility, community-driven innovation, and freedom from vendor lock-in.