all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Pjotr Prins <pjotr.public12@thebird.nl>
To: Mathieu Othacehe <m.othacehe@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: FOSDEM is coming!
Date: Sun, 24 Nov 2019 01:59:06 -0600	[thread overview]
Message-ID: <20191124075906.cixrxhrst35wzba2@thebird.nl> (raw)
In-Reply-To: <87blt2efn3.fsf@gmail.com>

On Sat, Nov 23, 2019 at 05:12:00PM +0100, Mathieu Othacehe wrote:
> 
> Hey Ludo,
> 
> > It’d be nice if you could present what you’ve been doing in or around
> > Guix there, particularly in tracks that would allow us to reach out to
> > people we don’t usually get to talk to.  There’s been a lot of work on a
> > variety of hot topics: bootstrapping (Mes & co., Rust, etc.), Guix Home,
> > Guix Data Service, ‘guix deploy’, GWL, Guix on ARM, etc. let’s talk
> > about it!
> 
> I submited a talk to minimalistic devroom titled: "GNU Guix as an
> alternative to the Yocto Project". Maybe the distributions devroom would
> have been more appropriate.
> 
> The point of this talk is to compare the process of creating a small
> root filesystem on Guix and Yocto for an embedded device (Pine A64
> LTS).

Hi Mathieu,

You can submit to both devrooms. As a coordinator of the minimalistic
devroom I think your talk fits. Mind, it still needs to go through the
review of the devroom to get selected. But yes, Guix represents
minimalism to me even though we still need to work to make it really
suitable for embedded systems (like routers).

Pj.

  reply	other threads:[~2019-11-24  8:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-23 14:21 FOSDEM is coming! Ludovic Courtès
2019-11-23 16:12 ` Mathieu Othacehe
2019-11-24  7:59   ` Pjotr Prins [this message]
2019-11-26 10:10   ` Ludovic Courtès
2019-11-26 10:27     ` Mathieu Othacehe
2019-11-23 17:29 ` Efraim Flashner
2019-11-24  8:04   ` Pjotr Prins
2019-11-26 10:08   ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20191124075906.cixrxhrst35wzba2@thebird.nl \
    --to=pjotr.public12@thebird.nl \
    --cc=guix-devel@gnu.org \
    --cc=m.othacehe@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 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.