Re: New License/Exception Request: MIT No Attribution


Mark Atwood (Amazon.com)
 

Hello J, 

 

While Amazon did create this license, we also found a reference to an even earlier identical independent invention of the same license text, and included a link to that document.    As to why MIT-0 instead of BSD0?, I do not know, it was before my time.  There may have been an internal legal committee discussion and rationale, but I do not have a record of it if there was.

 

..m

 

 

Mark Atwood <atwoodm@...>

Principal, Open Source

+1-206-604-2198

 

 

 

From: J Lovejoy [mailto:opensource@...]
Sent: Thursday, April 5, 2018 8:52 AM
To: Dennis Clark <dmclark@...>
Cc: Atwood, Mark <atwoodm@...>; SPDX-legal <spdx-legal@...>
Subject: Re: New License/Exception Request: MIT No Attribution

 

Mark,

 

Do I understand correctly then, that Amazon created this license?  

 

While I understand the rationale (as you explained below), which makes sense and I can see others having a similar goal. But, I’m wondering why Amazon made a new license, instead of using something that reaches the same goal and that is already out there, like: https://spdx.org/licenses/0BSD.html ?

 

 

thanks,

Jilayne

 

 

 



On Mar 28, 2018, at 11:58 AM, Dennis Clark <dmclark@...> wrote:

 

Hi Mark,

There is currently a request for this new license at  https://github.com/spdx/license-list-XML/issues/619

I don't think we have a target date for completion of the request just yet.

 

Regards,

Dennis Clark

nexB Inc.

 

On Wed, Mar 28, 2018 at 10:44 AM, Atwood, Mark via Spdx-legal <spdx-legal@...> wrote:

Hi!

* Provide a proposed Full Name for the license or exception.

MIT No Attribution

* Provide a proposed Short Identifier.

MIT-0

* Provide a functioning url reference to the license or exception text, either
from the author or a community recognized source.

https://github.com/aws/mit-0

* Create and attach a text file with the license or exception text from the
url provided.

See attached file "MIT-0".

* Indicate whether the license is OSI-approved (see:
http://www.opensource.org/licenses/alphabetical) or whether it has been
submitted for approval to the OSI and is currently under review.

Not currently OSI approved.  Not submitted for OSI approval. Not currently
under review by OSI.  We may submit this license to OSI for review at a later
date.

* Provide a short explanation regarding the need for this license or exception
to be included on the SPDX License List, including identifying at least one
program that uses this license.

This license has proven useful for code that is intended for developers to use
as reference, teaching samples, examples, or templates that other developers
may modify for their own purposes.
In many of these cases, the initial developer may not want to impose even the
cost of attribution, or the use cases may not be conducive to attribution.
The CC0 and various "do what you want" licenses and various public domain
dedications may be less attractive to the initial developer for various
reasons (i.e., a license is preferable to a public domain dedication). The MIT
license with all the attribution requirement language removed fills this need.

* Identify at least one program that uses this license.

https://github.com/awslabs/awscli-aliases


Thank you!

..m


Mark Atwood <atwoodm@...>
Principal, Open Source
+1-206-604-2198



_______________________________________________
Spdx-legal mailing list
Spdx-legal@...
https://lists.spdx.org/mailman/listinfo/spdx-legal

 

_______________________________________________
Spdx-legal mailing list
Spdx-legal@...
https://lists.spdx.org/mailman/listinfo/spdx-legal

 

Join Spdx-legal@lists.spdx.org to automatically receive all group messages.