|
| 1 | +Copyright (c) 2009 Robert Nystrom |
| 2 | + |
| 3 | +------------------------ Commentary ------------------------ |
| 4 | + |
| 5 | +The licensing story for this repository is a little complex. |
| 6 | +Here's my motivation: |
| 7 | + |
| 8 | +* I want you to get as much use out of the material here as |
| 9 | + possible. I wrote this book to help you, and I don't want |
| 10 | + you to be encumbered when it comes to making the most of |
| 11 | + it. That's also why I put it online for free. |
| 12 | + |
| 13 | +* I have been immensely fortunate to have a large number of |
| 14 | + people contribute to the book through bug reports, fixes, |
| 15 | + pull requests, and other suggestions. Putting on GitHub |
| 16 | + and treating it like an open source project made a |
| 17 | + dramatic improvement in the resulting quality of the |
| 18 | + book. |
| 19 | + |
| 20 | + I want to ensure people can fork the repo, send me fixes, |
| 21 | + etc. without violating the license or feeling weird. |
| 22 | + |
| 23 | +* When it comes to code, I'm completely comfortable with |
| 24 | + people redistributing, remixing, changing, whatever with |
| 25 | + it. I've been using the MIT license for open source stuff |
| 26 | + for decades. |
| 27 | + |
| 28 | +* When it comes to my prose and the visual design of the |
| 29 | + site, that feels a little more, I don't know, *me* than |
| 30 | + the code. The words are in my voice, and the look of the |
| 31 | + site is part of its and, by extension, my brand. |
| 32 | + |
| 33 | + I feel weird thinking about someone, say taking one of the |
| 34 | + chapters and making significant changes to it to fit their |
| 35 | + writing style while still having some of it read like it |
| 36 | + came from me. Likewise, I'd be sad to see another site |
| 37 | + online that looked exactly like mine because it reuses my |
| 38 | + stylesheets. |
| 39 | + |
| 40 | +* Because -- and this came as a total surprise to me -- |
| 41 | + there are foreign publishers interested in the |
| 42 | + translation rights to the book, I want to be careful to |
| 43 | + not be so permissive that it prevents me from signing |
| 44 | + typical contracts that give them exclusive translation |
| 45 | + rights to certain territories and languages. |
| 46 | + |
| 47 | +* If I allow the prose to be redistributed commercially, |
| 48 | + there is nothing preventing someone from slapping |
| 49 | + together a cheap print or ebook version of the book and |
| 50 | + putting it up for sale. I'm not too worried about my own |
| 51 | + sales being undercut, but I very much want to avoid |
| 52 | + readers finding themselves with a low quality book that |
| 53 | + they incorrectly think is from me. |
| 54 | + |
| 55 | + I worked very hard on this book, including type setting, |
| 56 | + layout, generating the ePub file, styling it, etc. I want |
| 57 | + you to get the best possible experience. |
| 58 | + |
| 59 | +All of this is way more complex than I'd like, especially |
| 60 | +since my brain isn't wired to care about intellectual |
| 61 | +property. I like thinking about making stuff, not thinking |
| 62 | +about the legal rights around the stuff I made. (If your |
| 63 | +brain is wired to think about legal stuff and you see that |
| 64 | +I'm doing something dumb, please do let me know.) |
| 65 | + |
| 66 | +The best solution I've been able to come up with is to use |
| 67 | +two licenses: |
| 68 | + |
| 69 | +------------------------ License(s) ------------------------ |
| 70 | + |
| 71 | +Each file in this repository falls under one of two |
| 72 | +licenses. Files whose extension is ".html", ".scss", ".css", |
| 73 | +".markdown", or ".txt" use this Creative Commons license: |
| 74 | + |
| 75 | + Attribution-NonCommercial-NoDerivatives 4.0 |
| 76 | + International (CC BY-NC-ND 4.0) |
| 77 | + |
| 78 | + https://creativecommons.org/licenses/by-nc-nd/4.0/ |
| 79 | + |
| 80 | +All other files, including (but not limited to) ".py", "h", |
| 81 | +and ".cpp" use the MIT license: |
| 82 | + |
| 83 | + Permission is hereby granted, free of charge, to any |
| 84 | + person obtaining a copy of this software and associated |
| 85 | + documentation files (the "Software"), to deal in the |
| 86 | + Software without restriction, including without |
| 87 | + limitation the rights to use, copy, modify, merge, |
| 88 | + publish, distribute, sublicense, and/or sell copies of |
| 89 | + the Software, and to permit persons to whom the Software |
| 90 | + is furnished to do so, subject to the following |
| 91 | + conditions: |
| 92 | + |
| 93 | + The above copyright notice and this permission notice |
| 94 | + shall be included in all copies or substantial portions |
| 95 | + of the Software. |
| 96 | + |
| 97 | + THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF |
| 98 | + ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED |
| 99 | + TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A |
| 100 | + PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT |
| 101 | + SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY |
| 102 | + CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION |
| 103 | + OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR |
| 104 | + IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER |
| 105 | + DEALINGS IN THE SOFTWARE. |
0 commit comments