unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: raingloom <raingloom@riseup.net>
Cc: guix-devel@gnu.org
Subject: Re: [opinion] CVE-patching is not sufficient for package security patching
Date: Tue, 23 Mar 2021 23:54:54 +0100	[thread overview]
Message-ID: <875z1hv5tt.fsf@elephly.net> (raw)
In-Reply-To: <20210322144404.1636b9cf@riseup.net>


raingloom <raingloom@riseup.net> writes:

> On Sat, 20 Mar 2021 12:19:11 +0100
> Ludovic Courtès <ludo@gnu.org> wrote:
>
>> Hi,
>> 
>> Mark H Weaver <mhw@netris.org> skribis:
>> 
>> > Ultimately, I gave up.  In my opinion, Guix has never achieved
>> > usability as a desktop system on non-Intel systems.  Therefore, the
>> > Guix community is unable to attract many developers who want a
>> > distro that supports non-Intel systems well.  Our community has
>> > thus become dominated by Intel users, and there's unsufficient
>> > political will to adopt policies that would enable us to provide a
>> > usable system for non-Intel users.  
>> 
>> A practical problem that’s been mentioned repeatedly is lack of
>> ci.guix hardware for non-Intel architectures: please everyone,
>> consider helping the project find either sponsors or companies that
>> sell fitting hardware, along with a plan to host it and maintain it
>> over time!
>> 
>> Ludo’.
>> 
>
> What about a Liberapay for Guix? Could also be used to pay developers.

This seems to be a misunderstanding.  The first step is to use the money
we already have but cannot exchange for hardware, because

- finding appropriate hardware that you can actually buy is not easy
- hosting needs to be considered because we can’t just dump them in the
  MDC data centre where most of the Intel servers are hosted.

We bought a handful of Overdrive 1000 in the past (they are no longer
sold), and hosting was always an obstacle.

While looking for ways to get the project some more money is certainly
worthwhile, it’s really not the pressing issue here.

-- 
Ricardo


  parent reply	other threads:[~2021-03-23 22:55 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-16 11:10 [opinion] CVE-patching is not sufficient for package security patching Léo Le Bouter
2021-03-16 11:17 ` Jonathan Brielmaier
2021-03-16 11:27   ` Léo Le Bouter
2021-03-16 19:15 ` Leo Famulari
2021-03-16 23:19 ` Mark H Weaver
2021-03-16 23:49   ` Leo Famulari
2021-03-17 11:54     ` Guix moving too fast? zimoun
2021-03-17  6:07   ` [opinion] CVE-patching is not sufficient for package security patching Léo Le Bouter
2021-03-17  6:21   ` Léo Le Bouter
2021-03-20 11:19   ` Ludovic Courtès
2021-03-22 13:44     ` raingloom
2021-03-23 16:22       ` Joshua Branson
2021-03-23 23:53         ` Mark H Weaver
2021-03-23 17:56       ` Leo Famulari
2021-03-23 22:54       ` Ricardo Wurmus [this message]
2021-03-24 19:51         ` Leo Famulari
2021-03-24 20:24           ` Vincent Legoll
2021-03-24 20:32             ` Léo Le Bouter
2021-03-24 20:55             ` Leo Famulari
2021-03-25 14:22           ` Mathieu Othacehe
2021-03-25 18:19             ` Leo Famulari
2021-03-30  8:42           ` Buying AArch64 hardware? Ludovic Courtès

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=875z1hv5tt.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=guix-devel@gnu.org \
    --cc=raingloom@riseup.net \
    /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).