Skip to content

Commit d3d44b5

Browse files
author
Paul Nathan
committed
Updating readme with license information.
1 parent 6846061 commit d3d44b5

File tree

1 file changed

+27
-0
lines changed

1 file changed

+27
-0
lines changed

README.org

Lines changed: 27 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -48,3 +48,30 @@ Please pull off the top of the `devel` branch for your contributions and use git
4848
My home Jenkins instance deploys that branch out to articulate-lisp.com/devel. This allows me to merge your PR and
4949
see the result quickly without being at a development machine: e.g., I can use my mobile phone to merge your work and
5050
keep the awesome flowing as fast as possible.
51+
52+
** License information & legalities.
53+
54+
My opinion on articulate-lisp.com's licencing is this: it should be easy to grab bits and pieces and easy to fork if
55+
the author disappears. After some careful reading, I selected...
56+
57+
- GPL3 for the documentation itself.
58+
59+
- Snippets and other samples embedded in the documentation should be considered public domain a.k.a CC0.
60+
61+
- The full-size examples in src/ are more substantial and, are licensed as AGPL3. This is denoted in their comment header.
62+
63+
I do not believe that these terms are onerous and I have sought to structure them to permit both free use of small things
64+
and continuity of information.
65+
66+
AGPL3 is a very strict copyleft license and I feel obligated to justify its choice.
67+
68+
Simply put, I believe that software developers have a moral obligation to allow their users to repair the software that
69+
they provide. This facility is usual for physical items: we can fix our bikes, chairs, cars, etc. I believe that we
70+
ought to let our users fix the software they use, or hire other people to make that fix. I also have profound issues with
71+
the software patent industry. AGPL3 is the best license I know of to ensure that what I create gives users these
72+
capabilities and will not be patented. As these are ridiculously small examples, I am fairly positive that any
73+
serious work will not use them. So it should not be onerous on you.
74+
75+
If your corporate lawyers refuse to let example AGPL3 code exist in your development environment, please write in and -
76+
for my part - I will make a good faith effort to negotiate with you for you a less strict license for your company. And I
77+
will doubtlessly say rude things about lawyers.

0 commit comments

Comments
 (0)