From: Maxime Devos <maximedevos@telenet.be>
To: Vijay Marupudi <vijay@vijaymarupudi.com>, guile-devel@gnu.org
Subject: Re: [PATCH] Added srfi-214: flexvectors
Date: Wed, 19 Jan 2022 15:04:40 +0000 [thread overview]
Message-ID: <cb79b4584d21322b72687c65232f75e8497505db.camel@telenet.be> (raw)
In-Reply-To: <87wnivzvd4.fsf@vijaymarupudi.com>
[-- Attachment #1: Type: text/plain, Size: 2183 bytes --]
Vijay Marupudi schreef op wo 19-01-2022 om 08:51 [-0500]:
> > however, the README says ‘by Adam Nelson’. Did you reach some kind
> > of
> > agreement with Adam Nelson about copyright assignment? And since
> > SRFIs
> > are licensed under Expat (not 100% sure), wouldn't this need to be
> > the
> > Expat license text?
> >
> > Even if the Expat license allows this (I don't know), then I would
> > still recommend to keep the license the same, such that fixes can
> > easily be interchanged between Scheme implementations (e.g. there
> > have
> > been some fixes to SRFI-64 a while ago).
>
> There was no copyright assignment.
If no copyright assignment has happend, then the copyright still
belongs to the author
-- from the Git repository's LICENSE: Copyright © Adam Nelson (2020)).
While possibly you might have made some small changes to flexvectors,
it seems that most code is preserved, so at most a ‘© FSF’ line could
be added (*), however, the copyright line ‘© Adam Nelson’ would need to
remain, otherwise the copyright lines are misleading.
(*) This assumes you did copyright assignment to the FSF, otherwise
‘© Vijay Marupudi’.
Furthermore, the license requires preserving existing copyright
notices:
> The above copyright notice and [...] (including [...]) shall be
> included in all copies or substantial portions of the Software.
> The expat license is GPL compatible,
> so I assumed GPL would be the preferred license for a contribution to
> Guile. [...] I can definitely change the license for my edits to
> whatever is
The expat license is GPL compatible, but the expat license requires
preserving the license text:
> Permission is hereby granted [...]:
>
> The above [...] and this permission notice (including the next
> paragraph) shall be included in all copies or substantial portions of
> the Software.
>
> [warranty disclaimer]
Here, ‘this permission notice’ seems to be the text of the expat
license. But I'm not seeing this text in the srfi-214.scm of your
patch.
> best for Guile.
That would be up to the maintainers I suppose.
Greetings,
Maxime.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next prev parent reply other threads:[~2022-01-19 15:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-19 2:34 [PATCH] Added srfi-214: flexvectors Vijay Marupudi
2022-01-19 9:00 ` Maxime Devos
2022-01-19 13:55 ` Vijay Marupudi
[not found] ` <87wnivzvd4.fsf@vijaymarupudi.com>
2022-01-19 15:04 ` Maxime Devos [this message]
2022-01-19 15:44 ` Vijay Marupudi
2022-01-19 16:04 ` Maxime Devos
2022-01-20 15:34 ` Vijay Marupudi
2022-01-20 16:53 ` Maxime Devos
2022-01-20 17:57 ` Vijay Marupudi
2022-01-20 18:15 ` Maxime Devos
2022-01-20 20:38 ` Vijay Marupudi
2022-10-07 19:58 ` Vijay Marupudi
2022-10-12 12:22 ` Ludovic Courtès
2022-11-13 20:27 ` Vijay Marupudi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cb79b4584d21322b72687c65232f75e8497505db.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=guile-devel@gnu.org \
--cc=vijay@vijaymarupudi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).