https://wiki.spdx.org/index.php?action=history&feed=atom&title=General_Meeting%2FMinutes%2F2019-09-05 2026-05-07T12:20:44Z Revision history for this page on the wiki MediaWiki 1.23.13 https://wiki.spdx.org/index.php?title=General_Meeting/Minutes/2019-09-05&diff=4745&oldid=prev 2019-09-05T18:52:24Z

<p>Created page with &quot;* Attendance: 17 * Lead by Phil Odence * Minutes of Aug meeting approved == Special Presentations - Hiro Fukuchi, Sony == * SPDX- Lite ** Open Chain Japan Work Group *** M...&quot;</p> <p><b>New page</b></p><div>* Attendance: 17<br /> * Lead by Phil Odence<br /> * Minutes of Aug meeting approved <br /> <br /> <br /> == Special Presentations - Hiro Fukuchi, Sony ==<br /> <br /> * SPDX- Lite<br /> ** Open Chain Japan Work Group<br /> *** Member companies- Toyota, Denso, Panasonic, Pioneer, Sony, Fujitsu, Olympus, Renesas<br /> ** Common Problem- Can’t get OSS information from suppliers (HW vendors, ODMs, SOC, partners…in Asia (China/Taiwan) and Japan<br /> *** They don’t have complete information<br /> *** Don’t have the tools to generate and evaluate<br /> ** SPDX Lite is part of guidelines<br /> *** Fits in at a fairly high level of maturity<br /> **** OpenChain - “Making Process”<br /> **** SPDX (and OSS tooling) - “Improving Process”<br /> **** Most suppliers are at low levels of maturity<br /> *** Looking not to fork, but to expand usage of SPDX Lite<br /> ** Lite Description<br /> *** Subset of SPDX<br /> *** Minimum requirement<br /> *** Can be manually generated<br /> *** Proved in actual business use<br /> ** Scenarios<br /> *** 1 Unskilled suppliers<br /> **** Useful at a lower level of maturity than SPDX requires<br /> *** 2 Non-engineering Staff<br /> **** More understandable by Legal and Procurement staff.<br /> *** Skilled suppliers would still use full SPDX<br /> **** OpenChain compliant suppliers would be sophisticated enough<br /> ** Question: Is SPDX Lite fully SPDX compliant<br /> *** Yes, all mandatory fields are included in SPDX Lite plus some of the optional fields may be included.<br /> <br /> == Tech Team Report - Gary ==<br /> <br /> * Spec<br /> ** Being worked in a GitHub repo<br /> *** Set up for pull requests for 2.2<br /> *** Anyone who has ideas or proposed changes, please submit as a pull request<br /> *** One in place is SPDX Lite<br /> **** Proposal is as an Appendix<br /> **** Thought is a profile for a specific use case<br /> **** Could be first of a number of profiles<br /> * Tools<br /> ** Successful conclusion to GSoC<br /> *** All passed<br /> *** A number of new libraries including Python, Golang<br /> *** Mentors and students were great<br /> *** Record number of projects<br /> ** Challenge now is integrating and putting into production<br /> *** All legal team tools have been submitted as pull requests<br /> **** Should be up and running in a month or so.<br /> <br /> == Legal Team Report - Jilayne/Paul/Steve ==<br /> <br /> * Legal Team License Submittal Demo (GSoC)<br /> ** Video and minutes available<br /> ** Need to update contribution instructions<br /> * Team call today<br /> * License List<br /> ** 3.7 release at end of month<br /> *** Fewer licenses in release that some recents<br /> ** Recent discussions have been more high level on principles than specific licenses<br /> <br /> <br /> == Outreach Team Report - Jack ==<br /> <br /> * Survey<br /> ** Has been out for a few months<br /> ** 37 responses so far<br /> ** Will make one more pass<br /> ** Looking at presenting at Gen Meeting in Nov<br /> * Philipe has been talking to the Python community about using SPDX License IDs and expressions in Python package manifest<br /> ** Could be a model for other communities<br /> *** …some of which have been using formally or informally<br /> *** Potentially high leverage<br /> *** RUST and Go are using sporadically<br /> <br /> == Cross Functional - ==<br /> <br /> * None<br /> <br /> == Attendees ==<br /> <br /> * Phil Odence, Black Duck/Synopsys<br /> * Steve Winslow, LF<br /> * Gary O’Neall, SourceAuditor<br /> * Jack Manbeck, TI<br /> * Nicolas Toussaint, Orange<br /> * Mark Atwood, Amazon<br /> * Jilayne Lovejoy, Canonical<br /> * Hiro Fukuchi, Sony<br /> * Shinsuke Kato, Panasonic<br /> * Philippe Ombrédanne- nexB<br /> * Michael Herzog, NexB<br /> * Patrice-Emmanuel Schmitz, Trasys International, European Commission<br /> * Richard Fontana, Red Hat<br /> * Mark Baushke, Juniper<br /> * Paul Madick, Dimension Data<br /> * Nisha Kumar, VMWare<br /> * David Marr, Qualcomm<br /> <br /> [[Category:General|Minutes]]<br /> [[Category:Minutes]]</div>

Podence