https://wiki.spdx.org/index.php?action=history&feed=atom&title=Technical_Team%2FMinutes%2F2020-05-19 2026-05-07T12:20:36Z Revision history for this page on the wiki MediaWiki 1.23.13 https://wiki.spdx.org/index.php?title=Technical_Team/Minutes/2020-05-19&diff=4833&oldid=prev 2020-05-19T19:38:15Z

<p>Created page with &quot;May 19, 2020 == Attendees == * Jim Hutchison * Rex Jaeschke * GogginsS * John Mudge * Nisha Kumar * Steve Winslow * Kate Stewart * William Bartholomew * Gary O’Neall * Rose...&quot;</p> <p><b>New page</b></p><div>May 19, 2020<br /> == Attendees ==<br /> * Jim Hutchison<br /> * Rex Jaeschke<br /> * GogginsS<br /> * John Mudge<br /> * Nisha Kumar<br /> * Steve Winslow<br /> * Kate Stewart<br /> * William Bartholomew<br /> * Gary O’Neall<br /> * Rose Judge<br /> * Takashi Ninjouji<br /> * Santiago Torres<br /> * Peter Shin<br /> * Vicky Brasseur<br /> * Thomas Steenbergen<br /> * Rishabh Bhatnagar<br /> <br /> ==SPDX 2.2==<br /> * Question on how to submit new features beyond 2.2<br /> ** Consensus to add issues in Github<br /> * SPDX 2.2 wrap up - status of .pdf generation, next steps <br /> ** Kate &amp; Gary - follow up, still some issues outstanding.<br /> ==SPDX 2.2.1==<br /> * update from Rex<br /> ** A new numbering scheme<br /> ** An appendix will be added to translate from the old to new numbering<br /> ** John gave an update on new format<br /> * Line breaks discussion<br /> ** Thomas recommended line breaks be made post production rather than explicitly<br /> ** Agreed to not add explicit line breaks<br /> * Discussion on changing Intent to Description<br /> ** Agreed to change to Description<br /> * Possible issue with the word Example<br /> ** May have to change to a different word such as sample<br /> ** Thomas raised an issue with changing to sample<br /> * Embedded HTML in the examples may cause issues<br /> ** Suggest removing the HTML except for anchors<br /> ** May also be an issue with 3.0<br /> * Major issues have been resolved<br /> * Expect to have a list of remaining issues by the end of the week<br /> <br /> ==GSoC==<br /> * Anisha, Rohit &amp; Gary - had call, researching alternatives<br /> * Rishab, Steve &amp; Gary - golang, discussion <br /> * Philip - Kate, Santiago &amp; Philippe - pending<br /> * Tenjong - license cross ref, already engaging. <br /> * reasonable activitity on gitter. <br /> * Bringing back one of student proposals through community bridge, update June 1.<br /> <br /> ==Automation for the Spec==<br /> * Level of Automation for 3.0<br /> ** OWL document —&gt; Schema’s work —&gt; Sample code, etc. <br /> ** Two sources of errors: tools doing translations, copy paste error<br /> ** Can we look at automating the creation from everything from one source of record.<br /> ** Having mark down be the source of record.<br /> * Automation Proposals:<br /> * Pick a source of record, everything else is automated from there.<br /> ** Diagram - how can this work with markdown.<br /> ** Possibly not include generated artifacts in repo.<br /> ** Could be added into a github action to generate diagram. Not store in repo itself, since its generated.<br /> ** Everytime PR, get new OWL document <br /> ** William’s diagrams are already generated by plugin<br /> ** Software generate example files, and then they are included in markdown.<br /> * Concern: How fragile are the tools? <br /> ** Gary - will handcode in Java, specific to SPDX. Subsection &amp; schemas. Tool dependency.<br /> ** Thomas - Companies do this, but we need to make sure. <br /> * Sections will have to be very much tied to the formatting. <br /> * Breaking formatting may break build. PR requested via breaking build. More of burden for submitters.<br /> * Nisha, Kate, William, are a favor in trying this.<br /> * Gary looking for collaboration on the tools. Nisha &amp; Rose willing to work with Python. <br /> ** Gary ok to do it in Python, if Rose able to help out here. Separate Sync up in 2 or 3 weeks. <br /> ** William ok mentor. Thomas ok to review.<br /> * Revisit in 3 weeks - status of tooling <br /> <br /> ==SPDX 3.0==<br /> * How do we submit proposals for 3.0?<br /> ** Use Github Issues<br /> ** Proposal to add Github labels for the profiles<br /> ** Add Tech Team review as a label to schedule a call<br /> * Annotations and/or Relationships have YAML samples for review<br /> ** Kate will help with the examples<br /> * Suggest we start a mapping spreadsheet<br /> ** Kate will start the sheet<br /> * Wait for 2.2.1 template completion from John<br /> ** After template, William will create 3.0<br /> * Need a way to specify which profiles are in effect<br /> ** Suggest adding a field to the base<br /> ** Base is always listed, additional profiles are also listed<br /> ** Defer versioning<br /> * Discussed if you can use fields from other profiles<br /> ** OK to re-use fields from other profiles<br /> ** Profiles define which fields are mandatory<br /> ** To be further discussed<br /> <br /> ==Next Week’s Agenda==<br /> * Thomas to lead discussion on Security profile<br /> <br /> [[Category:Technical|Minutes]]</div>

Goneall