From: pukkamustard <pukkamustard@posteo.net>
To: Shivam Madlani <shivammadlani5@gmail.com>
Cc: Attila Lendvai <attila@lendvai.name>,
guix-devel@gnu.org, Christopher Baines <mail@cbaines.net>
Subject: Re: Hello GUIX
Date: Wed, 29 Mar 2023 09:55:25 +0000 [thread overview]
Message-ID: <86sfdnrhn1.fsf@posteo.net> (raw)
In-Reply-To: <CAAa6Hddp8UPCJvQsdhir4SDjKF8csGVjV7DPoxrfJo_af3zsuA@mail.gmail.com>
Hi Shivam,
Welcome to Guix! I think that Sneakernet-esque distribution of
substitutes is very interesting and something that was also talked about
at the Guix Days before FOSDEM 23 (Guix with no internet and air-gapped
machines).
Some comments on the proposal:
- You might want to refer to the document "SQLite for ERIS block
storage" (https://eris.codeberg.page/eer/sqlite.xml).
- I think the user experience as described in the proposal could be
improved/might not quite work as expected:
- Reading from a disk maybe should happen automagically if it can be
detected (and is enabled in some configuration). This might also
require some integration with udisks. The complexity of this should
not be underestimated.
- Writing packages to a USB stick seems to be closer to a `guix
publish` or `guix deploy`. Maybe you can read up on those commands
and think of a nice way to publish or deploy a set of packages to a
USB stick. This is also relevant for publishing to other p2p
networks (IPFS, GNUnet, etc.).
- Maybe the Narinfos also need to packed onto the USB drive? How would
an air-gapped computer otherwise know which substitute to get? Also
have a look at the nar-herder tool
(https://git.cbaines.net/guix/nar-herder) by Christopher Baines (in
CC).
-pukkamustard
Shivam Madlani <shivammadlani5@gmail.com> writes:
> Hey everyone!
> I am Shivam Madlani, an undergraduate at DAIICT, India. I want to participate in GSoC'23 for The GNU
> organization. The project "Decentralized substitute distribution" in GUIX amused me and I want to
> apply for the same. I have been in touch with the project mentor -pukkamustard for over a month
> now and started learning more about the project. I'm very excited to work on this project as it lies in
> my interests.
>
> I've drafted a proposal on this project and I aim to add a transport protocol-Sneakernet. This will allow
> the substitutes to be air-gappable. My approach is to use SQLite to store the ERIS encoded substitute
> in the external drive using a custom schema. This is just a brief overview of the project and more
> details are included in the attached proposal.
>
> I would love to hear your thoughts and reviews on my proposal and hopefully improve it by filling in
> any missing key points.
>
> Thank you,
> Shivam
>
> [4. application/pdf; GSoC'23 GUIX proposal.pdf]...
next prev parent reply other threads:[~2023-03-29 10:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-26 18:27 Hello GUIX Shivam Madlani
2023-03-29 9:55 ` pukkamustard [this message]
2023-03-31 9:16 ` Shivam Madlani
2023-04-06 1:23 ` Csepp
2023-04-07 9:54 ` Shivam Madlani
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=86sfdnrhn1.fsf@posteo.net \
--to=pukkamustard@posteo.net \
--cc=attila@lendvai.name \
--cc=guix-devel@gnu.org \
--cc=mail@cbaines.net \
--cc=shivammadlani5@gmail.com \
/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).