https://wiki.spdx.org/index.php?action=history&feed=atom&title=Technical_Team%2FMinutes%2F2020-09-22Technical Team/Minutes/2020-09-22 - Revision history2026-05-07T12:33:14ZRevision history for this page on the wikiMediaWiki 1.23.13https://wiki.spdx.org/index.php?title=Technical_Team/Minutes/2020-09-22&diff=4879&oldid=prevGoneall: Created page with "September 22, 2020 == Attendees == * Kate Stewart * Rishabh Bhatnagar * Nisha Kumar * William Bartholomew * Gary O’Neall * Steve Winslow * Thomas Steenbergen * David Kemp..."2020-09-22T17:59:42Z<p>Created page with "September 22, 2020 == Attendees == * Kate Stewart * Rishabh Bhatnagar * Nisha Kumar * William Bartholomew * Gary O’Neall * Steve Winslow * Thomas Steenbergen * David Kemp..."</p>
<p><b>New page</b></p><div>September 22, 2020<br />
== Attendees ==<br />
* Kate Stewart<br />
* Rishabh Bhatnagar<br />
* Nisha Kumar<br />
* William Bartholomew<br />
* Gary O’Neall<br />
* Steve Winslow<br />
* Thomas Steenbergen <br />
<br />
* David Kemp<br />
* Jim Hutchison<br />
* Peter Shin<br />
<br />
Topics:<br />
* Base Profile<br />
<br />
== Base Profile ==<br />
* Other profiles (legal and vulnerabilities/defects) are currently blocked on documentation structure<br />
* Need a basic structure to start from<br />
* Need to core basically be defined<br />
* How aligned is the spec with 3T?<br />
* Don’t want to wait for the entire base to be specified<br />
* We have a diagram for Base that is pretty close<br />
* Should we have a diagram for the other profiles?<br />
* Licensing isn’t currently blocked – using a Google doc with text to make progress<br />
** Format looks similar to the 2.2 spec text<br />
** Would like to move to Github which will require a format to be specified<br />
* Need to follow the ISO profile as far as format<br />
* How do we specify which profiles are in effect<br />
** Clause 6 – Document information<br />
* Should we use the 2.2 format?<br />
* Document structure is in Google Docs at https://docs.google.com/document/d/19pAxCjXER5c_tdAjIIqK2Ipz5AvirH81GQuG5CsP8wk/edit<br />
* Discussion on Artifact superclass<br />
** Package, File and Snippet are concrete classes based on Artifact<br />
** Artifact is abstract<br />
* Should we check into 3.0 branch?<br />
** Current 3.0 branch was done before Rex’s reformatting<br />
** Rename 3.0 branch and create a new branch based on 2.2.1<br />
** DCO BOT is enabled for the spec repo in the branch protection rules<br />
** William will create a new branch<br />
* Steve will start putting the license in the new branch once available<br />
* If anyone has an issue blocking their profile, they will add an issue<br />
* Nisha asked if the base profile fields are locked down or if they are open to changes<br />
** Not locked down – can add<br />
** Base will be rather minimal<br />
** Profiles should work out what they need and raise issues when they need something to base<br />
* Are we adding fields to relationships?<br />
* Are annotations going to be used for defects?<br />
* Need to describe problem statements as well as solutions<br />
* Create a label “Blocked” if a team is blocked in making progress<br />
* Create a label for each profile<br />
* Create a meta-issue for each profile – optional<br />
* Subteams would decide if they need a diagram – if so, extend the base diagram<br />
* When the spec is complete, each profile will have its own diagram based on the base profile<br />
** Uses draw.io (a.k.a. diagrams.net)<br />
** Draw.io file can be saved<br />
<br />
==Next Week==<br />
* Thursday is a joint tech team legal call<br />
* Tuesday may be a continuation of Thursday’s call<br />
* How interoperate between profile teams – if times allow<br />
** Diagrams<br />
*** Python class diagrams<br />
*** diagrams.net format<br />
*** Plant UML <br />
<br />
[[Category:Technical|Minutes]]</div>Goneall