<?xml version="1.0"?>
<?xml-stylesheet type="text/css" href="https://wiki.spdx.org/skins/common/feed.css?303"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
		<id>https://wiki.spdx.org/index.php?action=history&amp;feed=atom&amp;title=Technical_Team%2FMinutes%2F2019-07-16</id>
		<title>Technical Team/Minutes/2019-07-16 - Revision history</title>
		<link rel="self" type="application/atom+xml" href="https://wiki.spdx.org/index.php?action=history&amp;feed=atom&amp;title=Technical_Team%2FMinutes%2F2019-07-16"/>
		<link rel="alternate" type="text/html" href="https://wiki.spdx.org/index.php?title=Technical_Team/Minutes/2019-07-16&amp;action=history"/>
		<updated>2026-05-07T12:25:58Z</updated>
		<subtitle>Revision history for this page on the wiki</subtitle>
		<generator>MediaWiki 1.23.13</generator>

	<entry>
		<id>https://wiki.spdx.org/index.php?title=Technical_Team/Minutes/2019-07-16&amp;diff=4741&amp;oldid=prev</id>
		<title>Goneall: Created page with &quot;July 16, 2019 == Attendees == * Steve Winslow * Gary O’Neall * Alexios Zavras * Krys Nuvadga * Paul Madick * Philippe Ombredanne,  * Rohit Lodha * Tanjong Smith * Vladimir S...&quot;</title>
		<link rel="alternate" type="text/html" href="https://wiki.spdx.org/index.php?title=Technical_Team/Minutes/2019-07-16&amp;diff=4741&amp;oldid=prev"/>
				<updated>2019-08-07T16:49:47Z</updated>
		
		<summary type="html">&lt;p&gt;Created page with &amp;quot;July 16, 2019 == Attendees == * Steve Winslow * Gary O’Neall * Alexios Zavras * Krys Nuvadga * Paul Madick * Philippe Ombredanne,  * Rohit Lodha * Tanjong Smith * Vladimir S...&amp;quot;&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;July 16, 2019&lt;br /&gt;
