all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: guix-devel <guix-devel@gnu.org>
Subject: Medium-term road map
Date: Sat, 25 Apr 2020 15:37:44 +0200	[thread overview]
Message-ID: <87mu6zd6tz.fsf@gnu.org> (raw)

Hello Guix!

We released 1.1.0, but what’s coming next?  What would you like to see?

There are many exciting things being developed and great ideas floating
around.  For myself, I feel like focusing on “consolidating” what we
have in the coming weeks.  Here are the areas I hope to focus on (and
embarking as many of you as possible :-)):

  1. Authentication.  I want to finally provide a standardized mechanism
     to allow channels to be authenticated upon ‘guix pull’.  “make
     authenticate” was a first milestone, let’s get it done.  See
     <https://issues.guix.gnu.org/issue/22883>.

  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>.

     Related to that is the question of substitute availability, another
     major hindrance to usability.  We should address this both in the
     build farm (reducing the
     time-to-push-to-time-of-substitute-availability, tracking random
     build failures), and on the client side (can we provide ways for
     users to pull to a commit that won’t require them to build
     everything from source, while not compromising on their security?).

  3. G-exps.  We should really finish the migration to gexps, as in the
     ‘wip-build-system-gexp’ branch, and adjust our APIs accordingly.

  4. User interface.  Let’s get our act together with ‘guix shell’ and
     ‘guix run-script’, and let’s address other annoyances that
     newcomers keep stumbling upon!

Thoughts?

Happy hacking!  :-)

Ludo’.

             reply	other threads:[~2020-04-25 13:37 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-25 13:37 Ludovic Courtès [this message]
2020-04-25 16:23 ` Medium-term road map 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
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

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

  git send-email \
    --in-reply-to=87mu6zd6tz.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@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.