-
29 March 2017
Open Source License Business Perception Reportthe pain and confusion of common open licenses, roughly quantified
-
16 February 2017
Against Legislating the Nonobviousshort-order feedback on the default contributor license in GitHub's draft terms of service
-
10 February 2017
The Mendicant Maintaineratino holy fools for Open Source
-
21 September 2016
The MIT License, Line by Line171 words every programmer should understand
-
18 September 2016
The Earl of Ethereum’s CaseWho keeps a blockchain’s conscience?
-
12 September 2016
Deal MechanicThe writing on the door.
-
20 August 2016
Emancipation by ReferenceI am just a copy of a copy of a copy. Everything I say you have read before.
-
19 August 2016
Node.js Streamsfundamental abstractions reviewed and revisited
-
08 August 2016
IP Field Guidepublicly licensed, publicly available intro for non-lawyers
-
26 July 2016
The JavaScript Joke Was on Meor, a few things learned the hard way
-
19 June 2016
Circulation PolicyConfidentiality rules and procedures for the great Common Form library in the sky
-
28 May 2016
Annotations in ContextA first attempt at useful, responsible Common Form annotations
-
13 May 2016
I Don't Want to Know What “Open Source” MeansI am he as you are he as you are me and we are all on GitHub.
-
13 May 2016
License from Who?Safe open-source licensing means more than a LICENSE file.
-
20 April 2016
The Triplebyte PlanThe tangled web of one start-up equity plan
-
18 April 2016
The Berneout PledgeSucks less than CLAs!
-
30 March 2016
First Read: The Fair Source LicenseText and my first thoughts on a new, non-open source form license
-
28 February 2016
I’ll Never Be a Super LawyerIn feigned ignorance there is no grace.
-
23 February 2016
Startup UnixAn open legal operating system for start-up technology companies
-
27 November 2015
What Enumeration MeansEnumeration is an essential contract drafting tool. Don't disclaim it!
-
27 November 2015
Template AmbiguityDocument assembly can make ambiguity even harder to spot.
-
29 October 2015
The Blanks ProblemA tough Common Form design decision explained.
-
08 October 2015
Term InjectionFighting insertion of unexpected terms in automated form contracts
-
25 September 2015
React Patent RedlineChanges to Facebook's patent grant for React, Flux, Immutable, &c.
-
10 September 2015
Certificated AssentHow signed is signed enough for a hosted software licensing deal?
-
03 September 2015
Hacking Common FormOverview of existing Common Form software for programmers
-
24 August 2015
Terms of Service; Already ReadVerifiable contracts should help consumers, too.
-
21 August 2015
Reproduction of HierarchyMarkdown isn't great for contracts. HTML5 is better.
-
15 August 2015
Index Card ContractsCommon Form for paper people
-
14 August 2015
Grab-Bag ContractsMight we write contracts like we fill shopping bags at the grocery store?
-
01 August 2015
Named ProvisionsIf contract section numbers are just another namespace, can they be replaced with defined terms?
-
31 July 2015
vesting.jsFrom code to law and back again
-
22 May 2015
Blind PatchesWhat if open-source contributors could submit patches anonymously and choose to claim credit later?
-
18 May 2015
Modularity is not the LawAncient and modern principles of contract interpretation work against contracts made of modular parts
-
17 May 2015
The Halliburton HypothesisQuantifying the negotiating process to mount attacks on the confidentiality of a public contract forms repository
-
20 April 2015
Value Statementas found at the feet of my bills
-
13 February 2015
FTC 2014 Year in ReviewWhat do the FTC’s 2014 privacy and security enforcement actions teach tech companies?
-
09 February 2015
Common FormComposable, verifiable, shareable form contracts for the modern practice of law
-
22 January 2015
deflect.jsAn ECMAScript module fusing Node.js error-first convention with continuation passing style, plus a twist to make composed stacks of asynchronous functions dynamic
-
23 October 2014
Deep Data Privacy RiskCheap storage technology isn't just changing what information we store; it's also changing how we store familiar kinds of information. Both developments have implications for privacy.
/dev/lawyer
>> Law, technology, and the space between
All content by Kyle E. Mitchell, who is not your attorney.