Search results

...majority vote for people that attended the meeting (at least 5 people and 1 legal)

** 1/2 day track on legal related issues Thursday morning

*** 1/2 day track on legal related issues Thursday morning

...majority vote for people that attended the meeting (at least 5 people and 1 legal)

* Ready for presentation to other teams in the next 1-2 months ** 1/2 day track on legal related issues Thursday morning

* Discussion on if we should prepend property names with cardinality of 1 to N with “has” – we will decide after completing the rest of the spr

** sub-section 2.1 SPDX Specification Version Number ...e future reference to format and define it to be just a string for version 1

* LicenseInfo fields – add the new syntax for license sets and mandatory 1 * Section 5.2 is currently 4.1 – renumber/format issue

* 1) analyzed and data is insufficient to draw a conclusion * Cardinality of licenseInfoFromFile is 1 .. n

...pddl/1.0/|Open Data Commons PDDL 1.0] as a potential candidate to resolve #1 above.

* A third delivery model – 1) SPDX is a sidecar to the package archive, 2) SPDX is embedded in the packa

...review (and clean up) bugs. Decide which ones need to be fixed for release 1.

Version 1 shows the SPDX Home Page with 9 proposed child pages that would be availabl

* Proposal – cardinality 1, String format

** Phil has speaking slot, JimZ should mention in Keynote, 1 pg handout, table

...' - probably more for informing new people than real working session, only 1 hour. Very few people from technical team attending event, so not enough ti

** SPDX booth staffing in progress; John Ellis working schedule; 1 pg handout will be available ...statement will be included in SPDX file at this time; we will revisit post 1.0 GA

*** Use Case 1: In comparing an SPDX document to the files, the algorithm would need to be *** Use Case 2 would likely be done in a scenario where Use Case 1 would also be done (or in a scenario where the SPDX is used in a “side-ca

[[Image:spdxdoodle2-1.jpg]] * '''Creator (Annotation): '''Equivalent to SPDX 1.0 Creation Information Creator

*** Goal: At least 1 major community announcing support

* Goal: Get cheat sheet out by General Team 1/12

== Version 1.1 == Tools need to be updated to the latest spec, Gary will review 1.1 draft once completed and update the Java tools to the latest spec

...majority vote for people that attended the meeting (at least 5 people and 1 legal)

....gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/profiles/license_groups?revision=1.102&view=markup (the above only covers 252 out of the 614 licenses presentl ** This would be a 1 day meeting in person with people involved in the software supply chain to

* Work of tech team is focused on the 1.1 spec. * They did a review of the draft 1.1 spec and there were a few follow up items.

...tely a work in progress. Most of the class definitions can be found in the 1.0 spec in the RDF appendix (model) or in [[Technical_Team/Proposals/Rough_p See the attached document for the mapping between the SPDX 1.0 properties and this proposal.

** This would be a 1 day meeting in person with people involved in the software supply chain to

* Date for version 1.1 == Date for 1.1 ==

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

* Minutes for 2011/1/26 approved * 1.1 is very close. Gate is validating the verification algorithm.

* 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.