EDIT: A guide on Software Licenses (#572)

learning-software-engineering · Mar 18, 2024 · ad45709 · ad45709
2 parents 682b40b + 125e092
commit ad45709
Show file tree

Hide file tree

Showing 2 changed files with 4 additions and 2 deletions.
diff --git a/Topics/Software_Engineering.md b/Topics/Software_Engineering.md
@@ -23,3 +23,5 @@ Potential topics--
 Guidelines for effectively handling bugs through a systematic life cycle and technical debt through proactive identification, documentation, and strategic repayment practices, emphasizing the importance of maintaining a resilient and sustainable software development ecosystem.
 
 #### [Ethics In Software Engineering](./Software_Engineering/Ethics_In_Software_Engineering.md)
+
+#### [Software Licenses](./Software_Engineering/Software_Licenses.md)
diff --git a/Topics/Software_Engineering/Software_Licenses.md b/Topics/Software_Engineering/Software_Licenses.md
@@ -124,14 +124,14 @@ As mentioned above, there exist many types of software licenses, especially open
 
 In 2008, the Free Software Foundation filed a complaint against Cisco Systems claiming that various Cisco products under the Linksys brand had violated the licenses of many programs on which the FSF held a copyright. Most of the programs were licensed under the GNU General Public License (GPL) and so they allowed users like Cisco to use, modify, and distribute the software in condition that the redistributors shared their source code as well. The FSF accused Cisco of distributing licensed software without sharing source code with its customers.
 
-The FSF and Cisco came to a settlement. You can read more about the case [here].(https://www.fsf.org/news/2008-12-cisco-suit)
+The FSF and Cisco came to a settlement. You can read more about the case [here.](https://www.fsf.org/news/2008-12-cisco-suit)
 
 
 ### [Software Freedom Conservancy and Tesla](https://www.theregister.com/2018/05/21/tesla_inches_toward_gpl_compliance/)
 
 In 2018, after multiple years of pressure from the Software Freedom Conservancy, Tesla released part of its open-source code as required under GNU General Public License (GPL). The company used some GPL-licensed software in the Tesla Model S but had failed to comply with the requirements of the copyleft license.
 
-To learn more about the situation, you can read it [here].(https://www.theregister.com/2018/05/21/tesla_inches_toward_gpl_compliance/)
+To learn more about the situation, you can read it [here.](https://www.theregister.com/2018/05/21/tesla_inches_toward_gpl_compliance/)
 
 
 ## Conclusion
Original file line number	Diff line number	Diff line change
Expand Up		@@ -23,3 +23,5 @@ Potential topics--
		Guidelines for effectively handling bugs through a systematic life cycle and technical debt through proactive identification, documentation, and strategic repayment practices, emphasizing the importance of maintaining a resilient and sustainable software development ecosystem.

		#### [Ethics In Software Engineering](./Software_Engineering/Ethics_In_Software_Engineering.md)

		#### [Software Licenses](./Software_Engineering/Software_Licenses.md)