|
3.1 release
+1 to ISO8601
By
Mark Atwood (Amazon.com)
· #2248
·
|
|
New License/Exception Request: MIT No Attribution
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,
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,
|
By
Mark Atwood (Amazon.com)
· #2249
·
|
|
New License/Exception Request: MIT No Attribution
Ha, you had gotten ahead of me, I didn’t realize you had already started the process after our conversations. We prefer the long name be “MIT No Attribution”. We (Amazon and AWS) very much prefer that
Ha, you had gotten ahead of me, I didn’t realize you had already started the process after our conversations. We prefer the long name be “MIT No Attribution”. We (Amazon and AWS) very much prefer that
|
By
Mark Atwood (Amazon.com)
· #2251
·
|
|
New License/Exception Request: MIT No Attribution
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 MI
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 MI
|
By
Mark Atwood (Amazon.com)
· #2257
·
|
|
New License/Exception Request: Python Imaging Library License
Provide a proposed Full Name for the license or exception. Python Imaging Library License Provide a proposed Short Identifier. PILL Provide a functioning url reference to the license or exception text
Provide a proposed Full Name for the license or exception. Python Imaging Library License Provide a proposed Short Identifier. PILL Provide a functioning url reference to the license or exception text
|
By
Mark Atwood (Amazon.com)
· #2502
·
|
|
the freenode.net/#spdx channel seems to be dead, is there an official SPDX chat venue? <EOM>
By
Mark Atwood (Amazon.com)
· #2515
·
|
|
A proposal for SPDX Private License Identifiers. Example: .com.amazon.-.ASL-2.0
I would like to propose a syntax for SPDX "Private License Identifiers". SPDX short identifiers and SPDX-License-Identifier declarations in source code and in compliance documents have proven to be us
I would like to propose a syntax for SPDX "Private License Identifiers". SPDX short identifiers and SPDX-License-Identifier declarations in source code and in compliance documents have proven to be us
|
By
Mark Atwood (Amazon.com)
· #2530
·
|
|
A proposal for SPDX Private License Identifiers. Example: .com.amazon.-.ASL-2.0
Just following up, does anyone have any comments or suggestions for my proposal for SPDX Private License Identifiers?
Just following up, does anyone have any comments or suggestions for my proposal for SPDX Private License Identifiers?
|
By
Mark Atwood (Amazon.com)
· #2533
·
|
|
Minutes from 6 Feb 2019 tech call
Thank you Gary and Kate. I’ve reviewed the minutes, and look forward to discussing the topic. As you may guess, my strong basis is towards self-assigned DNS-based namespace with optional registration.
Thank you Gary and Kate. I’ve reviewed the minutes, and look forward to discussing the topic. As you may guess, my strong basis is towards self-assigned DNS-based namespace with optional registration.
|
By
Mark Atwood (Amazon.com)
· #2542
·
|
|
Proposed: two methods for for organizations to self-declare SPDX license identifiers.
As discussed at the SPDX meeting prior to OSLS two weeks ago. Proposed: two methods for for organizations to self-declare SPDX license identifiers. The two methods will be referred to a “organization
As discussed at the SPDX meeting prior to OSLS two weeks ago. Proposed: two methods for for organizations to self-declare SPDX license identifiers. The two methods will be referred to a “organization
|
By
Mark Atwood (Amazon.com)
· #2577
·
|
|
New License/Exception Request: selinux-nsa-declaration
1. Provide a proposed Full Name for the license or exception. selinux-nsa-declaration-1.0 2. Provide a proposed Short Identifier. selinux-nsa-declaration-1.0 3. https://github.com/SELinuxProject/selin
1. Provide a proposed Full Name for the license or exception. selinux-nsa-declaration-1.0 2. Provide a proposed Short Identifier. selinux-nsa-declaration-1.0 3. https://github.com/SELinuxProject/selin
|
By
Mark Atwood (Amazon.com)
· #2717
·
|
|
Chime instead of Zoom, a modest proposal
Hi Kate and other SPDX folk, We have been using Zoom to provide teleconference for SPDX meetings. In light of recent events, Zoom has gotten very popular, and also been failing many security audits, a
Hi Kate and other SPDX folk, We have been using Zoom to provide teleconference for SPDX meetings. In light of recent events, Zoom has gotten very popular, and also been failing many security audits, a
|
By
Mark Atwood (Amazon.com)
· #2777
·
|
|
FW: Invalid SPDX identifier in Linux source tree
I just got this note from one of my developers. Is he correct? Should we or someone send a patch to Linux project? ..m
I just got this note from one of my developers. Is he correct? Should we or someone send a patch to Linux project? ..m
|
By
Mark Atwood (Amazon.com)
· #2800
·
|