all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars-Dominik Braun <lars@6xq.net>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel@gnu.org
Subject: Re: I'm retiring (for a while); help needed
Date: Fri, 7 Jun 2024 08:35:37 +0200	[thread overview]
Message-ID: <ZmKqOZQ83fSIvS6o@noor.fritz.box> (raw)
In-Reply-To: <87o78mldio.fsf@elephly.net>

Hi Ricardo,

> * maintenance of R, as well as CRAN and Bioconductor packages.

is there anyone who will look after the automated channels
guix-cran/guix-bioc (and possibly guix-science)?

> * Finishing the python-team branch.
> 
>   We wanted to merge the "python-team" branch soon, which contains
>   changes to the pyproject-build-system and many many package updates.
>   Build farm troubles threw a spanner in the works and we were unable to
>   figure out exactly how many packages are now broken due to our
>   changes.  This branch needs a manager who assesses the current status,
>   rebases it, and coordinates the merge.  This should be done after the
>   merge of "core-updates".

I’m still interested in getting this merged, but I have very limited
time on my hands. If no-one else volunteers until you leave, I’ll
do it.

Lars



  parent reply	other threads:[~2024-06-07  6:36 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-31  6:08 I'm retiring (for a while); help needed Ricardo Wurmus
2024-05-31  9:56 ` jbranso
2024-06-01 14:01   ` Ludovic Courtès
2024-06-07  8:05     ` Ricardo Wurmus
2024-06-17 12:39       ` pico.css in Cuirass Ludovic Courtès
2024-06-17 13:22         ` Ricardo Wurmus
2024-06-01 14:03 ` I'm retiring (for a while); help needed Ludovic Courtès
2024-06-04 16:43 ` Simon Tournier
2024-06-04 19:35   ` jbranso
2024-06-07  7:58   ` Ricardo Wurmus
2024-06-28 12:51     ` Laurent Gatto
2024-06-07  6:35 ` Lars-Dominik Braun [this message]
2024-06-07  8:00   ` Ricardo Wurmus
2024-06-17 12:37     ` Ludovic Courtès
2024-06-17 13:38       ` Ricardo Wurmus

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=ZmKqOZQ83fSIvS6o@noor.fritz.box \
    --to=lars@6xq.net \
    --cc=guix-devel@gnu.org \
    --cc=rekado@elephly.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.