Search results

* agenda seems to be broken down into two types of audiences: 1) what is it, how do I get started; 2) what is it, not interested in it now,

** End User Panel: How SPDX fits into a Corporate Compliance Program -- 1 hrs

===Example 1=== ...<filename>.spdx.zip files will not be backward compatible with SPDX 1.0 tooling. However, the SPDX Data Files they contain can be, and can be eas

* 12:15-1:45 Discussion: Challenges and Approaches to Implementing SPDX led by SPDX E * 1:45-2:00 Break

** not going to worry about 1 and 2 for now, but 3 could be used for listing items to be discussed on thu

== Steps needed to close on v 1.1 of the spec == ** Appendix 1 will be updated to reflect what’s on the website as of date -- Kate

* A)PROPOSAL 1: leave 'as is' on license list now which is that these scenarios are captur **** (1)But then, what about when you aren't sure - which short identifier do you u

Collecting use cases – concern on the deadline – 1 ½ weeks isn’t enough. Suggest 5 from today deadline. Agreed to 5 weeks.

...ovide link to OSI license, verify that it is the same text as supplied in #1 above.

1) Discuss status of Adding Licenses proces

* Spec 1.1 Charter: * Spec 1.2 Why is a common format for data exchange needed?

== 1.1 Discussion == ** Discussion on tag name. Two proposals for the definition of the term – 1) a reference to the canonical form of the license as the source of the lice

* 1.1 update == 1.1 Discussion ==

* item #1 completed, will be removed ...license list to be uploaded and published by 6/20 for inclusion in Spec 1.1

== Guideline 1. Verbatim Text == ** not going to happen for 1.1, but for 2.0? is this as simple as return status indication or would we nee

<nowiki>1) Matching text – indicating replaceable or omitable text. Last call we de

1) discussed various aspects of recent mailing lists posts in regards to lice

1) New License Request for GNU Affero General Public License v3.0 or later (A

== Linuxcon (Panel, Working group meeting, 1.1 PR?) == Working group meeting on Tuesday from 1-6pm will focus on 2.0. The first hour will be reserved to provide an SPDX i

...faster path of success and it is critical to get to that point. Otherwise, 1) recruiting other companies into this WG will be a mission impossible chall ...nce a lot of folks are expected to attend, then it would make sense to add 1 more day to the meeting to cover these items.

{| style="width: 637px" border="1" 1

* The volunteer based model worked well to get SPDX to 1.x. Going forward there is a need to have a different model. This will be co ...content in the form of practical papers - tutorial style, doing more than 1 F2F (for all of SPDX WG) and inviting target companies to attend a 0.5 day

* comment (by creator) 0:1 '''WORKFLOW''' is a 3.1 issue.

...name in third clause of BSD; third, fourth, and fifth clauses of Apache 1.1; or in disclaimer clauses). And, if the latter, how to provide such markup The group supported option #1 above, and suggested using markups such as the following:

* 1.2 release ** Could be handled by regex (e.g. 0:1)

...dular and can be assembled into configurations from a 1 slide version to a 1 hour presentations

...b.com/spreadsheets/d/11AKxLBoN_VXM32OmDTk2hKeYExKzsnPjAVM7rLstQ8s/edit?pli=1#gid=695212681 <br /> ...b.com/spreadsheets/d/11AKxLBoN_VXM32OmDTk2hKeYExKzsnPjAVM7rLstQ8s/edit?pli=1#gid=0 <br />

1) new page for tracking licenses – Jack added a table format for ease of u

...age for the license - thus allowing the license list to be maintained with 1 file per license (instead of two)

1) review changes to License Request page here: http://spdx.org/spdx-license-

== Version 1.17 of the SPDX License List == Version 1.17 of the SPDX License List has been released (finally)!! .zip file is post

1 License Template 1.1 Standard License List Template Download

'''1) License tracking table''' – need an owner (Dennis was volunteered by Mic * BSD, Apache, GPL, LGPL, Eclipse, MIT, MPL v1.1, CDDL, CPL,

'''1) Standard Headers issues''' * Mark will do this work: 1) general review of Standard Headers for correctness; 2) add markup (variabl

'''1) LinuxCon is coming up! September 16-18 in New Orleans''' ...) SISSL license issue brought on list by Camille: we have SISSL (version 1.1), but there is also a v1.2'''

'''1) LinuxCon, various other updates, administrative stuff'''

'''1) License Matching Guidelines: status update, go over any questions for new

{| class="wikitable sortable" border="1" {| class="wikitable sortable" border="1"

1) Ruby License: Ruby has a notice at the top of the license stating the dis ...rs that other text changed incrementally, much earlier (in between 1.4 and 1.6 of Ruby) making it hard to determine where to call it different versions.

as defined by the Linux Foundation's SPDX project [1]. For example, :* SPDX-License-Identifier: (LGPL-2.1 AND BSD-2-CLAUSE)

'''1) Summary of LinuxCon happenings'''

Oct. 1, 2013 * SPDX 1.2

{| class="wikitable sortable" border="1" | SPDX 2.0 RC 1

'''1) License Matching Guidelines'''

{| class="wikitable sortable" border="1" | SPDX-TR-2014-1

1) License Matching Guidelines

'''1) License Matching Guidelines (Jilayne)''' - The SPDX License List Matching ...sion numbering for license list - does it need to follow spec (in terms of 1.x and 2.x)? or can it follow it's own numbering? does it matter?

1) Fedora list (Zac) - went through next set of licenses to view and made not ...ribution - it is verbatim 3-clause, plus another clause; sort of Apache 1.1-ish; ADD, but will use different short identifier than Fedora to better lin

...Ref-1 , :LicenseRef-4 , :LicenseRef-2 , Apache-1.0 , :LicenseRef-3 , MPL-1.1 , Apache-2.0 ...mber :LicenseRef-1 , :LicenseRef-4 , :LicenseRef-2 , :LicenseRef-3 , MPL-1.1 , Apache-2.0

1) what on the plate?