exceptions for v2.1

J Lovejoy

Hi All,

I’ve begun to add the exceptions to the SPDX License List in preparation for the v2.1 release at the end of the month.  A few things to ponder here or discuss on the next call:

Should exceptions have markup for omitable or replaceable text, as per the Matching Guidelines? If so, we’d need to update the Matching Guidelines, 2.3 and 2.4 to reference the exceptions, instead of just the license text.  Thoughts?

Please have a look at the exception tab marked for release for 2.1  https://docs.google.com/spreadsheets/d/11AKxLBoN_VXM32OmDTk2hKeYExKzsnPjAVM7rLstQ8s/edit?pli=1#gid=0
and review for the following items:

1) names and short identifiers - this could use another look, before putting these on the list. 

2)  I’ve noted some exceptions specifically because they have text that could possibly use markup:
  • CLISP-exception-2.0 - should the summary at the top be included as part of the exception text?  Should this have markup as omitable? 
  • i2p-gpl-java-exception-2.0 - see text, looks like the XXXX is supposed to allow for a variable name value?  Should this have markup as replaceable?
  • MySQL-Connector-ODBC-exception-2.0 - need an external link to this (preferably), does anyone have one?
  • Qwt-exception-1.0 - has some text that should be replaceable in suggestion for notice at end of exception text

SPDX Legal Team co-lead

Join Spdx-legal@lists.spdx.org to automatically receive all group messages.