From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-project <gentoo-project@lists.gentoo.org>
Cc: gentoo-dev-announce@lists.gentoo.org, elections@gentoo.org
Subject: [gentoo-project] Re: [gentoo-dev-announce] Gentoo Council Election Results for term 2019/2020
Date: Wed, 10 Jul 2019 23:02:48 +0200 [thread overview]
Message-ID: <e2605c5f7901e6b5c93d52103602fcc2efcb0b5c.camel@gentoo.org> (raw)
In-Reply-To: <VQU4LK2N.SVCL5WXR.OYMSX3A3@VK3RXPYD.IEYP7CEY.6DED6ZNQ>
[-- Attachment #1: Type: text/plain, Size: 2884 bytes --]
On Sun, 2019-07-07 at 16:56 +0100, Roy Bamford wrote:
>
> The master ballot file is attached to this e-mail. Please use the ID
> that will be sent to you in the confirmation email to verify that your
> vote was included in the master ballot file. If you don't get your
> ID or you can't find your vote inside the ballot file, please contact the
> election officials (elections@g.o or #gentoo-elections on freenode).
>
Hope you don't mind me hijacking this thread but I'd like to try to
encourage developers to not only implicitly verify their votes but also
participate in the explicit verification process via app-misc/votrify.
First of all, please note that this tool does not invade your privacy.
The resulted confirmations do not contain your votes, or even indicate
whether you voted at all. They only say 'yes, I did verify the vote
and got the following result...'.
Secondly, devs who did not vote (but were eligible) also count towards
improving the reliability of vote. So even if you hadn't voted, please
consider participating.
If you're interested in some background, you can read my today's blog
post [1]. If you want to help, here are almost-copy-paste instructions.
Start by installing votrify; it will also pull election data in:
emerge -nv app-misc/votrify
If you voted in the election, get your vote file from woodpecker,
and find your confirmation ID in mail:
scp dev.gentoo.org:.ballot-council-201906-submitted .
Then run the tool like this, substituting XXXX for your confirmation ID,
and changing your vote path if necessary:
votrify-make-confirmation -v .ballot-council-201906-submitted \
-c XXXX \
-b /usr/lib/gentoo-elections/completed/council-201906/ballot-council-201906 \
-m /usr/lib/gentoo-elections/completed/council-201906/master-council-201906 |
tee ${USER}.gpg
If you have *not* voted, use '-n' instead of '-v' + '-b':
votrify-make-confirmation -n \
-b /usr/lib/gentoo-elections/completed/council-201906/ballot-council-201906 \
-m /usr/lib/gentoo-elections/completed/council-201906/master-council-201906 |
tee ${USER}.gpg
('tee' so you see what gets produced)
If everything verifies fine, a file named "${USER}.gpg" should be
written. If your username is not reasonably unique, please rename it.
Afterwards, scp the file to woodpecker:
scp ${USER}.gpg dev.gentoo.org:/space/votrify-council201906/
When more files are uploaded there, anyone will be able to fetch them
and verify the results:
scp dev.gentoo.org:/space/votrify-council201906/*.gpg .
votrify-verify-confirmations \
-v /usr/lib/gentoo-elections/completed/council-201906/voters-
council-201906 \
*.gpg
TIA.
[1] https://blogs.gentoo.org/mgorny/2019/07/09/verifying-gentoo-election-results-via-votrify/
--
Best regards,
Michał Górny
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 618 bytes --]
next prev parent reply other threads:[~2019-07-10 21:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-07 15:56 [gentoo-project] Gentoo Council Election Results for term 2019/2020 Roy Bamford
2019-07-08 1:14 ` Benda Xu
2019-07-10 21:02 ` Michał Górny [this message]
2019-07-12 13:08 ` [gentoo-project] Re: [gentoo-dev-announce] " Michał Górny
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=e2605c5f7901e6b5c93d52103602fcc2efcb0b5c.camel@gentoo.org \
--to=mgorny@gentoo.org \
--cc=elections@gentoo.org \
--cc=gentoo-dev-announce@lists.gentoo.org \
--cc=gentoo-project@lists.gentoo.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox