In the short term I'd like to merge the python optimisations. We discussed it before release and thought it might be nice to merge them before c-u, from a separate branch.

Maybe before next release we'll have our separate repo on savannah for translations (it's currently a repo I manage on framagit). I'd also like to add some automation so I don't have to manually update the pot files :)

Le 15 mai 2021 13:47:19 GMT-04:00, "Ludovic Courtès" <ludo@gnu.org> a écrit :
Hello Guix!

So, now that 1.3.0 is out the door, what’s next?!

Here’s my wish list of things that look achievable within 4 to 6 months
(I hope to help on some of these):

• Merging Guix Home.

• Completing and consolidating Disarchive support (see
<https://issues.guix.gnu.org/47336>): continuously building the
Disarchive database, making sure it’s replicated or backed up by
SWH, and having a blog post or two explaining the whole endeavor
(I’m looking at you, Timothy ;-)).

• Merging Magali’s ‘guix git log’ work.

• Merging ‘core-updates’, perhaps with a switch to GCC 10? Perhaps
with support for “simplified packages” (getting rid of input
labels)? We’ll see how much can go in there, but the sooner the
better.

• On ‘core-updates’, merging either the full-source bootstrap or
the reduced bootstrap on ARM, whichever comes first. :-)

• Consolidating the POWER9 and AArch64 ports (more build machines
behind ci.guix!).

• Maybe a step towards “early cutoffs” to reduce the amount of
rebuilding (more on that in a future post).

• Maybe optimized substitute downloads based on
<https://lists.gnu.org/archive/html/guix-devel/2021-01/msg00080.html>
or at the store item level (same as for early cutoffs).

• Maybe parameterized packages based on
<https://lists.gnu.org/archive/html/guix-devel/2020-11/msg00312.html>.

What do people think? What’s your wish list? What do you feel an urge
to hack on? :-)

Ludo’.