Pull request #4 from guide-fontana#princip
Title: Need nuanced explanation of "no restrictions" in defining completeness of software freedom
Modify sentence that oversimplifies notion of completeness of software freedom. In reality the FSF (as chief guardians of what the definition of free software is) and the larger Free Software community have tolerated certain kinds of restrictions on software freedom. One example, called out in my change to this sentence, is that of copyleft requirements. To arch lax-permissive-license advocates copyleft requirements may be an undue restriction on software freedom, but the larger Free Software community considers copyleft (at least within limits recognized by the FSF) to be a tolerable deviation from maximum software freedom for a given user. In the case of copyleft, the justification is that the constraints on that user allow software freedom to be maximized among the larger set of present and future users.
Under review
1 reviewer
guide#master
git pull https://k.copyleft.org/guide-fontana princip
2014-12-07 05:00:27
Richard Fontana (fontana)
fontana@sharpeleven.org
Git pull requests don't support updates yet.
Pull Request Reviewers
  • Bradley Kuhn (bkuhn)
Pull Request Content
2 comments (0 inline, 2 general)
Showing 1 commit
3
1 2015-04-03 01:18:39
fontana
 1a7de6ba649d princip
Modify sentence that oversimplifies notion of completeness of software freedom. In reality the FSF (as chief guardians of what the definition of free software is) and the larger Free Software community have tolerated certain kinds of restrictions on software freedom. One example, called out in my change to this sentence, is that of copyleft requirements. To arch lax-permissive-license advocates copyleft requirements may be an undue restriction on software freedom, but the larger Free Software community considers copyleft (at least within limits recognized by the FSF) to be a tolerable deviation from maximum software freedom for a given user. In the case of copyleft, the justification is that the constraints on that user allow software freedom to be maximized among the larger set of present and future users.
Common ancestor: 26def8538a10
0 files changed
No files
Changeset was too big and was cut off... Show full diff anyway

Changeset was too big and was cut off... Show full diff anyway

2 comments (0 inline, 2 general)
Richard Fontana (fontana)
3 years and 6 months ago on pull request "Need nuanced explanation of "no restrictions" in defining completeness of software freedom"

Status change: Under review

Auto status change to Under Review

Stephen Compall (S11001001)
3 years and 3 months ago on pull request "Need nuanced explanation of "no restrictions" in defining completeness of software freedom"

My first instinct was to say that this point oughtn't be made. The description is convincing of the need for this change, though.

I think that the point being made should be moved to a following paragraph, though. I think it interrupts the intro of Freedom 0 just as it's gaining momentum.

Also, I would replace "compatible with software freedom" with "to improve, rather than detract from, software freedom for all users". That may eliminate the need for the parenthetical.