all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Christopher Baines <mail@cbaines.net>
Cc: guix-devel@gnu.org
Subject: Re: Bringing substitutes from the Guix Build Coordinator to users
Date: Tue, 11 May 2021 22:18:49 +0200	[thread overview]
Message-ID: <875yzpxbva.fsf@gnu.org> (raw)
In-Reply-To: <87fsz2cnj9.fsf@cbaines.net> (Christopher Baines's message of "Tue, 04 May 2021 20:22:02 +0100")

Hi!

Christopher Baines <mail@cbaines.net> skribis:

> Ludovic Courtès <ludo@gnu.org> writes:

[...]

>> A QA entry point like you proposed in the thread you mentioned¹ could
>> certainly help.  A reproducibility entry point would be nice too.  A
>> package browser for guix.gnu.org like the one Danjela worked on would be
>> great too, possibly with version browsing facilities.  And Guix Weekly
>> News!  And the security tracker!  :-)
>>
>> ¹ https://lists.gnu.org/archive/html/guix-devel/2021-02/msg00096.html
>>
>> It seems to me that all that hard work is already done and what I
>> describe above are rather low-hanging fruits.
>>
>> Taking Conway’s law into account, we may find it easier to recruit if as
>> much as possible takes place here, things get deployed behind
>> *.guix.gnu.org, and relevant bits are made part of Guix proper.  And
>> also, we must regularly advertise progress; one blog post in all of the
>> Guix Data Service’s lifetime is not enough.  :-)
>>
>> Thoughts?
>
> This doesn't really relate to the subject of substitutes.

Indeed, I slid off-topic, but it’s all there in the big picture.  :-)

> Some of the things you mention do relate to work I'm trying to progress
> though. I'm still working on automated patch (plus branch) testing, and
> I think having a simple overview of patch+branch states is hopefully
> something that I'll get to at some point.
>
> On the subject of the patch testing stuff, that isn't under
> .guix.gnu.org and I haven't written a blog post yet. I can't see Cuirass
> starting to test patches, but then I wouldn't have predicted it would be
> managing builds across multiple machines. Maybe there are some risks
> with the patch testing work that I haven't done enough/the right stuff
> to mitigate.
>
> I've also got too many things in progress at the moment, with the
> combination of work on substitutes (I hope to implement things set out
> in [1] some point soon), Outreachy, and the security related work that
> I'm trying to start, I need to "finish" some things before starting new
> ones or going back to unfinished things.
>
> 1: https://lists.gnu.org/archive/html/guix-devel/2021-02/msg00104.html

Yeah, I do think polishing, deploying, and advertising some of these
things that are already 80% ready would be a great booster for all of
us.  To help recruit people, we can also deploy at guix.gnu.org things
that are not complete yet (the package browser, Guix Weekly News, the QA
entry point, etc.); it’s always easier once the thing is palatable.

HTH!

Ludo’.


  reply	other threads:[~2021-05-11 20:19 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-01 18:56 Bringing substitutes from the Guix Build Coordinator to users Christopher Baines
2021-05-02 21:51 ` Ludovic Courtès
2021-05-03 10:30   ` Christopher Baines
2021-05-04  8:27     ` Ludovic Courtès
2021-05-04 19:22       ` Christopher Baines
2021-05-11 20:18         ` Ludovic Courtès [this message]
2021-05-04 18:38 ` Andreas Enge
2021-05-04 19:29   ` Christopher Baines
2021-05-12 22:58     ` Christopher Baines
2021-05-15 16:38       ` Ludovic Courtès
2021-05-15 17:24         ` Christopher Baines
2021-05-17 20:28           ` Ludovic Courtès
2021-05-18  8:26             ` Christopher Baines
2021-05-06 16:26   ` Ludovic Courtès
2021-05-18 19:45 ` [bug#48435] " Christopher Baines
2021-05-18 21:24   ` Ludovic Courtès
2021-05-18 22:29     ` Christopher Baines
2021-05-19  6:54       ` Mathieu Othacehe
2021-05-19  7:57         ` Christopher Baines
2021-06-07 14:53   ` Christopher Baines

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=875yzpxbva.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=mail@cbaines.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 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.