all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Wilko Meyer <w@wmeyer.eu>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: Call for contribution to the Guix infrastructure
Date: Thu, 06 Jun 2024 21:50:58 +0200	[thread overview]
Message-ID: <871q59zw7x.fsf@wmeyer.eu> (raw)
In-Reply-To: <87h6en5ndg.fsf@inria.fr> ("Ludovic Courtès"'s message of "Fri, 24 May 2024 15:51:39 +0200")

Hi Ludo,

Ludovic Courtès <ludo@gnu.org> writes:
>       - Improve infra monitoring: set up a dashboard to monitor all the
>         infrastructure, and an out-of-band channel to communicate about
>         downtime.
...
>       - Support mirroring: We’d like to make it easy for others to
>         mirror substitutes from ci.guix and bordeaux.guix, perhaps by
>         offering public rsync access.
...
>     We’re also looking for people who’d be willing to have SSH access to
>     some of the infrastructure to help with day-to-day maintenance:
>     restarting a build, restarting the occasional service that has gone
>     wild (that can happen :-)), reconfiguring/upgrading a machine,
>     rebooting, etc.

I think I could spare a couple of hours per week (approx. 4-5h
most of the time realistically with availability in the earlier morning
hours and around the evening, my current timezone is CEST) to assist
with these tasks, especially with maintenance/sysadmin things and with
uptime/infrastructure monitoring if help's still needed for these things.

Even though:

>     Prerequisite: Being a “known” member of the community, familiarity
>     with Guix System administration, with some of the services/web sites
>     being run, and with the infrastructure handbook:
>     <https://git.savannah.gnu.org/cgit/guix/maintenance.git/tree/doc/infra-handbook.org>.

I've been only around for a bit more than a year in this community, so
it's up to others to decide wether I already count as a "known" member
or not.

-- 
Kind regards,

Wilko Meyer
w@wmeyer.eu


  parent reply	other threads:[~2024-06-06 19:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-24 13:51 Call for contribution to the Guix infrastructure Ludovic Courtès
2024-05-26  9:05 ` Jonathan Brielmaier
2024-06-01 13:54   ` Ludovic Courtès
2024-06-04 12:07 ` Carlo Zancanaro
2024-06-06 15:23   ` Ludovic Courtès
2024-06-06 19:50 ` Wilko Meyer [this message]
2024-06-17 12:20   ` Ludovic Courtès
  -- strict thread matches above, loose matches on Subject: below --
2024-06-10 16:04 Zach Oglesby
2024-06-17 12:36 ` Ludovic Courtès
2024-06-17 13:29   ` Zach Oglesby

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=871q59zw7x.fsf@wmeyer.eu \
    --to=w@wmeyer.eu \
    --cc=guix-devel@gnu.org \
    --cc=ludo@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.