diff options
| author | Drew DeVault <sir@cmpwn.com> | 2023-05-17 12:40:49 +0200 |
|---|---|---|
| committer | Drew DeVault <sir@cmpwn.com> | 2023-05-17 12:40:49 +0200 |
| commit | 1710f6dabb6b3a123e7366412ca326ff5a1b4ece (patch) | |
| tree | 9eefa79fae362eb4024abbf6481980291246b588 /content/learn | |
| parent | 49adbc12dd3eb818d16b0f5c25ed82c1749dd71b (diff) | |
| download | writefreesoftware.org-1710f6dabb6b3a123e7366412ca326ff5a1b4ece.tar.xz | |
Various editorial improvements
Diffstat (limited to 'content/learn')
| -rw-r--r-- | content/learn/four-freedoms.md | 13 | ||||
| -rw-r--r-- | content/learn/licenses.md | 29 |
2 files changed, 24 insertions, 18 deletions
diff --git a/content/learn/four-freedoms.md b/content/learn/four-freedoms.md index 17e5632..971b35c 100644 --- a/content/learn/four-freedoms.md +++ b/content/learn/four-freedoms.md @@ -26,13 +26,14 @@ Let's examine each of the four freedoms in more detail. ## 0: Use the software The first freedom guarantees the right for everyone to **use** the software for -any purpose. You are entitled to the use of any free software for any reason, +any purpose. You are entitled to the use of any free software for any purpose, including commercial use -- counter-intuitively, you can sell free software. You can also incorporate free software into your own work, but be careful -- there -are some gotchas here, which we cover under [use & reuse](/learn/use/). +are some gotchas here, which we cover under [use & reuse](/learn/participate/derived-works/). {{< tip >}} -In free software lingo, this is often called the "non-discrimination" clause. +In free software lingo, this is often called the "non-discrimination" +requirement. {{< /tip >}} ## 1: Study and improve the software @@ -57,8 +58,8 @@ it's better for everyone! {{< tip >}} You can charge a fee to those you share the software with, for instance to cover -the costs of bandwidth. Note however that the recipient is entitled to share it -on themselves without paying back any royalties. +the costs of bandwidth. Note however that the recipient is entitled to the right +to share it themselves, without paying back any royalties. {{< /tip >}} ## 3: Collaborate on the software @@ -69,3 +70,5 @@ source code, and the people you share it with can study, improve, and share it right back with you. This is the foundation of the **Free Software Movement**: a global community of software enthusiasts sharing and improving software together. + +{{< button "/learn/licenses" "Next: Free software licenses" "next-button" >}} diff --git a/content/learn/licenses.md b/content/learn/licenses.md index f86826e..67e6e80 100644 --- a/content/learn/licenses.md +++ b/content/learn/licenses.md @@ -12,18 +12,17 @@ with many different trade-offs to suit each software project's unique situation. A free software license grants the necessary rights, perhaps subject to some caveats (e.g. attribution), to establish the four freedoms for recipients of the software. Any software license can be a free software license if it -upholds the four freedoms, but in practice most projects pick from one of a few -licenses established for general use. - -Comments on specific general-purpose software licenses and how to choose between -them for your own projects are addressed in +upholds the four freedoms, but in practice most projects pick one of the many +popular licenses established for general use. Information about these +general-purpose software licenses and how to choose between them for your own +projects are addressed in [choosing a license](/learn/participate/choose-a-license/). -Generally speaking you will encounter a free software license in the "LICENSE" -or "COPYING" file in the software source code. Other projects, particularly -those which pull together source code from many sources, have more intricate -ways of explaining their licensing situation. A common approach to managing this -is the [REUSE specification][0]. +Often you will encounter a free software license in the "LICENSE" or "COPYING" +file present in the software source code. Other projects, particularly those +which combine software from many sources, have more complex ways of explaining +their licensing situation. A common approach to managing this is the [REUSE +specification][0]. [0]: https://reuse.software/ @@ -46,7 +45,7 @@ Attribution clauses require you to **attribute** the authors when distributing or reusing software based on a license with such a clause. This generally involves reproducing the license in full, or sometimes a simple copyright notice, when you distribute the software, modifications to it, or new software -which incorporates some or all of the software. +which incorporates some or all of the original software. Here's an example from the [MIT license]: @@ -118,11 +117,15 @@ Not all licenses have terms which are compatible with one another; in particular copyleft licenses tend to be less compatible with others. Software with incompatible licenses cannot be combined into one work. +{{< tip >}} +You can learn more about license compatibility in [Re-using free software](/learn/participate/derived-works/). +{{< /tip >}} + ### Use of trademarks and patents Software licenses generally deal with copyright-related rights, but commercial -software publishers often hold other kinds of intellectual property, namely -trademarks and patents. Free software licenses often incorporate clauses which +software publishers often hold other kinds of intellectual property, such as +trademarks and patents. Some free software licenses incorporate clauses which address the relationship between the software's copyright grant and other intellectual property, for example agreeing that use of the software does not infringe on the copyright holder's patents, or forbidding the use of the |
