From: "Ludovic Courtès" <ludo@gnu.org>
To: Carlo Zancanaro <carlo@zancanaro.id.au>
Cc: guix-devel@gnu.org
Subject: Re: Call for contribution to the Guix infrastructure
Date: Thu, 06 Jun 2024 17:23:17 +0200 [thread overview]
Message-ID: <87o78e2ize.fsf@gnu.org> (raw)
In-Reply-To: <87r0dc52sk.fsf@zancanaro.id.au> (Carlo Zancanaro's message of "Tue, 04 Jun 2024 22:07:55 +1000")
Hello Carlo,
Carlo Zancanaro <carlo@zancanaro.id.au> skribis:
> On Fri, May 24 2024, Ludovic Courtès wrote:
>> • Day-to-day system administration
>>
>> 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 help with this. I can't guarantee that I'll always be
> available, but I'm able and willing to help where I can.
[...]
> My timezone has generally made it hard for me to be actively involved in
> real-time conversations about Guix (I'm in Australia), so hopefully that
> wouldn't be too much of an impediment here. It might even be an asset,
> if you don't already have people available in this timezone.
Excellent. If you’re fine with this, I/we can add you to the
guix-sysadmin mailing list, which is private (we can discuss
non-security-sensitive issues such as bugs in infra software here, of
course).
A sample of the kind of tasks we’ve had in recent days: ci.guix needing
close monitoring to ensure it smoothly processes builds, redeployment
needed because i586-gnu builders of ci.guix went unavailable due to
<https://issues.guix.gnu.org/69401> (trying to do that currently),
qa.guix throwing exceptions for some issues.
Often reporting an issue of that sort on IRC is already one step towards
a solution.
> I'm not sure if I count as a "known" member of the community, but I have
> been around the periphery for a while. My earliest commit that made it
> into Guix is from 2016, and I made it to the Guix day in 2018. I have
> been running my own personal infrastructure primarily on Guix since at
> least 2018.
You definitely count as a “known member”. :-)
Thanks for volunteering!
Ludo’.
next prev parent reply other threads:[~2024-06-06 15:24 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 [this message]
2024-06-06 19:50 ` Wilko Meyer
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
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=87o78e2ize.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=carlo@zancanaro.id.au \
--cc=guix-devel@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 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).