We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
There was an error while loading. Please reload this page.
1 parent 0fdb9e9 commit 0fa7cc5Copy full SHA for 0fa7cc5
1 file changed
docs/04_1_Creating_Binding_Agreements.md
@@ -294,6 +294,12 @@ curl -q https://www.apache.org/licenses/LICENSE-2.0.txt > envelopes/license-apac
294
shasum -a 256 envelopes/license-apache-4-01.txt > envelopes/license-apache-4-01-hash.txt
295
```
296
297
+That hash is essentially a proof of the license: Ben can later offer
298
+the license and show it hashes to the shasum he incudes in the
299
+CLA. It's the same methodology as used to created commitments, but in
300
+this case Ben is committing to the text of a file, mainly for legal
301
+clarity. (More on that in §4.2.)
302
+
303
Ben's CLA includes a subenvelope with a clear definition of the
304
license. (Remember, envelopes are usually built from the inside out.)
305
0 commit comments