Hello,

John Cowan <xxxxxx@ccil.org> writes:

> On Fri, Dec 8, 2023 at 6:37 PM Arthur A. Gleckler <xxxxxx@speechcode.com>
> wrote:
>
> I'm happy to add things to my checklist as long as they are clearly spelled
>> out , i.e. they're unambiguous.
>>
>
> So I'm suggesting these checklist items for new SRFIs:
>
> 0) Ensure that the SRFI text includes the text of the MIT/Expat license.
> (Presumably this is already required.)

+1.  Should be the case since it's in the HTML template.

> 1) Ensure that all the source and data files to be included in the repo
> include either (a) the text of the MIT/Expat license, or (b) the text of
> the license or a reference to the license, as the case may be, if the file
> was not written for the SRFI and the editor sees fit to allow the use of
> this file.

Isn't "a reference to the license" a bit weak?  Shouldn't the full
license notice text be preserved instead, per previous discussions?

> 2) If any file is a derivative work, it may also include the license of the
> original work or a reference to it, if that is required by the license of
> the original work.  There should be no SPDX metadata for such a license.

As mentioned in my previous email, since one of my goals here is to
achieve REUSE compliance, each file must have copyright and license
information, which implies at least a 'SPDX-License-Identifier:' tag in
every file, even those with non-standard licenses (thankfully, these are
rare).

> 3) Ensure that all files include SPDX metadata specifying the license of
> the file, provided that there exists appropriate metadata for that license.
>
> Is that satisfactory to you?  Does anyone else object to it at this point?

Let me try to rephrase with my added REUSE requirements:

0) Ensure the the SRFI text includes the text of the MIT/Expat license.

1) Ensure that all the source and data files to be included in the repo
   use a permissive (non-copyleft) free software license, ideally the
   same MIT/Expat as the text.  Each file should contain a copyright
   notice, and each legally significant (> 15 lines of code) file should
   contain the license notice text.

2) The "reuse lint" command should pass, i.e. the SRFI is REUSE
   compliant.  This implies that every source at least contains a
   SPDX-License-Identifier tag with the license, and that a LICENSES/
   directory contains the referenced licenses text.

--
Thanks,
Maxim