== Attendees ==&lt;br /&gt;
* Steve Winslow&lt;br /&gt;
* Gary O’Neall&lt;br /&gt;
* Alexios Zavras&lt;br /&gt;
* Krys Nuvadga&lt;br /&gt;
* Paul Madick&lt;br /&gt;
* Philippe Ombredanne, &lt;br /&gt;
* Rohit Lodha&lt;br /&gt;
* Tanjong Smith&lt;br /&gt;
* Vladimir Sitnikov&lt;br /&gt;
* Uday Korlimarla&lt;br /&gt;
* Kate Stewart&lt;br /&gt;
&lt;br /&gt;
==Recording==&lt;br /&gt;
Recording available at https://zoom.us/recording/share/i586KdwLMoj7_2RfgvIC3iTRls81Y0rQl3ohnp9kGoqwIumekTziMw &lt;br /&gt;
&lt;br /&gt;
==GSoC==&lt;br /&gt;
* Tanjong - promotion to license repository method, questions and suggestions welcomed for the namespace repository. &lt;br /&gt;
* Tushar - some suggestions about code give &lt;br /&gt;
* Uday and Philippe – Ndip has made good progress so far,  shared info about data stats.   Working prototype is there.   Ndip - dealing with flooding. &lt;br /&gt;
* Rohit - student is a bit behind,  but seems to be catching up.&lt;br /&gt;
* Philippe - ahead of schedule for original plan.   Working on enhancements to python library. &lt;br /&gt;
* Krys - .pdf/html documentation - students making good progress.   Internal links in .pdf now work.   Natish working on language conversion,  but some snags.   Wordpress library plugin template going well. &lt;br /&gt;
&lt;br /&gt;
==Tech and Legal SPDX call==&lt;br /&gt;
* Workflow: Monitoring issues – bot teams monitor both sets of issue?&lt;br /&gt;
** Recommend subscribing both,   tagging technical issues in legal, and visa version. &lt;br /&gt;
* Use filter listed of topics from tags. &lt;br /&gt;
* This call will be used for figuring out from the filtered list. &lt;br /&gt;
&lt;br /&gt;
==Legal team issue to discuss with tech team==&lt;br /&gt;
* We have short form identifier format for licenses in source code.&lt;br /&gt;
* Should there be something similar for copyright notices.   No prescribed format, but here is a prefix that can be used to find them.    FSFE reuse version has proposed “SPDX-Copyright:”,   lengthy discussion in github  https://github.com/spdx/spdx-spec/issues/122.   Concerns from legal side, implying that SPDX has a copyright in it, or the format is recommended by SPDX, and other things that the legal team was ok with.    More comfort to the exact tag used in SPDX specification -  SPDX-FileCopyrightText: &amp;lt;copyright notice&amp;gt;&lt;br /&gt;
* Instructs someone reading the code that plops into the specific name.&lt;br /&gt;
* Call - one way to add SPDX information inside files - then use exact tag name as defined in the spec.    &lt;br /&gt;
* Philippe: concerns about asking for structured copyright information is only value of adding SPDX-Copyright. &lt;br /&gt;
* Steve:  Legal concern does not want to prescribe one format over another,  so not sure that SPDX project should be doing this.    &lt;br /&gt;
* Philippe:  Don’t see why we shouldn’t follow https://dep-team.pages.debian.net/deps/dep5/#copyright-field&lt;br /&gt;
Since change is lets do it right, regex,   any generic is fine.   Broader discussion.   &lt;br /&gt;
* Vladimir: could SPDX-Copyright:… reference a file?&lt;br /&gt;
* Gary: If the FileCopyrightText is in an SPDX document, it could reference a file.  For this proposal, the tag would be in the file itself.  Tools could then generate a valid SPDX document from the source file parseable information.&lt;br /&gt;
* SPDX-Fieldname:value - will have some places where it won’t make sense.&lt;br /&gt;
* Does it make sense to indicate which ones actually make sense?&lt;br /&gt;
** Alexios - just an indication want to share information, rather than authorative.&lt;br /&gt;
** Gary - makes sense to go through the specific level fields,  does this field make sense.     The follow are ones that have been discussed and may be in use. &lt;br /&gt;
** Probably a good idea to make up a table.      Explain why not identifer, checksum, etc. &lt;br /&gt;
* Agree to put Files &amp;amp; Packages fields, and put information in table on the ones that make sense, and an explanation of for the ones that don’t.&lt;br /&gt;
&lt;br /&gt;
==Namespace topic==&lt;br /&gt;
* reviewed GSoC project https://summerofcode.withgoogle.com/projects/#5604490302980096&lt;br /&gt;
* need to be registered vs -. do not need.&lt;br /&gt;
* possibly make a fully currated for the registered list.  &lt;br /&gt;
* Do we have fully uncurrated - first come, first serve,  be their name on official list of spdx list promoted registry.&lt;br /&gt;
* Philippe - understand legal concern, but intent is just to have known strings being used as prefix.  With ok with no registry.&lt;br /&gt;
* Gary - project proposal was already agreed by technical and legal.   Change nature of considerations to what can we do to make this sucessful, and implementable processes. &lt;br /&gt;
* Alexios - separate registry of namespaces from registry licenses.    Don’t see this easy to be automated - we need namespace registry.&lt;br /&gt;
* Gary follow up call?   Yes,   proposing when Legal team spot would be this thursday.  &lt;br /&gt;
* Philippe willing to pilot namespaces about Namepace for ClearlyDefined &amp;amp; ScanCode.  &lt;br /&gt;
[[Category:Technical|Minutes]]&lt;br /&gt;
[[Category:Minutes]]&lt;/div&gt;</summary>
		<author><name>Goneall</name></author>	</entry>

	</feed>