Search results

1) Contributing updates and license submission tool:

** Proposed: In new XML format, any new property where cardinality is >1, will have two properties: singular to represent the individual element, an

1) Open Source Leadership Summit coming up, March 12-14. SPDX face2face on th

1) Open Source Leadership Summit agenda * SPDX f2f time is Monday afternoon 1-5pm

1) go through outstanding issues for 3.5 release and update: ...to have all tied up by next Friday, Mar 29 then do actual release on April 1

** Merged some of the external repository features as a library into 4.1 * 1 draft – not sure which one this is

** Porting license expression library: 1

1) Steve and Gary gave a great presentation on the general call prior to this

1) meetings posted for April 4th; most of work from April 18th are mostly in

1) Update on GSoC - maybe next call have Gary update us on which projects are ...iew, see: https://github.com/spdx/license-list-XML/blob/jlovejoy-inclusion-1/DOCS/what-why-how.md

1) GSoC update from Umang who is working on a project to enhance the workflow * 1 week prior: all PRs have been merged that are going to be part of release a

...ibe “ALL” the license that apply to a distinct package. If more than 1 separate work, it becomes confusing.

1) Joint tech/legal team calls:

1) Follow-up conversation re: “SPDX-Copyright:” or related tags – sugge ...ion on whether or not to add a license to the list. If >= 3 people give a +1 and no objections, then fine, easy to add. If complicated issues, then labe

*** 1 Unskilled suppliers

* 1 repository still needs to be moved – JavaScript project

* NTIA phase 1 documents are published at https://www.ntia.gov/sbom (SPDX is a recognized * Pushing Jan meeting to 1/9.

** Many to many? 1:1? 1:*, *:1?

==SPDX 2.2.1== * 1 to 2 weeks we should be “throwing the switch”

==SPDX 2.2.1== ...nging back one of student proposals through community bridge, update June 1.

* The project is scheduled to start July 1 and run through end of September

** 2.1 is in good shape *** We are through phase 1 (funding for this year)

* Will be turn on Sept. 1

*** pushed first draft of fields for (1) vulnerabilities, and (2) defects => impact on packages, false positives, e *** 1 for transitioning / updating online SPDX tools

* [https://github.com/spdx/spdx-spec/blob/development/v2.2.1/ontology/spdx-ontology.owl.xml Current RDF/OWL document for SPDX spec] 1. Enable developers with a "code view" of tool-generated SPDX document close