unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Fabio Natali <me@fabionatali.com>
To: Andreas Enge <andreas@enge.fr>
Cc: Wilko Meyer <w@wmeyer.eu>,
	guix-devel@gnu.org,
	Tobias Alexandra Platen <guix@platen-software.de>
Subject: Re: Guix at 37C3 Chaos Communication Congress in late Dec?
Date: Thu, 18 Jan 2024 19:22:01 +0000	[thread overview]
Message-ID: <87zfx2zbty.fsf@fabionatali.com> (raw)
In-Reply-To: <Zakmv5AOM8GpDeoe@jurong>

On 2024-01-18, 14:25 +0100, Andreas Enge <andreas@enge.fr> wrote:
> thanks for your report!

Hey Andreas, thank you for getting back to me.

> This is quite amazing. One of the most depressing experiences at a CCC
> was when I went to a Lisp assembly, and there were at most a dozen
> people around a table, none of whom used the same Lisp dialect.

Haha, yes, I can see how this can very well be a risk!

The advantage of a Lisp assembly is the economy of scale. That'd combine
together various projects that were all massively under-represented at
37c3 - I'm primarily thinking of Guix, Guile, and Emacs as those are the
projects I care about, but there are others too.

If we build enough momentum, we should be able to have decently sized
assembly subgroups - in other words, we should be able to avoid the
twelve-people-that-speak-twelve-different-lisps scenario. :)

What's not ideal with a Lisp assembly is that Guix and Emacs are not
programming languages and, despite related to Lisp, their scope and
ideas transcend - or are partly orthogonal to - Lisp itself.

An other option would be to go the "FOSDEM way" and have a "declarative
and minimalist computing" assembly instead - what do you think?

I still have a slight preference for the Lisp assembly idea, but let's
see what the general feeling/preference is here in the ML. 38c3 won't be
happening any time soon anyway. :)

Thanks, best, F.


-- 
Fabio Natali
https://fabionatali.com


  parent reply	other threads:[~2024-01-18 19:22 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-11 11:26 Guix at 37C3 Chaos Communication Congress in late Dec? Fabio Natali
2023-12-11 20:15 ` Wilko Meyer
2023-12-11 20:32   ` Tobias Alexandra Platen
2023-12-11 21:02     ` Fabio Natali
2023-12-12 16:56       ` Fabio Natali
2023-12-12 17:19         ` Matt
2023-12-12 22:01           ` Fabio Natali
2023-12-13 12:34           ` Wilko Meyer
2023-12-13 15:01             ` Kristoffer Ström
2023-12-13 23:18               ` Sergio Pastor Pérez
2023-12-30 19:28         ` Wilko Meyer
2024-01-01 13:49           ` Fabio Natali
2024-01-02 20:26             ` Matt
2024-01-18 13:25             ` Andreas Enge
2024-01-18 18:12               ` Matt
2024-01-18 19:22               ` Fabio Natali [this message]
2024-01-19 16:08                 ` Andreas Enge

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=87zfx2zbty.fsf@fabionatali.com \
    --to=me@fabionatali.com \
    --cc=andreas@enge.fr \
    --cc=guix-devel@gnu.org \
    --cc=guix@platen-software.de \
    --cc=w@wmeyer.eu \
    /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).