From: ludo@gnu.org (Ludovic Courtès)
To: summer-of-code@gnu.org
Cc: Guix Development <guix-devel@gnu.org>
Subject: GSoC ideas for GNU Guix
Date: Wed, 19 Feb 2014 23:08:43 +0100 [thread overview]
Message-ID: <877g8q4uxg.fsf@inria.fr> (raw)
[-- Attachment #1: Type: text/plain, Size: 2812 bytes --]
Good evening!
Below is a list of GSoC ideas for GNU Guix.
Guix people: you’re welcome to put your name as the mentor of one of the
projects below, and to propose other ideas.
Thanks!
Ludo’.
<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>
<strong>Mentor</strong>: <a href="mailto:ludo@gnu.org">Ludovic Courtès</a>
<h4>Package management from Emacs</h4>
<p>
The goal of this project is to write a complete package management
user interface for use in GNU Emacs. The UI would provide the
same functionality as the <tt>guix package</tt> command, but using an
interface similar to that of <tt>package.el</tt>.
</p>
<strong>Mentor</strong>: <a href="mailto:ludo@gnu.org">Ludovic Courtès</a>
<h4>Porting Guix to GNU/Hurd</h4>
<p>
GNU Guix currently supports building packages for GNU/Linux only. The
goal of this project would be to allow it to cross-build and build
packages for GNU/Hurd, and to provide a virtual machine image that
boots into such a system.
</p>
<p>
This would involve packaging Mach/Hurd/MiG/libc, adjusting allowing
cross-compilation to GNU/Hurd, cross-compiling the “bootstrap
binaries” for GNU/Hurd, and then working towards support for GNU/Hurd
in the <code>(gnu system)</code> Guix modules. This last point would
allow a VM image of the complete system to be built.
</p>
<strong>Mentor</strong>: <a href="mailto:ludo@gnu.org">Ludovic Courtès</a>
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next reply other threads:[~2014-02-19 22:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-19 22:08 Ludovic Courtès [this message]
2014-02-19 22:27 ` GSoC ideas for GNU Guix Jose E. Marchesi
[not found] ` <87iosagz9m.fsf@yagnesh.org>
2014-02-20 11:05 ` [GSoC] Emacs UI for Guix Ludovic Courtès
2014-02-22 20:35 ` Yagnesh Raghava Yakkala
2014-02-27 13:33 ` Ludovic Courtès
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=877g8q4uxg.fsf@inria.fr \
--to=ludo@gnu.org \
--cc=guix-devel@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).