From: "Ludovic Courtès" <ludo@gnu.org>
To: Christopher Baines <mail@cbaines.net>
Cc: guix-devel@gnu.org
Subject: Re: Medium-term road map
Date: Sun, 03 May 2020 22:11:18 +0200 [thread overview]
Message-ID: <874kswye1l.fsf@gnu.org> (raw)
In-Reply-To: <877dy2nmgr.fsf@cbaines.net> (Christopher Baines's message of "Sun, 26 Apr 2020 19:14:28 +0100")
Hi!
Christopher Baines <mail@cbaines.net> skribis:
> Ludovic Courtès <ludo@gnu.org> writes:
>
>> We released 1.1.0, but what’s coming next? What would you like to see?
>
> Thanks for starting this thread Ludo, I love this kind of thinking :)
Though I realize now that I have an email problem that introduces a
significant delay in my response time, and I apologize for it!
>> 2. Performance. There are many things we can improve there, first and
>> foremost: the “Computing derivation” part of ‘guix pull’, Guile’s
>> compiler terrible time and space requirements, further optimizing
>> core operations like ‘package-derivation’, as well as low-level
>> stuff as described at <https://issues.guix.gnu.org/issue/40626>.
>
> I remember saying that the Guix Data Service times various things, and
> that it could time the "Computing derivation" bit, but it doesn't store
> that data currently. While the performance is dependent on what else is
> going on at the same time, it might be interesting to store the data to
> see if there's a trend going forward.
Yup!
Performance monitoring in general would be nice, and could have been a
subject for GSoC/Outreachy.
> The other things on my mind are:
>
> Patch submission and review, some information in [2]. I at least want to
> do some more work on the Guix Data Service to make the comparisons more
> useful for reviewing patches, as well as seeing if I can get the Guix
> Build Coordinator to build the affected things, and report back. Then
> there are all the issues around submitting packages, like how do I know
> if someone is working on this already, or how do I know this hasn't been
> updated on core-updates, and how can actually submitting patches be made
> easier.
>
> 2: https://lists.gnu.org/archive/html/guix-devel/2020-03/msg00476.html
Would be nice.
> More sophisticated policies on accepting substitutes, this means being
> able to say things like "I trust substitutes if there signed by all
> these keys/entities". While most of the work on reproducible builds has
> been on getting things to build reproducibly, Guix could lead the way on
> doing the user facing side of this. A majority of the substitutes for
> x86_64-linux match between Bayfront and Berlin, so we already have a
> minimially viable "rebuilder" setup to actually make use of this.
+1!
Thanks,
Ludo’.
next prev parent reply other threads:[~2020-05-03 20:11 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-25 13:37 Medium-term road map Ludovic Courtès
2020-04-25 16:23 ` Pierre Neidhardt
2020-05-03 20:13 ` Ludovic Courtès
2020-04-25 21:38 ` Jack Hill
2020-04-26 1:22 ` Josh Marshall
2020-05-03 20:18 ` Ludovic Courtès
2020-05-06 17:03 ` [EXT] " Thompson, David
2020-05-06 18:58 ` Efraim Flashner
2020-05-06 19:46 ` Jack Hill
2020-05-07 12:24 ` [EXT] " Thompson, David
2020-04-26 16:06 ` zimoun
2020-04-26 18:20 ` Christopher Baines
2020-05-03 20:07 ` Ludovic Courtès
2020-05-04 10:32 ` zimoun
2020-04-26 18:14 ` Christopher Baines
2020-05-03 20:11 ` Ludovic Courtès [this message]
2020-04-27 8:16 ` Andy Wingo
2020-04-27 13:06 ` Christopher Lemmer Webber
2020-04-30 21:27 ` Joshua Branson
2020-05-05 23:50 ` raingloom
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=874kswye1l.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 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).