all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Alex Sassmannshausen <alex.sassmannshausen@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: FOSDEM 2016
Date: Wed, 26 Aug 2015 14:12:53 +0200	[thread overview]
Message-ID: <877foi8cze.fsf@gmail.com> (raw)
In-Reply-To: <87pp2bdoxy.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 825 bytes --]

Hello,

I think a guile track proposal for FOSDEM is a great idea.  The last 2
years I've put forward FOSDEM proposals, the first for a GNU track, the
second for a Guix track.

The first was declined as the FOSDEM organisers were worried that the
track might not be technical enough.  The second proposal was declined
as a result of us proposing a track on a distribution, when there was a
general distributions track.

I think making the track a Guile track seems like a great approach to
avoid these issues.

I've attached last year's proposal — maybe it would help in formulating
this year's proposal.  I'm also happy to contribute to the discussion in
terms of practical questions that I may be able to answer as a result of
my applications the previous years.  By and large the process is quite
painless.

HTH!

Alex


[-- Attachment #2: Room proposal --]
[-- Type: text/plain, Size: 3005 bytes --]

* Devroom name.

  GNU Guix — growing the GNU distribution.

* Devroom description:

  GNU Guix is the foundation for the reference GNU distribution.

  Guix is a functional package manager based on Nix, written in GNU
  Guile. Development started just 2 years ago, and it has now reached
  a critical juncture: hitherto it was a symbiotic package manager
  installed alongside other package managers within distributions. Now
  it's also becoming a distribution in its own right.

  Goals of the distro (the niche in the "distro market"):
  - transparent, transactional, per-user package-management
  - declarative system configuration;
  - extensibility from the ground up (where possible core distro
    functionality is provided through Guile programs, a language
    specifically designed to be hackable and extensible — for example,
    at present the init system is provided by dmd, which is written in
    Guile);
  - secure: builds are performed in isolated environments to
    facilitate reproducibility, and can be checked independently by
    end-users;
  - blurring of lines between developers, distribution maintainers and
    end-users:
    + high level DSL for describing packages makes packaging easy to
      understand for developers and end-users alike, reducing barriers
      to distro maintenance contribution;
    + support for concurrent system configurations within different
      'profiles' allows for on-the-fly system reconfigurations to help
      bug-tracking and development.

  The devroom will provide the following content:

  - high level overview of & tutorial on the distribution;
  - hacking sessions for packaging software, enhancing the
    distribution (installer, package-management tools, user
    interfaces);
  - discussions & presentations of specific components:
    + Secure networking through gnunet:
      * integration of the GNU Name Service (peer-to-peer, secure DNS
        replacement);
      * choice of defaults that help users remain in control (Linux
        TCP stealth patch, GNUnet and Tor services, etc.)
    + Extending the init system: use Guile (DMD) or established systems?
    + Providing kernel hotswapping: supporting hurd development by
      providing it as an alternative to linux-libre.
    + Extensibility from the ground up: grafting Guile into the heart
      of a distro (e.g. GNU Posh, Guix, DMD).
  - open discussions on the further development of Guix and the
    distro.

  The purpose of the room is to technically progress the distribution
  through:
  - demonstrations of its viability;
  - debates around its technical composition;
  - a space where hackers can contribute concrete chunks of code.

* Related URLs

  - GNU Project: http://www.gnu.org
  - GNU Guix: http://www.gnu.org/software/guix

* Devroom organisers

  - Alex Sassmannshausen (alex.sassmannshausen@gmail.com):
    co-ordinator and occasional contributor to Guix.
  - Ludovic Courtès (ludo@gnu.org): maintainer and core developer of
    Guix.

[-- Attachment #3: Type: text/plain, Size: 788 bytes --]


Ludovic Courtès writes:

> Hello!
>
> (Resent with Alex Cc’d this time.)
>
> Pjotr Prins <pjotr.public12@thebird.nl> skribis:
>
>> We should propose a Guile + Guix developers track for FOSDEM. They usually have
>> Ruby/Perl/Python dev tracks, so Guile will fit right in. I am sure we can
>> generate enough interesting talks on aspects of Guix packaging, for one.
>>
>> Deadline for dev room proposals is half September.
>
> That’s a good idea.  In the past, Alex Sassmannshausen (Cc’d) took care
> of submitting dev room proposals for GNU as a whole.  Alex: What would
> you think of making a Guix or Guile+Guix (instead of GNU) dev room?
> Would you like to give a hand?
>
> If we fail to get a dev room, we can surely submit one or two talk
> proposals.
>
> Thanks,
> Ludo’.

  reply	other threads:[~2015-08-26 12:13 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-18 10:32 FOSDEM 2016 Pjotr Prins
2015-08-18 10:45 ` Amirouche Boubekki
2015-08-18 11:06 ` Claes Wallin (韋嘉誠)
2015-08-18 13:11 ` Thompson, David
2015-08-18 15:11   ` Pjotr Prins
2015-08-23 17:36 ` Ludovic Courtès
2015-08-24  7:29   ` Pjotr Prins
2015-08-24 17:42   ` Tomáš Čech
2015-08-25 21:43   ` Ludovic Courtès
2015-08-26 12:12     ` Alex Sassmannshausen [this message]
2015-08-28  9:15       ` Ludovic Courtès
2015-08-28 17:17         ` Ricardo Wurmus
2015-08-29 10:35           ` Ludovic Courtès
2015-08-30  7:11         ` Pjotr Prins
2015-08-30 11:47           ` Ludovic Courtès
2015-09-01  6:28             ` Pjotr Prins
2015-09-01  7:16               ` Alex Sassmannshausen
2015-08-24 15:59 ` Christopher Allan Webber
2015-08-24 17:28 ` Ricardo Wurmus

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=877foi8cze.fsf@gmail.com \
    --to=alex.sassmannshausen@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=ludo@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.