yyc12345/stb
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update why_public_domain.md

Browse Source
This commit is contained in:
Sean Barrett 2015-04-14 02:03:22 -07:00
parent 31461003c7
commit d44e52d363
1 changed files with 7 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
docs/why_public_domain.md
View File

@ -50,7 +50,7 @@ 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
@ -58,7 +58,9 @@ 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)
I choose to place all my libraries in the public
@ -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. :(
```