From: Jonathan Brielmaier <jonathan.brielmaier@web.de>
To: "Ludovic Courtès" <ludo@gnu.org>, guix-devel@gnu.org
Subject: Re: Call for contribution to the Guix infrastructure
Date: Sun, 26 May 2024 11:05:15 +0200 [thread overview]
Message-ID: <1a7188a3-25c0-465d-9d1d-f6b45b9507c7@web.de> (raw)
In-Reply-To: <87h6en5ndg.fsf@inria.fr>
Hello Ludo,
Am 24.05.24 um 15:51 schrieb Ludovic Courtès:
> • Hosting
>
> We’re looking for people who can host machines and help out whenever
> physical access is needed. More specifically:
>
> - We need hosting of “small” machines such as single-board
> computers (AArch64, RISC-V) for use as build machines.
>
> - We need hosting for front-ends and x86_64 build machines in a
> data center where they can be racked and where, ideally, several
> local Guix sysadmins can physically access them.
>
> The machines should be accessible over Wireguard VPN most of the
> time, so longer power or network interruptions should be the
> exception.
>
> Prerequisites: Familiarity with installing and remotely
> administering Guix System.
I offered my help in hosting an ARM build machine (Softiron Overdrive)
at home to guix-sysadmin@gnu.org in March 2024.
But apart from Maxim's reply I did not receive an answer from the Guix
Sysadmins...
~Jonathan
next prev parent reply other threads:[~2024-05-26 9:05 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 [this message]
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
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=1a7188a3-25c0-465d-9d1d-f6b45b9507c7@web.de \
--to=jonathan.brielmaier@web.de \
--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.