unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: "Dr. Arne Babenhauserheide" <arne_bab@web.de>
To: Jean Abou Samra <jean@abou-samra.fr>
Cc: "Ludovic Courtès" <ludo@gnu.org>, "Andy Wingo" <wingo@pobox.com>,
	guile-devel@gnu.org
Subject: Re: Relaxing the copyright assignment policy
Date: Thu, 06 Oct 2022 22:59:55 +0200	[thread overview]
Message-ID: <877d1c64rz.fsf@web.de> (raw)
In-Reply-To: <d92c95ce-e898-a6cd-8143-de46ae689575@abou-samra.fr>

[-- Attachment #1: Type: text/plain, Size: 908 bytes --]


Jean Abou Samra <jean@abou-samra.fr> writes:
> When I did this copyright assignment for Emacs, I recall
> that the procedure was a bit demotivating (the person
> was very friendly, but when you live in an isolated area
> and don't have a printer and you must print the document
> to sign it ...).

It also sounds good to me — though I had the experience that getting the
paperwork done to be allowed to license code written in my free time
under free licenses while employed was much more work than assigning the
copyright for Emacs.

This came up due to copyright assignment, but it was not caused by it.
It was caused by employment laws granting the employer power over the
code that employees write in their free time.

(luckily my employer signed the employer disclaimer of rights)

Best wishes,
Arne
-- 
Unpolitisch sein
heißt politisch sein,
ohne es zu merken.
draketo.de

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 1125 bytes --]

  reply	other threads:[~2022-10-06 20:59 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 [this message]
2022-10-06 20:45 ` Thompson, David
2022-10-07  9:58 ` Maxime Devos
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=877d1c64rz.fsf@web.de \
    --to=arne_bab@web.de \
    --cc=guile-devel@gnu.org \
    --cc=jean@abou-samra.fr \
    --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).