unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Sean Allred <code@seanallred.com>
Cc: emacs-devel@gnu.org
Subject: Re: CLAHub and the FSF copyright assignment
Date: Sat, 13 Dec 2014 23:24:33 -0500	[thread overview]
Message-ID: <jwvvbleoomu.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <2F7CC5C4-503C-4867-87DC-644F8E4862E4@seanallred.com> (Sean Allred's message of "Sat, 13 Dec 2014 11:53:15 -0500")

> Can GNU/the FSF use this resource to fulfill its copyright assignment?

I do not understand how it could help with the assignment process, which
is mostly a process of getting the paperwork to sign, signing it and
returning it.  This process can be done "fully paperbased" and in some
cases it can be done partly electronically or fully electronically.
The details change overtime, as FSF's lawyers work out new procedures
that are more convenient while still being legally valid.

I don't think there's much tool that can be help streamline this process
(tho maybe a lawyer could help, or maybe lobbying some governments to
change regulations).

Of course, there's the rest of the issue which is to figure out who has
signed the needed paperwork already and who hasn't, and how to make sure
all your contributors have signed paperwork.

As maintainer of a GNU package, I have access to this "copyright.list"
information, but the FSF does not make this info public, since it could
probably be considered as a breach of privacy.

Maybe we could come up with some way to make it easier than having to
ask one of those people with access to the copyright.list.  Maybe we
could create an "Emacs Copyright Assigned" (ECA) GPG key, and signing
a GPG key with this ECA key would mean "this guy has signed the
paperwork already".  Then people can publicly put this signature on
their key if they want to advertise the fact that they have signed the
copyright paperwork.  Or they can show you the key in private if they
don't want it to be public.


        Stefan



      parent reply	other threads:[~2014-12-14  4:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-13 16:53 CLAHub and the FSF copyright assignment Sean Allred
2014-12-13 18:51 ` Paul Eggert
2014-12-13 19:01   ` Rasmus
2014-12-14  1:25 ` Artur Malabarba
2014-12-14  4:19   ` Sean Allred
2014-12-14  8:15     ` Artur Malabarba
2014-12-14 13:37     ` Stefan Monnier
2014-12-14  4:24 ` Stefan Monnier [this message]

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/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=jwvvbleoomu.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=code@seanallred.com \
    --cc=emacs-devel@gnu.org \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).