From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/319 Path: news.gmane.org!not-for-mail From: Solar Designer Newsgroups: gmane.linux.lib.musl.general Subject: Re: Unit tests Date: Mon, 2 May 2011 17:27:49 +0400 Message-ID: <20110502132749.GA18254@openwall.com> References: <20110410044515.GB13185@brightrain.aerifal.cx> <87bozlv621.fsf@gmail.com> <20110502124922.GA17994@openwall.com> <201105020602.15342.errno@cox.net> Reply-To: musl@lists.openwall.com NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: dough.gmane.org 1312595722 11582 80.91.229.12 (6 Aug 2011 01:55:22 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Sat, 6 Aug 2011 01:55:22 +0000 (UTC) To: musl@lists.openwall.com Original-X-From: envelope-from@hidden Mon May 02 13:28:09 2011 Content-Disposition: inline In-Reply-To: <201105020602.15342.errno@cox.net> User-Agent: Mutt/1.4.2.3i Xref: news.gmane.org gmane.linux.lib.musl.general:319 Archived-At: On Mon, May 02, 2011 at 06:02:15AM -0700, errno wrote: > Have you considered cc0? > > http://creativecommons.org/about/cc0 Not really, although I had heard of it. I just took a closer look, and I think that it's a poor choice for software: an uncommon choice (CC0 specifically), lengthy full legal text (too long given the very simple spirit and purpose), and might be tricky to apply when there are multiple authors (and new ones joining development). Summary: http://creativecommons.org/publicdomain/zero/1.0/ (notice "the person", which we might need to edit when we have a second contributor to the code). Full text: http://creativecommons.org/publicdomain/zero/1.0/legalcode I did use public domain statements along with license fallback, which is similar to CC0's approach, for some of my own works, e.g.: http://openwall.info/wiki/people/solar/software/public-domain-source-code/md5 but this gets tricky when there are multiple authors, and lately I tend to consider it an unneeded complication compared to going with copyright and a purely-permissive license right away (my choice so far is cut-down BSD, but cut-down ISC will work as well). Alexander