From: Eli Zaretskii <eliz@gnu.org>
To: Phillip Lord <phillip.lord@newcastle.ac.uk>
Cc: larsi@gnus.org, emacs-devel@gnu.org
Subject: Re: Assignment overview (again)
Date: Fri, 25 Dec 2015 09:29:14 +0200 [thread overview]
Message-ID: <838u4jm1f9.fsf@gnu.org> (raw)
In-Reply-To: <DBXPR07MB334DAFF1E889A4B705DE15BC5E70@DBXPR07MB334.eurprd07.prod.outlook.com> (message from Phillip Lord on Thu, 24 Dec 2015 21:40:42 +0000)
> From: Phillip Lord <phillip.lord@newcastle.ac.uk>
> CC: "emacs-devel@gnu.org" <emacs-devel@gnu.org>
> Date: Thu, 24 Dec 2015 21:40:42 +0000
>
> That is a reason why the full list cannot go up, not a reason why any list cannot go up.
What do you mean by "any list"? There are other private details
there, how can we know who and why wouldn't want that to be public
knowledge?
> I think I've seen it suggested before, but there might be an electronic way of achieving this. Like, for example, signing peoples
> GPG key with a FSF key. This would let people assert that they have copyright assigned at least.
Feel free to talk with the FSF about that. Setting up some server
that could be securely queried sounds to me like the best idea and
easiest on users. But any other solution is also fine.
next prev parent reply other threads:[~2015-12-25 7:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-24 19:31 Assignment overview (again) Lars Ingebrigtsen
2015-12-24 19:37 ` Lars Ingebrigtsen
2015-12-24 19:37 ` Eli Zaretskii
2015-12-24 19:41 ` Lars Ingebrigtsen
2015-12-24 19:50 ` Eli Zaretskii
2015-12-24 20:00 ` Lars Ingebrigtsen
2015-12-24 21:40 ` Phillip Lord
2015-12-25 7:29 ` Eli Zaretskii [this message]
2016-01-07 0:16 ` Phillip Lord
2016-01-07 3:40 ` Eli Zaretskii
2016-01-08 5:54 ` Richard Stallman
2016-01-08 13:48 ` Phillip Lord
2016-01-08 14:55 ` Jose E. Marchesi
2016-01-08 15:37 ` Eli Zaretskii
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=838u4jm1f9.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.org \
--cc=phillip.lord@newcastle.ac.uk \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.