From: Christian Neukirchen <chneukirchen@gmail.com>
To: musl@lists.openwall.com
Subject: Re: Unit tests
Date: Mon, 02 May 2011 10:51:34 +0200 [thread overview]
Message-ID: <87bozlv621.fsf@gmail.com> (raw)
In-Reply-To: <20110501193650.GA1723@openwall.com> (Solar Designer's message of
Solar Designer <solar@openwall.com> writes:
> On Fri, Apr 29, 2011 at 01:54:42PM +0200, Christian Neukirchen wrote:
>> Solar Designer <solar@openwall.com> writes:
>>
>> > What license is it going to be under? I propose cut-down BSD (to the
>> > point of being copyright only, with no restrictions):
>> >
>> > This software is Copyright (c) YEAR YOUR NAME <your at e-mail.address>,
>> > and it is hereby released to the general public under the following terms:
>> >
>> > Redistribution and use in source and binary forms, with or without
>> > modification, are permitted.
>> >
>> > This should be compatible with any other Open Source license, which I
>> > think is a plus. We currently use this for contributions to JtR:
>> >
>> > http://openwall.info/wiki/john/licensing
>> >
>> > I see little reason to have GPL-like restrictions on the unit tests;
>> > I think that would do more harm than good.
>>
>> A court-proven formulation of this is the
>> http://en.wikipedia.org/wiki/ISC_license I think.
>
> What do you mean by it being court-proven? (There's probably something
> I am not aware of, which is not surprising given that I'm not really
> into licensing.)
>
> I dislike the requirement "... provided that the above copyright notice
> and this permission notice appear in all copies." I am not a lawyer,
> but I think this doesn't allow derived versions to be placed under
> certain other licenses (that would not give the same rights).
The ISC license is widely used (BIND, new OpenBSD stuff...) and thus a
lawyer has looked over it, which generally is not true for "own"
licenses.
> Alexander
--
Christian Neukirchen <chneukirchen@gmail.com> http://chneukirchen.org
next prev parent reply other threads:[~2011-05-02 8:51 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-10 4:45 Simple testing task - string functions Rich Felker
2011-04-10 12:08 ` Luka Marčetić
2011-04-10 15:25 ` JIghtuse
2011-04-10 15:34 ` Rich Felker
2011-04-10 15:46 ` keep discussion threads separate (was: Simple testing task - string functions) Solar Designer
2011-04-14 17:59 ` Simple testing task - string functions Luka Marčetić
2011-04-14 23:11 ` Rich Felker
2011-04-18 12:20 ` Luka Marčetić
2011-04-25 19:34 ` Unit tests Luka Marčetić
2011-04-26 19:14 ` Solar Designer
2011-04-27 0:32 ` Rich Felker
2011-04-27 0:42 ` Rich Felker
2011-04-27 6:29 ` Luka Marčetić
2011-04-29 5:36 ` Solar Designer
2011-04-29 11:54 ` Christian Neukirchen
2011-05-01 19:36 ` Solar Designer
2011-05-02 8:51 ` Christian Neukirchen [this message]
2011-05-02 12:49 ` Solar Designer
2011-05-02 13:02 ` errno
2011-05-02 13:11 ` Rich Felker
2011-05-02 13:30 ` Solar Designer
2011-05-02 13:32 ` Rich Felker
2011-05-02 13:52 ` Solar Designer
2011-05-02 13:27 ` Solar Designer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87bozlv621.fsf@gmail.com \
--to=chneukirchen@gmail.com \
--cc=musl@lists.openwall.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).