From d44e52d3638b8dd3eaaa7958c5352976f4ffaa12 Mon Sep 17 00:00:00 2001 From: Sean Barrett Date: Tue, 14 Apr 2015 02:03:22 -0700 Subject: [PATCH] Update why_public_domain.md --- docs/why_public_domain.md | 11 +++++++---- 1 file changed, 7 insertions(+), 4 deletions(-) diff --git a/docs/why_public_domain.md b/docs/why_public_domain.md index 902e766..661ba1f 100644 --- a/docs/why_public_domain.md +++ b/docs/why_public_domain.md @@ -50,16 +50,18 @@ in the public domain: 4. discussion from stb_howto.txt on what YOU should do for YOUR libs -EASY-TO-COMPLY LICENSE +```EASY-TO-COMPLY LICENSE I make my libraries public domain. You don't have to. But my goal in releasing stb-style libraries is to reduce friction for potential users as much as possible. That means: - a. easy to build (what this file is mostly about) - b. easy to invoke (which requires good API design) - c. easy to deploy (which is about licensing) + a. easy to build (what this file is mostly about) + + b. easy to invoke (which requires good API design) + + c. easy to deploy (which is about licensing) I choose to place all my libraries in the public domain, abjuring copyright, rather than license @@ -112,3 +114,4 @@ modifying one character, and then license that however they like. (Indeed, *adding* the zlib or BSD license would be such a modification!) Unfortunately, their lawyers reportedly didn't like that answer. :( +```