unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Léo Le Bouter" <lle-bout@zaclys.net>
To: Bengt Richter <bokr@bokr.com>, Leo Famulari <leo@famulari.name>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: Security-czar needed? WAS: Re: Release 1.2.1: zstd 1.4.4 -> 1.4.9: grafting or core-updates?
Date: Wed, 17 Mar 2021 07:24:02 +0100	[thread overview]
Message-ID: <6550f60a302ab3f633fa121e665e66e419cb5cee.camel@zaclys.net> (raw)
In-Reply-To: <20210316214611.GA17584@LionPure>

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

On Tue, 2021-03-16 at 22:46 +0100, Bengt Richter wrote:
> I would feel better about running guix on my laptop if I
> knew all you developers had gotten together and elected
> a "security czar" who is the most competent of you to monitor
> security and also cares the most, and had the power to prevent
> applying unreviewed patches, and making sure all CVEs are taken
> care of, and kitchen doors not left open the way we did in the '50s.
> 
> Sorry if it sounds like I think guix security is lax.
> Please convince me it's not so ;)
> 
> Thanks, nevertheless, for all the great technical work!
> 
> Just wish I could type
>     guix --what-and-who-am-I-trusting-q --full-report
> and get a complete list, with batting averages of the
> developers (regressions vs fixes), packages (estimated
> number of times executed without problem, dangerous bugs
> in development history, etc).
> 
> </rant>
> 

I think we can handle this without granting us any special powers, I
like it that we don't have roles actually!

We can discuss, debate, agree to common goals, I don't think we are
going to enter into conflict, we hear each other, we communicate, I
think that's a really good thing in GNU Guix :-D

Lots of other communities enter into conflict fast and stop
communicating, GNU Guix is not that, there's a spirit of goodwill of
everyone and that's really pleasing to live as a contributor and user.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  parent reply	other threads:[~2021-03-17  6:24 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-06  5:09 GNU Guix (pull?) on i686 broke after zstd grafting Léo Le Bouter
2021-03-06  5:30 ` Léo Le Bouter
2021-03-10 10:37 ` Ludovic Courtès
2021-03-10 10:43   ` Léo Le Bouter
2021-03-11  2:11   ` Léo Le Bouter
2021-03-11  9:37     ` zimoun
2021-03-11  9:40       ` Léo Le Bouter
2021-03-11  9:58         ` zimoun
2021-03-11 10:05           ` Léo Le Bouter
2021-03-16 16:34 ` Release 1.2.1: zstd 1.4.4 -> 1.4.9: grafting or core-updates? zimoun
2021-03-16 17:06   ` Léo Le Bouter
2021-03-16 17:48     ` Leo Famulari
2021-03-16 18:03       ` Léo Le Bouter
2021-03-16 17:59     ` zimoun
2021-03-16 17:55   ` Leo Famulari
2021-03-16 18:08     ` Léo Le Bouter
2021-03-16 18:46       ` zimoun
2021-03-16 18:50         ` Léo Le Bouter
2021-03-16 19:04           ` zimoun
2021-03-16 18:19     ` zimoun
2021-03-16 18:26       ` Léo Le Bouter
2021-03-16 19:18       ` Leo Famulari
2021-03-16 19:25         ` zimoun
2021-03-16 19:29           ` Leo Famulari
2021-03-16 21:46             ` Security-czar needed? WAS: " Bengt Richter
2021-03-16 22:03               ` Leo Famulari
2021-03-17  6:24               ` Léo Le Bouter [this message]
2021-03-17 14:00                 ` zimoun
2021-03-16 21:47             ` Maxime Devos
2021-03-16 20:53     ` Tobias Geerinckx-Rice
2021-03-16 21:18       ` Vincent Legoll
2021-03-16 21:56         ` Leo Famulari
2021-03-17  6:40       ` Léo Le Bouter
2021-03-30  0:35   ` Léo Le Bouter

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://guix.gnu.org/

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

  git send-email \
    --in-reply-to=6550f60a302ab3f633fa121e665e66e419cb5cee.camel@zaclys.net \
    --to=lle-bout@zaclys.net \
    --cc=bokr@bokr.com \
    --cc=guix-devel@gnu.org \
    --cc=leo@famulari.name \
    /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/guix.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).