From: Maxime Devos <maximedevos@telenet.be>
To: "Ludovic Courtès" <ludo@gnu.org>, guile-devel@gnu.org
Cc: Andy Wingo <wingo@pobox.com>
Subject: Re: Relaxing the copyright assignment policy
Date: Fri, 7 Oct 2022 11:58:10 +0200 [thread overview]
Message-ID: <48012d32-985c-c09d-eb30-755e6e96fff2@telenet.be> (raw)
In-Reply-To: <87tu4ghfk7.fsf@inria.fr>
[-- Attachment #1.1.1: Type: text/plain, Size: 1191 bytes --]
On 06-10-2022 22:18, Ludovic Courtès wrote:
> Hello Guilers!
> [...]
> New contributors are encouraged to assign copyright to the FSF by
> emailing them one of the forms at
> <https://git.savannah.gnu.org/cgit/gnulib.git/plain/doc/Copyright/>,
> especially if they intend to contribute significantly going forward.
>
> New contributors may instead choose to not assign copyright to the FSF.
What about the following third situation: the contributor doesn't mind
assigning Guile-related copyright to the FSF, but the assignment process
can take or is taking a long time or there are some disagreements with
the assignment contract to resolve (which might not even be possible in
the end), so
(1) first the contributor sends the patches without copyright
assignment
(2) then they are applied (after review, revisions, etc.)
(3) once/if the assignment completes, the copyright headers in Guile
are adjusted appropriately.
-- this avoids the time delay, while at the same time hopefully
eventually doing the assignment.
Would such a situation be accepted? (It doesn't quite fit the two
mentioned options.)
Greetings,
Maxime.
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 929 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]
next prev parent reply other threads:[~2022-10-07 9:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-06 20:18 Relaxing the copyright assignment policy Ludovic Courtès
2022-10-06 20:34 ` Jean Abou Samra
2022-10-06 20:59 ` Dr. Arne Babenhauserheide
2022-10-06 20:45 ` Thompson, David
2022-10-07 9:58 ` Maxime Devos [this message]
2022-10-07 12:05 ` Ludovic Courtès
2022-10-08 14:07 ` Jean Abou Samra
2022-10-29 5:44 ` Ian Kelling
2022-10-29 6:39 ` Ian Kelling
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=48012d32-985c-c09d-eb30-755e6e96fff2@telenet.be \
--to=maximedevos@telenet.be \
--cc=guile-devel@gnu.org \
--cc=ludo@gnu.org \
--cc=wingo@pobox.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).