all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Julien Lepiller <julien@lepiller.eu>
Cc: 54072-done@debbugs.gnu.org
Subject: bug#54072: [PATCH] [maintenance] roadmap: Update with items from the Guix Days.
Date: Thu, 17 Mar 2022 10:20:16 -0400	[thread overview]
Message-ID: <871qz0bqzj.fsf@gmail.com> (raw)
In-Reply-To: <20220220183944.4a6366fa@tachikoma.lepiller.eu> (Julien Lepiller's message of "Sun, 20 Feb 2022 18:39:44 +0100")

Hi Julien,

Julien Lepiller <julien@lepiller.eu> writes:

> Hi Guix!
>
> Attached is a patch that updates the ROADMAP according to the
> discussions that happened during the Guix Days! We tried to keep the
> items actionnable, so there are more thoughts that we haven't
> transcribed to the roadmap. I'll send all these items we discussed
> during the last session a bit later, and we should turn them into a
> blog post!

Thanks for updating the list.  I've committed it to the maintenance
repo, but some thoughts for the future:

1. Is a TODO in the maintenance repo the right location to track
Guix-specific enhancements?  Since this kind of list is bound to differ
for each of us (based on our personal interests), I've been keeping this
kind of list for myself in my ~/org/guix.org file.  Perhaps having a
"enhancements" page on the LibrePlanet wiki along the page for packaging
requests could be used?

2. How do we decide which item makes it to the list?  Discussing roadmap
items on guix-devel would reach the largest audience I think.

Anyway, food for thought :-).

Thanks for the refreshed list.

Maxim




      parent reply	other threads:[~2022-03-17 14:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-20 17:39 [bug#54072] [PATCH] [maintenance] roadmap: Update with items from the Guix Days Julien Lepiller
2022-03-02 11:46 ` Ludovic Courtès
2022-03-02 13:55   ` zimoun
2022-03-17 14:20 ` Maxim Cournoyer [this message]

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=871qz0bqzj.fsf@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=54072-done@debbugs.gnu.org \
    --cc=julien@lepiller.eu \
    /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.