Subject: For approval: a) MirOS Licence Template b) OpenBSD license template (2nd RESEND) (was Re: ISC copyright for BIND) (was Re: For approval: MirOS Licence Template (and question about others))
From: Thorsten Glaser <tg@66h.42h.de>
Date: Fri, 22 Oct 2004 16:05:51 +0000 (UTC)
Fri, 22 Oct 2004 16:05:51 +0000 (UTC)
Second RESEND - looks like posting to the gmane interface doesn't work;
this time trying direct eMail to the list.

Zvezdan Petkovic dixit:

>> On a related notice, did my other mails not get through?

>I didn't receive any.

Okay, I'll resend them hereby, please process ;-)
(once we'll receive the Okay from OSI, I'll provide you
 with the final version as HTML and ASCII, as requested)




Date: Tue, 12 Oct 2004 14:02:49 +0000 (UTC)
Subject: Re: For approval: MirOS Licence Template (and question about others)

John Cowan dixit:

>Thorsten Glaser scripsit:
>
>> With due respect, I would like the OSI to consider to
>> certify the "MirOS Licence Template" as shown on

>> http://mirbsd.bsdadvocacy.org/cvs.cgi/~checkout~/src/share/misc/licence.template?rev=HEAD

This will be updated in a few hours with the full file by a cronjob.
I've attached the fixed version.

>In my judgment, this license is obviously Open Source (and Free)
>and should be fast-tracked for OSI approval.

Thanks.

>A few typos:  s/publically/publicly, s/commata/commas.  In
>addition, there are some bad hyphenations: re-tained, not retai-ned;
>addition-al, not additio-nal; temp-late, not templa-te.

Good to hear that; fixed them except "commata" which I do want to
retain because the word has a Latin origin. (Shouldn't matter to
the discussion though, because it's in the explanatory text.)

>> a) any derivate of the original UCB/BSD licence, with
>>    clauses left out, or wording slightly changed (e.g.
>>    by putting in one's name)
>
>In general, no, except that you can replace ORGANIZATION, OWNER, and YEAR
>with the correct values.  But omitting clauses, no.  The canonical version
>for OSI purposes is at http://opensource.org/licenses/bsd-license.php .

Why? It's pretty common to leave out clause 3; most also leave out clause
4; some leave out clauses 2 and 3 but not 4 (I've seen that when checking
for MirPorts), and minimal changes to the disclaimer "should" not be too
worrysome.

Of couse, if that's OSI policy, we'll have to live with it; in that case
I'll pick out the special cases and mail them.

>> b) the following:
>> 
>> # Copyright (c) 2003 ...
>> # Permission to use, copy, modify, and distribute this software for any
>> # purpose with or without fee is hereby granted, provided that the above
>> # copyright notice and this permission notice appear in all copies.
>> # (disclaimer from BSD licence)
>> 
>> (see http://www.openbsd.org/cgi-bin/cvsweb.cgi/~checkout~/src/share/misc/license.template?rev=HEAD
>
>This is not the BSD license, but it is IMO Open Source, and should be
>assigned a name and then fast-tracked for approval.

The name is (new) "OpenBSD license template". I don't believe they
have got versions on them; for the "MirOS licence template" (notice
English spelling, not American) we're using the RCS revision number.

Thanks,
//mirabile



Date: Fri, 15 Oct 2004 14:39:00 +0000 (UTC)
From: Thorsten Glaser <tg-QuxvC+XXJv6ELgA04lAiVw@public.gmane.org>
Subject: Re: For approval: MirOS Licence Template

Dixi:

>>I've attached the fixed version.

>Here you are.

I'd like to know about this 'fast-track for approval'
process a little bit more.

When can we (the MirOS Project and the OpenBSD project)
expect a decision or an answer? (I'm just asking about
approximate values, mostly for curiosity (although our
next release is due in about 1-2 months).)

bye,
//mirabile



Date: Tue, 12 Oct 2004 18:59:56 +0000 (UTC)
From: Thorsten Glaser <tg-QuxvC+XXJv6ELgA04lAiVw@public.gmane.org>
Subject: Re: For approval: MirOS Licence Template (and question about others)

Russell Nelson dixit:

>Yes, you have to live with it.  It's a certification mark and we have
>to control how it's used.  If we lose or give up that control, then
>it's not a certification mark anymore.

I've got absolutely no problem with actually doing that, I was
more like _exploring_ what I have got to do for the certification
mark, and trying to narrow it down to as few actual work (for all
of us) as possible.

But the argumentation has a point, so it's settled now.

bye,
//mirabile

/*-
 * Copyright (c) year, year...
 *	First M. Last <user@host.domain>
 *
 * Licensee is hereby permitted to deal in this work without restric-
 * tion, including unlimited rights to use, publicly perform, modify,
 * merge, distribute, sell, give away or sublicence, provided all co-
 * pyright notices above, these terms and the disclaimer are retained
 * in all redistributions or reproduced in accompanying documentation
 * or other materials provided with binary redistributions.
 *
 * Licensor hereby provides this work "AS IS" and WITHOUT WARRANTY of
 * any kind, expressed or implied, to the maximum extent permitted by
 * applicable law, but with the warranty of being written without ma-
 * licious intent or gross negligence; in no event shall licensor, an
 * author or contributor be held liable for any damage, direct, indi-
 * rect or other, however caused, arising in any way out of the usage
 * of covered work, even if advised of the possibility of such damage.
 */

Below is an example license to be used for new code in OpenBSD,
modeled after the ISC license.

It is important to specify the year of the copyright.  Additional years
should be separated by a comma, e.g.
    Copyright (c) 2003, 2004

If you add extra text to the body of the license, be careful not to
add further restrictions.

/*
 * Copyright (c) CCYY YOUR NAME HERE <user@your.dom.ain>
 *
 * Permission to use, copy, modify, and distribute this software for any
 * purpose with or without fee is hereby granted, provided that the above
 * copyright notice and this permission notice appear in all copies.
 *
 * THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES
 * WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF
 * MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR
 * ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
 * WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN
 * ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF
 * OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
 */