Skip to content

Commit

Permalink
Update language on Open Source and Open Source licenses (#100)
Browse files Browse the repository at this point in the history
* Update starting_open_source_project.md

reviewed section about Open Sourc

* split starting os to add what is os and os licenses files

* Update starting_open_source_project.md

reviewed section about Open Sourc

* split starting os to add what is os and os licenses files

* add what is os and os licenses to sidebar

---------

Co-authored-by: catharinamaracke <[email protected]>
  • Loading branch information
smbuthia and catharinamaracke authored Sep 20, 2023
1 parent bb95ece commit 8900504
Show file tree
Hide file tree
Showing 4 changed files with 56 additions and 34 deletions.
2 changes: 2 additions & 0 deletions docs/_sidebar.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,7 @@
- Open Source Guides

- [What is Open Source](what_is_open_source.md)
- [Open Source Licenses](open_source_licenses.md)
- [Starting an Open Source Project](starting_open_source_project.md)
- [Choosing an Open Source License](choosing_a_license.md)
- [Setting up a GitHub Repository](new_github_repo.md)
Expand Down
29 changes: 29 additions & 0 deletions docs/guidance/open_source_licenses.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,29 @@
# Open Source Licenses

## 📄 Open Source Licenses

> **Note:** A project becomes Open Source once an **Open Source license is applied** to it, and the source code is made **available to the public**.
As per definition, all Open Source licenses require that the respective source code must be publicly available and that modification must be allowed. However, a detailed look into the terms of different Open Source licenses reveals that they can be devided into different categories:
- Copyleft licenses require further licensees, who modify the software, to make such modifi-cations available under the same terms under which the original software was released with-out any further restrictions.
- Permissive licences give the user the flexibility in the sense that they do not restrict the use of the software and do not impose any conditions as to which the software itself or any modification have to be used or subsequently licensed. Consequently software licensed under a permissive license may be modified and distributed under any license including a non open source license for example a proprietary license.

Popular Copyleft licenses include
- [GNU General Public License version 2.1]
- [GNU General Public License version 3.0](https://www.gnu.org/licenses/gpl-3.0.html)

Popular permissive licenses include
- [BSD License]
- [MIT License](https://mit-license.org/)
- [Apache License, Version 2.0](https://httpd.apache.org/docs/2.4/license.html)

> **Note:** Not all open source licenses are copyleft.
## 🔗 Links to Useful Resources

- [List of Open Source licenses approved by the Open Source Initiative](https://opensource.org/licenses)
- [The legal side of open source](https://opensource.guide/legal/)

## 💬 How the Open Source Programme Office Can Support Your Work

If you have questions, would like to make an existing project Open Source, or start a new project that you would like to be Open Source, please reach out on [Discussions](https://github.com/WorldHealthOrganization/open-source-communication-channel/discussions).
37 changes: 3 additions & 34 deletions docs/guidance/starting_open_source_project.md
Original file line number Diff line number Diff line change
@@ -1,12 +1,8 @@
# Starting an Open Source Project

This document provides some quick pointers as you plan to open source your work and use open source components in your work.
This document provides some quick pointers as you plan to make your work publicly available under and Open Source license.

## 🤔 What is Open Source?

The Open Source Initiative (OSI) provides [criteria](https://opensource.org/osd) for open source works. These include free distribution, publicly available source code, permitting derived works, and non-discrimination against people, fields or other software.

> **Note:** A project becomes open source once an **open source license is applied** to it, and the source code or source material is made **available to the public**.
## How to start an Open Source project: Best Practices

GitHub's [opensource.guide](https://opensource.guide/starting-a-project/) provides an easy to follow checklist to help you if you want to open source your project:

Expand All @@ -32,33 +28,6 @@ GitHub's [opensource.guide](https://opensource.guide/starting-a-project/) provid

✔ Assign a community manager to handle interaction with your community

## 📄 Open Source Licenses

Open source licenses are licenses that comply with the open source definition, allowing software to be freely used, modified, and shared. Examples of licenses that are commonly used and have previously been reviewed at WHO include:

- [GNU General Public License (GPL) version 3](https://www.gnu.org/licenses/gpl-3.0.html)
- [MIT License](https://mit-license.org/)
- [Apache License, Version 2.0](https://httpd.apache.org/docs/2.4/license.html)

### Copyleft

[Copyleft](https://opensource.org/faq#copyleft) refers to licenses that allow derivative works but require them to use the same license as the original work. The [GNU General Public License (GPL) version 3](https://www.gnu.org/licenses/gpl-3.0.html) is an example of a copyleft license.

> **Note:** Derived works of copyleft licenses work must be made available with compatible copyleft license.
### Permissive Open Source License

Software under a permissive license can be modified, copied, added to, subtracted from, etc. without any obligation to share those updates. The [MIT License](https://mit-license.org/), which is the most commonly used open source license, is an example of a permissive license.

> **Note:** Not all open source licenses are copyleft.
> 📖 **Read more:** [Choosing an Open Source License](choosing_a_license.md)
## 🔗 Links to Useful Resources

- [List of commonly used open source licenses](https://opensource.org/licenses)
- [The legal side of open source](https://opensource.guide/legal/)

## 💬 How the Open Source Programme Office Can Support Your Work

If you have questions, would like to make an existing project open source, or start a new project that you would like to be open source, please reach out on [Discussions](https://github.com/WorldHealthOrganization/open-source-communication-channel/discussions).
If you have questions, would like to make an existing project open source, or start a new project that you would like to be open source, please reach out on [Discussions](https://github.com/WorldHealthOrganization/open-source-communication-channel/discussions).
22 changes: 22 additions & 0 deletions docs/guidance/what_is_open_source.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,22 @@
# Open Source

## 🤔 What is Open Source?

The term “Open Source” refers to Open Source software, which is code designed to be publicly accessible by anyone to study, use, modify and distribute.

Historically, most software was “free and open” in the sense that it was developed by computer science academics and corporate researchers working together and distributing results under the principles of transparency, sharing and co-operation. However, the late 1960’s and especially the development of personal computers brought new opportunities to define a separate market for software: Since software is covered by copyright, which along with contract law provides a legal basis for its owner to establish exclusive rights, these rights were assigned or licensed under individual terms depending on the underlying business model. Consequently, hardware and software components were sold separately and under different conditions, whereby software was usually sold and distributed in “object code” format only, which is difficult for humans to understand, analyze or modify.

While this distinction between human-readable source code and machine-readable object code reflects a legitimate business model, some critics have argued that users should be able to study and change the software in use, e.g. to remove malicious elements or identify and address security issues, without having to rely on updates and support from respective software vendors. Hence, the main goal for the Free Software software approach is **not** to make software available free of charge but **free of legal constraints** that restrict studying and modifying software. In order to assure availability without restraints upon modification and redistribution, Free Software is released under public licenses reflecting the following four freedoms (see https://www.gnu.org/philosophy/free-sw.html):

- The freedom to run the program as you wish, for any purpose (freedom 0).
- The freedom to study how the program works, and change it so it does your computing as you wish (freedom 1). Access to the source code is a precondition for this.
- The freedom to redistribute copies so you can help others (freedom 2).
- The freedom to distribute copies of your modified versions to others (freedom 3). By doing this you can give the whole community a chance to benefit from your changes. Access to the source code is a precondition for this.

While the general idea of Free Software was very successful, the terminology was difficult to be adopted by the corporate sector. Because the English language does not differentiate between low price and liberty (or gratis and libre in other languages), the term Free Software invariably required further explanation. As a result of the debate with the corporate world, the term Open Source software was suggested as an alternative and as a strategic decision to “promote the idea of Free Software to business people” (see https://www.theregister.com/2018/02/03/open_source_turns_20/). Like the Free Software advocates, supporters of the Open Source software concept establshied a set of criteria for licensing terms to qualify as Open Source conformant, see OSI definition available at https://opensource.org/osd/.

Even if both terms and definitions exist in parallel, the ultimate goal of both the Free Software advocates and the Open Source Software supporters remains the same: Software should be available under legal terms that allow and facilitate studying, modifying and further distributing the software.

## 💬 How the Open Source Programme Office Can Support Your Work

If you have questions, would like to make an existing project Open Source, or start a new project that you would like to be Open Source, please reach out on [Discussions](https://github.com/WorldHealthOrganization/open-source-communication-channel/discussions).

0 comments on commit 8900504

Please sign in to comment.