all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: "Jose E. Marchesi" <jemarch@gnu.org>
Cc: guix-devel@gnu.org, gnunet-developers@gnu.org, summer-of-code@gnu.org
Subject: Re: GNU in GSOC 2015 - Application sent
Date: Mon, 09 Mar 2015 23:11:43 +0100	[thread overview]
Message-ID: <87zj7lq0rk.fsf@inria.fr> (raw)
In-Reply-To: 87fv9t65x7.fsf@gnu.org

ludo@gnu.org (Ludovic Courtès) skribis:

> Here are three ideas for Guix and dmd.  Others may follow.

Here’s a couple more.


<h4 id="guix_containers">Linux container support</h4>

<p>
  GNU Guix currently supports the installation of GuixSD on virtual
  machines and physical hosts through its <a
  href="/software/guix/manual/html_node/Invoking-guix-system.html"><code>guix
  system</code></a> command.  The goal of this project would be to add
  another installation target: containers.  A container is an
  environment that is similar to a virtual machine but without the
  overhead that comes with running a separate kernel and simulating
  hardware.  Containers are isolated on a host system through Linux's
  control groups and kernel namespaces.
</p>

<strong>Mentor</strong>: <a href="mailto:davet@gnu.org">David Thompson</a>



<h4>Supporting binary package distribution through GNUnet</h4>

<p>
GNU Guix provides a transparent binary/source deployment model.  A
server can claim: “hey, I have the binary for
<tt>/gnu/store/v9zic07iar8w90zcy398r745w78a7lqs-emacs-24.4</tt>!”, where the
base32 string uniquely identifies a build process.  If you trust that
server to provide genuine binaries, then you can grab them instead of
building Emacs locally.  This mechanism is called <a
href="/software/guix/manual/html_node/Substitutes.html"><emph>substitution</emph></a>.
</p>

<p>
The “traditional model” has been to have a build farm build and serve
binary packages over HTTP.  In that model, users trust the build farm to
provide authentic binaries.
</p>

<p>
The project aims to provide a <emph>practical</emph> decentralization
distribution mechanism for binary packages, using <a
href="/software/gnunet">GNUnet’s networking layers</a>.  In that
model, users would be able to automatically share binaries they have
built locally, and to install binaries built by other users.  This is
part of a broader goal of <emph>disintermediation</emph> among users,
and between users and upstream software developers.
</p>

<p>
Deliverables <a
href="http://lists.gnu.org/archive/html/guix-devel/2015-03/msg00192.html">include</a> 
a substituter that uses GNUnet as its back-end, and a tool to publish
build results.
</p>

<strong>Mentors</strong>:
<a href="mailto:totakura@in.tum.de">Sree Harsha Totakura</a>,
<a href="mailto:bart.polot@gmail.com">Bart Polot</a>

Thanks,
Ludo'.

_______________________________________________
GNUnet-developers mailing list
GNUnet-developers@gnu.org
https://lists.gnu.org/mailman/listinfo/gnunet-developers

  parent reply	other threads:[~2015-03-09 22:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <877fvftjg3.fsf@gnu.org>
2015-02-25 21:24 ` GNU in GSOC 2015 - Application sent Ludovic Courtès
2015-02-27 14:47   ` Jose E. Marchesi
2015-03-09 22:11   ` Ludovic Courtès [this message]
2015-03-09 23:33     ` Giuseppe Scrivano
2015-03-10  9:53     ` Sree Harsha Totakura
2015-03-10 14:59       ` Giuseppe Scrivano

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=87zj7lq0rk.fsf@inria.fr \
    --to=ludo@gnu.org \
    --cc=gnunet-developers@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=jemarch@gnu.org \
    --cc=summer-of-code@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.