all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Josh <joshua.r.marshall.1991@gmail.com>
To: help-guix@gnu.org
Subject: Re: How to present Guix to a wider audience
Date: Tue, 14 Jan 2020 19:20:31 -0500	[thread overview]
Message-ID: <dcd677f5-09f1-7527-131b-494b10fc7ba6@gmail.com> (raw)
In-Reply-To: <874kwyp9hi.fsf@ambrevar.xyz>

It is purist, and that's hard for a general audience.  To CS and math 
people, this is exactly the way to go.  The start is stronger.  Some of 
Ken Thompson's more worrying work should be included to convey our 
intuitive fear of this to the layperson. The second link may not be all 
that credible, but the story conveys what guix is meant to prevent, and fix.

http://wiki.c2.com/?TheKenThompsonHack

https://www.quora.com/What-is-a-coders-worst-nightmare/answer/Mick-Stute?srid=RBKZ&amp;share=1

https://en.wikipedia.org/wiki/Backdoor_(computing)#Compiler_backdoors

I think some of the buildup to the logical proof can be omitted, with 
just the assertion that with the elements of FLOSS, Reliability, and 
Trust are required and guix is designed to guarantee those would be 
sufficient for the audience.

  parent reply	other threads:[~2020-01-15  0:20 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-02 10:03 How to present Guix to a wider audience Pierre Neidhardt
2020-01-02 18:18 ` zimoun
2020-01-08 15:33   ` Pierre Neidhardt
2020-01-08 16:32     ` Ricardo Wurmus
2020-01-08 20:18     ` zimoun
     [not found]       ` <24DdUL_0dCHlf-Jsotb_z0Mxz7kuUpI_FeBoRrbgJUypYRxvic9u3GhPfBwAiz5ZGjRxITivscu59w_-BPA2cIY_wSbypis89M7Jb8AglBM=@protonmail.com>
     [not found]         ` <CAJ3okZ1CQ1zvbHnFT6EmB+yYFwcAszZ0baroyj03LzTK7AhBXw@mail.gmail.com>
2020-01-10  9:52           ` wisdomlight--- via
2020-01-10 12:19             ` Pierre Neidhardt
2020-01-02 19:20 ` Ricardo Wurmus
2020-01-08 15:26   ` Pierre Neidhardt
2020-01-14 11:23 ` Pierre Neidhardt
2020-01-14 15:58   ` Jack Hill
2020-01-14 17:00     ` Pierre Neidhardt
2020-01-14 21:01       ` Jack Hill
2020-01-14 23:44   ` Dimakakos Dimos
2020-01-15  0:07   ` Vagrant Cascadian
2020-01-15  8:52     ` Pierre Neidhardt
2020-01-15  0:20   ` Josh [this message]
2020-01-15  8:57     ` Pierre Neidhardt
2020-01-15  5:59   ` Arun Isaac
2020-01-15  8:53     ` Pierre Neidhardt
2020-01-15  8:59   ` Pierre Neidhardt
2020-01-15 17:44     ` sirgazil
2020-01-19 11:03       ` Todor Kondić
2020-01-19 15:57         ` wisdomlight
2020-01-21 21:49   ` ndre
2020-01-22 11:00     ` Pierre Neidhardt
2020-01-22 17:35       ` Pierre Neidhardt
2020-01-23 14:44         ` Kelsang Sherab
2020-01-23 21:25           ` Pierre Neidhardt
2020-02-11  7:45   ` Pierre Neidhardt
2020-02-11 17:38     ` Josh Marshall

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=dcd677f5-09f1-7527-131b-494b10fc7ba6@gmail.com \
    --to=joshua.r.marshall.1991@gmail.com \
    --cc=help-guix@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.