Proposal to use SPDX for SRFI license/copyright declarations Maxim Cournoyer (06 Dec 2023 22:46 UTC)
Re: Proposal to use SPDX for SRFI license/copyright declarations Arthur A. Gleckler (06 Dec 2023 23:06 UTC)
Re: Proposal to use SPDX for SRFI license/copyright declarations Philip McGrath (07 Dec 2023 08:43 UTC)
Re: Proposal to use SPDX for SRFI license/copyright declarations Wolfgang Corcoran-Mathe (07 Dec 2023 18:31 UTC)
Re: Proposal to use SPDX for SRFI license/copyright declarations Arthur A. Gleckler (07 Dec 2023 19:00 UTC)
Re: Proposal to use SPDX for SRFI license/copyright declarations Arthur A. Gleckler (07 Dec 2023 20:12 UTC)
Re: First batch of SPDX annotated SRFIs examples Maxim Cournoyer (09 Dec 2023 03:28 UTC)
Re: First batch of SPDX annotated SRFIs examples Lassi Kortela (09 Dec 2023 16:18 UTC)
Re: First batch of SPDX annotated SRFIs examples Maxim Cournoyer (09 Dec 2023 23:06 UTC)
Re: First batch of SPDX annotated SRFIs examples Lassi Kortela (10 Dec 2023 12:45 UTC)
Re: First batch of SPDX annotated SRFIs examples John Cowan (10 Dec 2023 13:15 UTC)
Re: First batch of SPDX annotated SRFIs examples Maxim Cournoyer (10 Dec 2023 16:03 UTC)
Re: First batch of SPDX annotated SRFIs examples Maxim Cournoyer (10 Dec 2023 15:59 UTC)
Re: First batch of SPDX annotated SRFIs examples Lassi Kortela (10 Dec 2023 16:32 UTC)
Re: First batch of SPDX annotated SRFIs examples Maxim Cournoyer (12 Feb 2024 19:48 UTC)
Re: Proposal to use SPDX for SRFI license/copyright declarations Marc Nieper-Wißkirchen (08 Dec 2023 16:21 UTC)
Re: Proposal to use SPDX for SRFI license/copyright declarations Arthur A. Gleckler (08 Dec 2023 23:37 UTC)
Re: Proposal to use SPDX for SRFI license/copyright declarations Arthur A. Gleckler (09 Dec 2023 00:01 UTC)
Re: Proposal to use SPDX for SRFI license/copyright declarations Arthur A. Gleckler (09 Dec 2023 00:11 UTC)
Re: Proposal to use SPDX for SRFI license/copyright declarations Arthur A. Gleckler (08 Dec 2023 23:31 UTC)
Re: Proposal to use SPDX for SRFI license/copyright declarations Arthur A. Gleckler (08 Dec 2023 23:35 UTC)
Re: Proposal to use SPDX for SRFI license/copyright declarations Marc Nieper-Wißkirchen (09 Dec 2023 08:06 UTC)
Re: Proposal to use SPDX for SRFI license/copyright declarations Marc Nieper-Wißkirchen (09 Dec 2023 14:19 UTC)
Re: Proposal to use SPDX for SRFI license/copyright declarations Marc Nieper-Wißkirchen (09 Dec 2023 16:08 UTC)
Re: Proposal to use SPDX for SRFI license/copyright declarations Marc Nieper-Wißkirchen (09 Dec 2023 16:02 UTC)
Re: Proposal to use SPDX for SRFI license/copyright declarations Arthur A. Gleckler (10 Dec 2023 02:21 UTC)
Re: Proposal to use SPDX for SRFI license/copyright declarations Marc Nieper-Wißkirchen (09 Dec 2023 17:28 UTC)
Re: Proposal to use SPDX for SRFI license/copyright declarations Arthur A. Gleckler (10 Dec 2023 02:30 UTC)
Re: Proposal to use SPDX for SRFI license/copyright declarations Arthur A. Gleckler (12 Dec 2023 00:15 UTC)
Re: Proposal to use SPDX for SRFI license/copyright declarations Arthur A. Gleckler (12 Dec 2023 18:44 UTC)
Re: Proposal to use SPDX for SRFI license/copyright declarations Arthur A. Gleckler (13 Dec 2023 00:26 UTC)
Re: Proposal to use SPDX for SRFI license/copyright declarations Arthur A. Gleckler (18 Dec 2023 19:41 UTC)
Re: Proposal to use SPDX for SRFI license/copyright declarations Arthur A. Gleckler (18 Dec 2023 23:03 UTC)
Re: Proposal to use SPDX for SRFI license/copyright declarations Arthur A. Gleckler (13 Dec 2023 00:41 UTC)
Re: Proposal to use SPDX for SRFI license/copyright declarations Marc Nieper-Wißkirchen (12 Dec 2023 07:01 UTC)
Re: Proposal to use SPDX for SRFI license/copyright declarations Arthur A. Gleckler (13 Dec 2023 00:24 UTC)
Re: Proposal to use SPDX for SRFI license/copyright declarations Daphne Preston-Kendal (09 Dec 2023 10:26 UTC)
Re: Proposal to use SPDX for SRFI license/copyright declarations Marc Nieper-Wißkirchen (09 Dec 2023 17:35 UTC)
Re: Proposal to use SPDX for SRFI license/copyright declarations Daphne Preston-Kendal (09 Dec 2023 21:09 UTC)
Re: Proposal to use SPDX for SRFI license/copyright declarations Arthur A. Gleckler (10 Dec 2023 02:18 UTC)

Re: Proposal to use SPDX for SRFI license/copyright declarations Philip McGrath 07 Dec 2023 08:43 UTC

On 12/7/23 02:55, John Cowan wrote:
>
> The MIT license text plainly says (emphasis added) "The above copyright
> notice and this permission notice (including the next paragraph) *shall*
> be included in all copies or substantial portions of the Software."  It
> does not say that a link to an outboard copy of the license is an
> adequate substitute for this requirement: the word "shall" implies that
> the requirement must be followed as written.
>

I think an expressed preference of actual SRFI authors to keep the full
license comments as they are is a more than sufficient reason to do so.

Just in an attempt at clarity, I'd distinguish three courses of action
one might consider:

1. Add SPDX metadata, but do not remove anything. I'm not aware of any
objections to this course of action.

2. Add SPDX metadata and remove existing comments, leaving the full text
of the MIT license nowhere. For the reasons John explains, this course
of action would seem to violate the requirements of the MIT license. (It
would be different if the original author included only SPDX comments,
as some people now do.)

3. Add SPDX metadata and move the full text of the MIT license to a
separate file distributed alongside the original file. This at least
arguably could satisfy the requirements of the license: for example,
copies of MIT-licensed software in compiled form often move the required
text to a separate file. However, some people do have concerns about
this approach. In my last email I wrote that it has the advantage that
readers don't have to determine if the text is exactly the standard
text, but it also has the disadvantage that copiers must be sure to also
copy the separate file for the license.

So, "add SPDX metadata, but do not remove anything" seems like the
safest course of action.

>
> The proposed patch to SRFI 119, which is the only one I've seen so far,
> also changes certain existing ";;" comments into ";;;;" comments.  That
> violates a strong convention of the Scheme (and indeed the wider Lisp)
> community that comments with four semicolons represent outline
> headings.  See <https://mumble.net/~campbell/scheme/style.txt
> <https://mumble.net/~campbell/scheme/style.txt>> s.v. "Outline
> Headings".  Therefore, this change should be undone.

I also noticed the changed number of semicolons and agree that it should
not be changed, my last email was just getting a bit long already.

Philip