https://wiki.spdx.org/index.php?action=history&feed=atom&title=General_Meeting%2FMinutes%2F2017-10-05 2026-05-07T12:33:18Z Revision history for this page on the wiki MediaWiki 1.23.13 https://wiki.spdx.org/index.php?title=General_Meeting/Minutes/2017-10-05&diff=4473&oldid=prev 2017-10-05T15:40:14Z

<p>Created page with &quot;* Attendance: 11 * Lead by Phil Odence * Minutes of Sept meeting approved == Guest Presentation - Alexander Lisianoi == * Background ** Working on masters in Technical Uni...&quot;</p> <p><b>New page</b></p><div>* Attendance: 11<br /> * Lead by Phil Odence<br /> * Minutes of Sept meeting approved <br /> <br /> <br /> == Guest Presentation - Alexander Lisianoi ==<br /> <br /> * Background<br /> ** Working on masters in Technical University of Vienna<br /> * Project<br /> ** Turning Python Code into Javascript<br /> *** Pooling PY and License expression<br /> *** Libraries that are self contained<br /> *** Initially looked easy<br /> ** Results<br /> *** It works!<br /> ** How it went<br /> *** Long list of tools available, so choosing a tool is the first step<br /> **** Brython, Batavia, Transcript<br /> **** Brython can read in pure Python<br /> **** Bytavia uses Python byte code<br /> **** Transcript actually translates to javacode, so he picked that one<br /> ***** Downside is that it doesn’t handle every Python capability<br /> *** Encountered a lot of bizarre results<br /> **** And complained a fair amount<br /> **** Tricky to know what goes wrong; have to debug both in parallel<br /> **** Errors can be subtle<br /> **** How things are compared differs between languages<br /> ** The resulting tool<br /> *** You can parse, but it can be broken<br /> ** Value of the work<br /> *** Javascript is very commonly used for front ends these days<br /> *** You don’t want to have to support two technologies for front and back end<br /> *** This allows leveraging the backend scripts for building front end<br /> *** Valuable to tool developers using JS and to development communities<br /> *** As a side-effect of the work, we Alexander helped <br /> <br /> == Tech Team Report - Kate/Gary ==<br /> <br /> * Spec<br /> ** All on GItHub now<br /> * Last few meetings have been focused on<br /> ** FSF proposal<br /> *** Supporting legal team on expanding license expression language<br /> ** Testing work from Jack<br /> *** Tool testing cases<br /> **** Scanners for locating license language<br /> **** License language matchers (using matching guidelines)<br /> *** Also testing license list generator<br /> **** Which requires test cases as well<br /> *** Looking at creating a repo for all test cases<br /> **** Two tool types <br /> **** License list gen<br /> *** Will be community based so folks can contribute cases<br /> * Preview<br /> ** Looks like there will be a new tool contribution from an LF member<br /> ** A tool to create a summary <br /> *** Input SPDX tag value; output easy to read/intrerpret format<br /> <br /> * LinuxCon Europe<br /> ** There will be a meeting for those creating tools<br /> ** New testing work with be on the agenda<br /> <br /> <br /> == Legal Team Report - Jilayne/Paul ==<br /> <br /> * FSF Proposal <br /> ** For how the GPL version is represented<br /> ** Questions about new operators, default<br /> ** Generated a large meeting with tech folks<br /> *** Lively discussion<br /> *** Did not reach resolution<br /> ** FSF has come back with another proposal<br /> *** Technical challenges<br /> *** Difference of opinion, particularly for case where<br /> *** Part of the issue is that FSF is focused on just the identifiers vs. how we use with SPDX<br /> **** License does not specify “or later” or “only”<br /> **** How do we represent without representing legal judgment<br /> **** Fundamentally there are different opinions on what it means when there is no specification<br /> **** Very important to FSF (including Richard Stallman)<br /> <br /> == Outreach Team Report - Jack ==<br /> <br /> * Mostly license test file work as described above<br /> <br /> <br /> <br /> == Attendees ==<br /> <br /> * Phil Odence, Black Duck<br /> * Kate Stewart, Linux Foundation<br /> * Alexander Lisianoi, Technical University of Vienna<br /> * Matthew Crawford, ARM<br /> * Matija Suklje, FSFE<br /> * Steve Winslow, Linux Foundation<br /> * Mike Dolan, Linux Foundation<br /> * Jack Manbeck, TI<br /> * Michael Herzog- nexB<br /> * Gary O’Neall, SourceAuditor<br /> * Paul Madick, Dimension Data<br /> <br /> <br /> <br /> <br /> [[Category:General|Minutes]]<br /> [[Category:Minutes]]</div>

Podence