├── CNAME
├── Cakefile
├── FAQ.md
├── LICENSE
├── index.html
└── v1.html


/CNAME:
--------------------------------------------------------------------------------
1 | lillicense.org


--------------------------------------------------------------------------------
/Cakefile:
--------------------------------------------------------------------------------
 1 | # `cake build` rebuilds index.html from the contents of LICENSE and FAQ.md
 2 | #
 3 | # Handy shcortcut to build live as you work:
 4 | # fswatch -o LICENSE FAQ.md | xargs -n1 -I{} cake build
 5 | 
 6 | fs = require 'fs'
 7 | md = require('markdown-it')()
 8 | 
 9 | wrap = (parts) ->
10 |   body = parts.slice(1).map((part) -> "<p>#{part}</p>").join('\n\n')
11 |   "\n\n<h1>#{parts.shift()}</h1>\n\n#{ body }\n\n"
12 | 
13 | section = (name, html) ->
14 |   "<div class=\"#{name}\">#{html}</div>"
15 | 
16 | matcher = (name) ->
17 |   ///<div\sclass="#{name}">[\s\S]*?<\/div>///
18 | 
19 | task 'build', 'build the HTML source from the LICENSE file', ->
20 |   source = fs.readFileSync('LICENSE').toString().split(/\n{2,}/g)
21 |   faq    = fs.readFileSync('FAQ.md').toString()
22 |   v1     = fs.readFileSync('v1.html').toString()
23 | 
24 |   v1 = v1.replace matcher('lil-license'), section('lil-license', wrap(source))
25 |   v1 = v1.replace matcher('faq'), section('faq', md.render(faq))
26 | 
27 |   fs.writeFileSync 'v1.html', v1
28 | 


