all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Chris Marusich <cmmarusich@gmail.com>
To: Efraim Flashner <efraim@flashner.co.il>
Cc: guix-devel@gnu.org
Subject: Re: Guix key signing party at FOSDEM?
Date: Sun, 04 Feb 2018 02:17:07 +0100	[thread overview]
Message-ID: <87woztimek.fsf@gmail.com> (raw)
In-Reply-To: <20180203200103.GB1003@macbook41> (Efraim Flashner's message of "Sat, 3 Feb 2018 22:01:03 +0200")

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

Efraim Flashner <efraim@flashner.co.il> writes:

> I have some printed slips with my key to hand out, when do we want to do
> it? Another options is that last year at the key signing party some people
> did show up with some slips and joined the line and handed out slips of
> paper instead of identifying their number.

About 15 of us discussed this over dinner, and we agreed to meet at the
same place and time where FOSDEM will be holding its key signing party
(which is: "Sunday, at 14:00, in the corridor on the second level of the
U building" [1]).  We will meet and conduct our own little key signing
party nearby, without intruding on the main event.

To participate, you just need to (1) know your key fingerprint and
associated user ID, and (2) bring a form of official identification
(e.g., your passport).  To make it easy to share your key fingerprint
and user ID with others, it would be good to create print-outs (or
hand-written copies) so that you can bring them to the party.  When you
do this, please be sure to double check the print-outs for correctness
before coming.

At the party, all we have to do is (1) share fingerprints/user IDs and
(2) verify user IDs using everyone's official form of identification.
There is no need to actually sign keys on the same day.  You can
actually sign the keys later (e.g., after FOSDEM is done - although
sooner is always better!), at which point you should send the signed
keys back to their respective owners.

If there are any errors in what I have said above, please correct me.  I
look forward to doing this together with many of you tomorrow!  As for
you specifically, Efraim: I hope that you will join in after the main
key signing event is done (and that others will stick around long enough
to meet with you, too!).

See you tomorrow,

Footnotes: 
[1]  https://fosdem.org/2018/keysigning/

-- 
Chris

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

  reply	other threads:[~2018-02-04  1:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-03 14:14 Guix key signing party at FOSDEM? Chris Marusich
2018-02-03 14:54 ` Andreas Enge
2018-02-03 20:01   ` Efraim Flashner
2018-02-04  1:17     ` Chris Marusich [this message]
2018-02-04 11:37       ` Efraim Flashner
2018-02-04 16:46 ` Tobias Geerinckx-Rice
2018-02-05 22:50   ` Chris Marusich
2018-02-07 21:51     ` Ludovic Courtès
  -- strict thread matches above, loose matches on Subject: below --
2018-02-03 17:31 Alex ter Weele

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=87woztimek.fsf@gmail.com \
    --to=cmmarusich@gmail.com \
    --cc=efraim@flashner.co.il \
    --cc=guix-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 external index

	https://git.savannah.gnu.org/cgit/guix.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.