From: ludo@gnu.org (Ludovic Courtès)
To: summer-of-code@gnu.org
Cc: gnunet-developers@gnu.org, bug-guix@gnu.org
Subject: GNU Guix GSoC ideas
Date: Mon, 25 Mar 2013 19:11:09 +0100 [thread overview]
Message-ID: <87mwtr4af6.fsf@gnu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2109 bytes --]
Hello,
Please find below project suggestions for GNU Guix for this year’s GSoC.
Thanks,
Ludo’.
<h3 id="guix"><a href="http://www.gnu.org/software/guix">Guix</a></h3>
<p>GNU Guix is a purely functional package manager, and associated free
software distribution, for the GNU system. In addition to standard
package management features, Guix supports transactional upgrades and
roll-backs, unprivileged package management, per-user profiles, and
garbage collection.</p>
<p><strong>Contact:</strong> bug-guix@gnu.org (to subscribe, see the
<a href="http://lists.gnu.org/mailman/listinfo/bug-guix">list-info page</a>).<br/>
<strong>Mentors:</strong> <a href="mailto:ludo@gnu.org">Ludovic Courtès</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>/nix/store/v9zic07iar8w90zcy398r745w78a7lqs-emacs-24.3</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.
</p>
<p>
The “traditional model” has been to have a build farm build and serve
binary packages. 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 file sharing service</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>
Problems to be solved <a
href="http://lists.gnu.org/archive/html/bug-guix/2013-03/msg00085.html">include</a>
the authentication of binary packages, user privacy, and the development
of a user interface that makes it trivial to contribute package build
results.
</p>
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next reply other threads:[~2013-03-25 18:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-25 18:11 Ludovic Courtès [this message]
2013-03-25 20:58 ` GNU Guix GSoC ideas Cyril Roelandt
2013-03-25 21:19 ` Ludovic Courtès
2013-03-26 19:57 ` Giuseppe Scrivano
2013-03-26 23:15 ` Ludovic Courtès
2013-03-26 5:11 ` Ling Kun
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=87mwtr4af6.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=bug-guix@gnu.org \
--cc=gnunet-developers@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 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).