From: "Ludovic Courtès" <ludo@gnu.org>
To: Nicolas Graves <ngraves@ngraves.fr>
Cc: 74046@debbugs.gnu.org
Subject: [bug#74046] [PATCH] doc: Add "Contributing to Guix's infrastructure".
Date: Wed, 20 Nov 2024 23:16:15 +0100 [thread overview]
Message-ID: <87bjy9v9e8.fsf@gnu.org> (raw)
In-Reply-To: <87msigp2v3.fsf@ngraves.fr> (Nicolas Graves's message of "Sun, 03 Nov 2024 19:51:44 +0100")
Hi,
Nicolas Graves <ngraves@ngraves.fr> skribis:
> I have no particular knowledge about distributed computing other than a
> past use of BOINC, but I wonder if some contribution in that form would
> be useful in a near future in Guix. I have a beefy machine and would be
> happy to lend ~10 cores for 10h/day to building Guix binaries. Not that
> much, but I like the idea, and I think it also helps to create another
> contribution option and might participate to create a stronger
> community. (By the way, same thing for peer-sharing build results, with
> the same problematics).
That’s not really an option, from a security viewpoint: since the only
way to check that the binaries someone provides really corresponds to
the source is to build them, the binary provider has to be trusted by
its users. A BOINC-style model doesn’t seem practical.
Ludo’.
next prev parent reply other threads:[~2024-11-20 22:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-27 12:45 [bug#74046] [PATCH] doc: Add "Contributing to Guix's infrastructure" Ekaitz Zarraga
2024-10-28 14:50 ` Greg Hogan
2024-11-03 18:51 ` Nicolas Graves via Guix-patches via
2024-11-20 22:16 ` Ludovic Courtès [this message]
2024-11-07 9:03 ` [bug#74046] [PATCH v2] " Ekaitz Zarraga
2024-11-20 22:28 ` Ludovic Courtès
2024-11-20 22:58 ` Ekaitz Zarraga
2024-11-29 12:54 ` Ludovic Courtès
2024-11-29 13:35 ` Ekaitz Zarraga
2024-11-29 14:47 ` bug#74046: [PATCH] " Ekaitz Zarraga
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=87bjy9v9e8.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=74046@debbugs.gnu.org \
--cc=ngraves@ngraves.fr \
/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).