[License-discuss] License Committee Report - 2013-03-06

2013-03-06 Thread Luis Villa
[After an absence of some time, the board has asked me to resurrect the formal license committee reports. This is the first one. Comments and suggestions on format, content, etc. are welcome.] This email is my report for licenses currently submitted to the OSI. If anybody disagrees with my

Adaptive Public License Re: License Committee Report v2

2004-04-15 Thread Ernest Prabhakar
On Apr 14, 2004, at 11:26 PM, Russell Nelson wrote: Unfortunately, even after two tries there have been insufficient comments on the Adaptive Public License. Maybe the third's the charm? Title: Adaptive Public License Submission: http://www.crynwr.com/cgi-bin/ezmlm-cgi?3:mss:6913:200305:

License Committee Report

2004-04-14 Thread Russell Nelson
I'm the chair of the license approval committee. This is my report for the current set of licenses under discussion. If anybody disagrees with my assessment of the committee's conclusions, say so promptly. -- Restricts license termination to only if the original work is alleged to infringe a

RE: License Committee Report

2004-04-14 Thread =?ISO-8859-1?Q?Rod=20Dixon=2C=20J=2ED=2E=2C=20LL=2EM=2E?=
Committee Report I'm the chair of the license approval committee. This is my report for the current set of licenses under discussion. If anybody disagrees with my assessment of the committee's conclusions, say so promptly. -- Restricts license termination to only if the original work is alleged

Re: License Committee Report

2004-04-14 Thread Carmen Leeming
Hi Russell. I am still hoping to get approval for the Adaptive Public License. I have attached our follow-up from the last License Committee Report. --Carmen Leeming Carmen Leeming writes: Title: Adaptive Public License Submission: http://www.crynwr.com/cgi-bin/ezmlm-cgi?3:mss:6913

License Committee Report v2

2004-04-14 Thread Russell Nelson
[ note the addition of the Adaptive Public License at the end. There have STILL not been sufficient comments on the Adaptive Public License. -russ ] I'm the chair of the license approval committee. This is my report for the current set of licenses under discussion. If anybody disagrees with

Re: License Committee report

2004-02-22 Thread Russell Nelson
[EMAIL PROTECTED] writes: I'm the chair of the license approval committee. This is my report for the current set of licenses under discussion. If anybody disagrees with my assessment of the committee's conclusions, say so promptly. The board voted on Thursday afternoon to accept the

Re: License Committee report

2004-02-21 Thread Ben Reser
On Tue, Feb 17, 2004 at 08:20:49PM -0500, Russell Nelson wrote: There is much discussion spent deciding whether NASA can copyright software at all. The license itself says that no copyright is claimed in the United States. The only serious concern that I can see is that the license

Re: License Committee report

2004-02-19 Thread James William Pye
On 02/17/04:07/2, Russell Nelson wrote: This must surely be the shortest open source license ever! Still, we should send it back to the author because he uses the hated word utilize. Don't use utilize! Utilize use instead. Means the same thing and avoids a phony formality. Title: Fair

Re: License Committee report

2004-02-19 Thread James William Pye
Just to precede my statements with a warning that they are as it seems to me. I am not a lawyer, so my opinions could use any [dis|]qualifications. On 02/17/04:07/2, Zooko O'Whielacronx wrote: Does the Fair License require the software developer who uses such licensed source code to inform his

Re: License Committee report

2004-02-18 Thread Ian Lance Taylor
Alex Rousskov [EMAIL PROTECTED] writes: While I agree with the goals of the license author, he's putting restrictions on the use of the software, and restrictions on use are not allowed. He points to other licenses which restrict some modifications, but they do it at redistribution time,

Re: License Committee report - regarding NASA Open Source Agreement Version 1.1

2004-02-18 Thread Rod Dixon, J.D., LL.M.
I think the NASA Open Source Agreement is worthy of OSI's approval - - with revision, but it also raises issues worthy of discussion and, perhaps, adjustment to the OSD since the internationalization of intellectual property law will likely raise similar open source licensing issues for other

Re: License Committee report - regarding NASA Open Source Agreement Version 1.1

2004-02-18 Thread Brian Behlendorf
On Wed, 18 Feb 2004, Rod Dixon, J.D., LL.M. wrote: Regarding the issue concerning whether NASA may license software it cannot copyright in the U.S., the answer is yes, notwithstanding that significant harm to the conception of public domain for digital works is likely to follow. And if

Re: License Committee report

2004-02-18 Thread Carmen Leeming
My license does not appear on your list: Title: Adaptive Public License Submission: http://www.crynwr.com/cgi-bin/ezmlm-cgi?3:mss:6913:200305:bogcdnbbhnfbgpdeahob License: http://www.mamook.net/APL.html This license was submitted in May 2003. I checked in June to make sure that the license

Re: License Committee report

2004-02-18 Thread Russell Nelson
Zooko O'Whielacronx writes: So if I understand correctly, the Simple Permissive License and the (ideally edited) Fair License both pass the litmus test of OSD. In addition to approving licenses which meet the OSD, the OSI also prefers to slow the proliferation of substantially similar

Re: License Committee report

2004-02-18 Thread Russell Nelson
Carmen Leeming writes: Title: Adaptive Public License Submission: http://www.crynwr.com/cgi-bin/ezmlm-cgi?3:mss:6913:200305:bogcdnbbhnfbgpdeahob License: http://www.mamook.net/APL.html This license was submitted in May 2003. I checked in June to make sure that the license had

License Committee report

2004-02-17 Thread Russell Nelson
I'm the chair of the license approval committee. This is my report for the current set of licenses under discussion. If anybody disagrees with my assessment of the committee's conclusions, say so promptly. -- We've sat on this license submission for far too long. It's a clever and innovative

Re: License Committee report

2004-02-17 Thread Zooko O'Whielacronx
This must surely be the shortest open source license ever! Still, we should send it back to the author because he uses the hated word utilize. Don't use utilize! Utilize use instead. Means the same thing and avoids a phony formality. Title: Fair License Submission: Original:

Re: License Committee report

2004-02-17 Thread Alex Rousskov
On Tue, 17 Feb 2004, Russell Nelson wrote: While I agree with the goals of the license author, he's putting restrictions on the use of the software, and restrictions on use are not allowed. He points to other licenses which restrict some modifications, but they do it at redistribution time,

Re: License Committee report

2004-02-17 Thread Richard Schilling
On 2004.02.17 17:43 Zooko O'Whielacronx wrote: [snip] So if I understand correctly, the Simple Permissive License and the (ideally edited) Fair License both pass the litmus test of OSD. In addition to approving licenses which meet the OSD, the OSI also prefers to slow the proliferation of