unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: jbranso@dismail.de
To: "Ricardo Wurmus" <rekado@elephly.net>, guix-devel@gnu.org
Subject: Re: I'm retiring (for a while); help needed
Date: Fri, 31 May 2024 09:56:02 +0000	[thread overview]
Message-ID: <176393afde572ee99f538acef20265fdaf3af973@dismail.de> (raw)
In-Reply-To: <87o78mldio.fsf@elephly.net>

May 31, 2024 at 2:08 AM, "Ricardo Wurmus" <rekado@elephly.net> wrote:



> 
> Hi Guix,
> 
> in the next few months (from June to the end of October 2024) I won't
> 
> have much time for computers. Unfortunately, this means that my
> 
> projects will stall unless some of you continue them.
> 
> There are only three important projects, and one unimportant project:
> 
> * maintenance of R, as well as CRAN and Bioconductor packages.
> 
>  I used to update all of CRAN and Bioconductor with "./pre-inst-env
> 
>  guix refresh -t {cran,bioconductor} -u", fix the updated package
> 
>  definitions (e.g. to restore undeclared inputs for replacing minified
> 
>  JavaScript), check that all of them build, and then push them to the
> 
>  "r-updates" branch. Then observe failures in the r-updates jobset on
> 
>  ci.guix.gnu.org, and fix those. Finally, rebase the changes, rebuild
> 
>  again, then merge. (This is subject to changes in branch/merge
> 
>  management.)
> 
> * Mentoring.
> 
>  I won't be able to respond to messages sent to the mentors team.
> 
> * 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".
> 
> * Cuirass CSS+JS.
> 
>  I had started to remove Bootstrap CSS+JS and jQuery from Cuirass,
> 
>  i.e. replacing Bootstrap and jQuery JavaScript with plain standard
> 
>  JavaScript, and moving Bootstrap CSS to the much less verbose
> 
>  Pico.css.


I've done some web work in the past.  I could probably help with the
bootstrap -> pico move.
 
> In July I'll be back to hack on Guix for about a week, but other than
> 
> that I won't be monitoring email.
> 
> If you would like to keep these projects alive, please say so here. I
> 
> can provide more information as needed.
> 
> -- 
> 
> Ricardo
>


  reply	other threads:[~2024-05-31  9:56 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 [this message]
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
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

  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=176393afde572ee99f538acef20265fdaf3af973@dismail.de \
    --to=jbranso@dismail.de \
    --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 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).