--------------------------------------------------------------------------------
/FAQ.md:
--------------------------------------------------------------------------------
 1 | FAQ
 2 | ---
 3 | 
 4 | Why publish yet another license? Why not just use [MIT](http://mitlicense.org)?
 5 | 
 6 | It's true that license proliferation is a real problem. And the MIT License
 7 | is lovely: functional, relatively clear in intent to all readers — not just
 8 | lawyers — and has stood the test of time.
 9 | [Roughly half](https://github.com/blog/1964-open-source-license-usage-on-github-com)
10 | of all open source projects use it. But it was written in the 1980s, and as open
11 | source authors and users we've learned that, in practice, we need just a little
12 | bit more: a declaration of the intent not to use software patents against users,
13 | and the shared understanding that contributions back to the project will be
14 | incorporated under the same terms of the license.
15 | 
16 | 
17 | What else is different about the Lil License?
18 | 
19 | Some of the legal phrasing has been simplified, the [legally UNNECESSARY SHOUTY
20 | TEXT](https://www.cameronhuff.com/blog/why-not-use-CAPITAL-LETTERS/index.html)
21 | quieted, and the words generally boiled down to a bare minimum. You may
22 | include the license verbatim or link to it instead, and there's also a bit about
23 | having no obligations to provide support or updates to your code.
24 | 
25 | 
26 | This license won't work for my project because of [ ... ]. Can I fix it?
27 | 
28 | You certainly can. Although we've put significant care and thought into the
29 | precise formulation of this license, there's no reason why it shouldn't be made
30 | even better. In fact, the "Lil" stands for "Lil Improvable License". Go ahead
31 | and make your changes. If you think they'd benefit everyone, please submit them
32 | [on Github](https://github.com/jashkenas/lil-license). The goal here is to
33 | whittle this thing down to a minimal social and legal contract among authors,
34 | contributors and users of open source. In plain English.
35 | 
36 | 
37 | This license is a terrible idea. We need something more legally robust!
38 | 
39 | If you're looking for a tried and tested, every term defined, dot the i's and
40 | cross the t's, permissive open source license, try [the Apache
41 | License](https://www.apache.org/licenses/LICENSE-2.0). It will serve you well.
42 | 
43 | 
44 | This license is a terrible idea. Software authors need to be able to be paid for
45 | their work!
46 | 
47 | Check out [License Zero](https://licensezero.com/). It helps software stay free
48 | for use and modification for non-commercial purposes, while commercial users
49 | can be required to pay after a trial period.
50 | 
51 | 
52 | I decided to license my project under the LIL. Does anyone care?
53 | 
54 | We do. Please take a moment to
55 | [add it to the wiki](https://github.com/jashkenas/lil-license/wiki/List-of-LIL-Licensed-Projects).
56 | 


--------------------------------------------------------------------------------
/LICENSE:
--------------------------------------------------------------------------------
 1 | The Lil License v1
 2 | 
 3 | Copyright (c) [years] [authors]
 4 | 
 5 | Permission is hereby granted by the authors of this software, to any person,
 6 | to use the software for any purpose, free of charge, including the rights
 7 | to run, read, copy, change, distribute and sell it, and including usage rights
 8 | to any patents the authors may hold on it, subject to the following conditions:
 9 | 
10 | This license, or a link to its text, must be included with all copies of
11 | the software and any derivative works.
12 | 
13 | Any modification to the software submitted to the authors may be incorporated
14 | into the software under the terms of this license.
15 | 
16 | The software is provided "as is", without warranty of any kind, including
17 | but not limited to the warranties of title, fitness, merchantability and
18 | non-infringement. The authors have no obligation to provide support or updates
19 | for the software, and may not be held liable for any damages, claims or other
20 | liability arising from its use.
21 | 


--------------------------------------------------------------------------------
/index.html:
--------------------------------------------------------------------------------
 1 | <!DOCTYPE html>
 2 | <html>
 3 |  <head>
 4 |    <title>The Lil License (Current Version)</title>
 5 |    <meta http-equiv="refresh" content="0;URL='http://lillicense.org/v1.html'" />
 6 |  </head>
 7 |  <body>
 8 |    <p>
 9 |      The current version of the Lil License is
10 |      <a href="http://lillicense.org/v1.html">v1</a>.
11 |    </p>
12 |  </body>
13 | </html>
14 | 


--------------------------------------------------------------------------------
/v1.html:
--------------------------------------------------------------------------------
  1 | <!DOCTYPE html>
  2 | <html>
  3 | <head>
  4 |   <meta charset="UTF-8">
  5 |   <meta name=viewport content="width=device-width, initial-scale=1">
  6 |   <title>The Lil License</title>
  7 | 
  8 |   <link href="https://fonts.googleapis.com/css?family=Droid+Sans+Mono|Open+Sans" rel="stylesheet">
  9 |   <style>
 10 | 
 11 |     body {
 12 |   	  background: #fff;
 13 |   	  color: #000;
 14 |       font-family: 'Open Sans', "Helvetica Neue", Helvetica, Arial, sans-serif;
 15 |       max-width: 660px;
 16 |       margin: 0 auto;
 17 |       padding: 0 10px;
 18 |       font-size: 14px;
 19 |       line-height: 1.5em;
 20 |     }
 21 | 
 22 |     .lil-license {
 23 |       font-family: 'Droid Sans Mono', Menlo, Monaco, Consolas, monospace;
 24 |       margin: 80px 0 80px;
 25 |       border-bottom: 1px solid #e5e5e5;
 26 |       padding-bottom: 80px;
 27 |     }
 28 |       .lil-license h1 {
 29 |         font-weight: normal;
 30 |         font-size: 30px;
 31 |         line-height: 35px;
 32 |         margin-bottom: 30px;
 33 |       }
 34 | 
 35 |     .faq {
 36 |       max-width: 550px;
 37 |       margin: 0 auto 50px;
 38 |       color: #666;
 39 |       font-size: 16px;
 40 |       line-height: 24px;
 41 |     }
 42 |       .faq a {
 43 |         color: #666;
 44 |       }
 45 |       .faq h2 {
 46 |         font-size: 24px;
 47 |         text-align: center;
 48 |         margin: 0 0 30px;
 49 |       }
 50 |       .faq p {
 51 |         margin: 10px 0 40px;
 52 |         color: #888;
 53 |       }
 54 |       .faq p:nth-child(even) {
 55 |         color: #666;
 56 |         font-style: italic;
 57 |         margin: 10px 0 0;
 58 |       }
 59 | 
 60 |     .credits {
 61 |       max-width: 550px;
 62 |       margin: 75px auto;
 63 |       font-size: 12px;
 64 |       color: #666;
 65 |     }
 66 |       .credits a {
 67 |         color: #666;
 68 |       }
 69 | 
 70 |     /* Mobile */
 71 |     @media (max-width: 500px) {
 72 |       .lil-license {
 73 |         margin: 30px 0 40px;
 74 |         padding-bottom: 40px;
 75 |       }
 76 |       .lil-license h1 {
 77 |         font-size: 26px;
 78 |       }
 79 |       .faq {
 80 |         margin-bottom: 50px;
 81 |       }
 82 |     }
 83 | 
 84 |   </style>
 85 | </head>
 86 | 
 87 | <body>
 88 | 
 89 | <!--
 90 |   Note: This file is built from the LICENSE and FAQ.md files with `cake build`.
 91 |   If you're making changes, please make them there, not here.
 92 | -->
 93 | <div class="lil-license">
 94 | 
 95 | <h1>The Lil License v1</h1>
 96 | 
 97 | <p>Copyright (c) [years] [authors]</p>
 98 | 
 99 | <p>Permission is hereby granted by the authors of this software, to any person,
100 | to use the software for any purpose, free of charge, including the rights
101 | to run, read, copy, change, distribute and sell it, and including usage rights
102 | to any patents the authors may hold on it, subject to the following conditions:</p>
103 | 
104 | <p>This license, or a link to its text, must be included with all copies of
105 | the software and any derivative works.</p>
106 | 
107 | <p>Any modification to the software submitted to the authors may be incorporated
108 | into the software under the terms of this license.</p>
109 | 
110 | <p>The software is provided "as is", without warranty of any kind, including
111 | but not limited to the warranties of title, fitness, merchantability and
112 | non-infringement. The authors have no obligation to provide support or updates
113 | for the software, and may not be held liable for any damages, claims or other
114 | liability arising from its use.
115 | </p>
116 | 
117 | </div>
118 | 
119 | <div class="faq"><h2>FAQ</h2>
120 | <p>Why publish yet another license? Why not just use <a href="http://mitlicense.org">MIT</a>?</p>
121 | <p>It's true that license proliferation is a real problem. And the MIT License
122 | is lovely: functional, relatively clear in intent to all readers — not just
123 | lawyers — and has stood the test of time.
124 | <a href="https://github.com/blog/1964-open-source-license-usage-on-github-com">Roughly half</a>
125 | of all open source projects use it. But it was written in the 1980s, and as open
126 | source authors and users we've learned that, in practice, we need just a little
127 | bit more: a declaration of the intent not to use software patents against users,
128 | and the shared understanding that contributions back to the project will be
129 | incorporated under the same terms of the license.</p>
130 | <p>What else is different about the Lil License?</p>
131 | <p>Some of the legal phrasing has been simplified, the <a href="https://www.cameronhuff.com/blog/why-not-use-CAPITAL-LETTERS/index.html">legally UNNECESSARY SHOUTY
132 | TEXT</a>
133 | quieted, and the words generally boiled down to a bare minimum. You may
134 | include the license verbatim or link to it instead, and there's also a bit about
135 | having no obligations to provide support or updates to your code.</p>
136 | <p>This license won't work for my project because of [ ... ]. Can I fix it?</p>
137 | <p>You certainly can. Although we've put significant care and thought into the
138 | precise formulation of this license, there's no reason why it shouldn't be made
139 | even better. In fact, the &quot;Lil&quot; stands for &quot;Lil Improvable License&quot;. Go ahead
140 | and make your changes. If you think they'd benefit everyone, please submit them
141 | <a href="https://github.com/jashkenas/lil-license">on Github</a>. The goal here is to
142 | whittle this thing down to a minimal social and legal contract among authors,
143 | contributors and users of open source. In plain English.</p>
144 | <p>This license is a terrible idea. We need something more legally robust!</p>
145 | <p>If you're looking for a tried and tested, every term defined, dot the i's and
146 | cross the t's, permissive open source license, try <a href="https://www.apache.org/licenses/LICENSE-2.0">the Apache
147 | License</a>. It will serve you well.</p>
148 | <p>This license is a terrible idea. Software authors need to be able to be paid for
149 | their work!</p>
150 | <p>Check out <a href="https://licensezero.com/">License Zero</a>. It helps software stay free
151 | for use and modification for non-commercial purposes, while commercial users
152 | can be required to pay after a trial period.</p>
153 | <p>I decided to license my project under the LIL. Does anyone care?</p>
154 | <p>We do. Please take a moment to
155 | <a href="https://github.com/jashkenas/lil-license/wiki/List-of-LIL-Licensed-Projects">add it to the wiki</a>.</p>
156 | </div>
157 | 
158 | <div class="credits">
159 |   Credits and inspiration:
160 |   <a href="https://mitlicense.org/">MIT</a>,
161 |   <a href="https://www.apache.org/licenses/LICENSE-2.0">Apache</a>,
162 |   <a href="https://opensource.org/licenses/PostgreSQL">Postgres</a>,
163 |   <a href="https://opensource.org/licenses/ISC">ISC</a>,
164 |   <a href="https://oss.kemitchell.com/">Kyle</a>
165 |   <a href="https://writing.kemitchell.com/2016/09/21/MIT-License-Line-by-Line.html">Mitchell</a>, and
166 |   <a href="http://www.abajournal.com/magazine/article/ax_these_terms_from_your_legal_writing/">clear</a>
167 |   <a href="http://law.tm/froomkins-legal-writing-tips-2/">legal</a>
168 |   <a href="https://www.law360.com/articles/748868/6-types-of-legal-mumbo-jumbo-attorneys-must-avoid">writing</a>.
169 | </div>
170 | 
171 | </body>
172 | 


--------------------------------------------------------------------------------