unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Fabio Natali <me@fabionatali.com>
To: emacs-devel@gnu.org
Subject: Lisp assembly at 38c3
Date: Fri, 06 Dec 2024 18:50:23 +0000	[thread overview]
Message-ID: <87a5d88x3k.fsf@fabionatali.com> (raw)

Dear All,

tl;dr: This is to let you know that I've registered a Lisp assembly at
38c3. I'm currently reaching out to various Lisp-related communities to
see if anyone is also attending 38c3 and might be interested in joining
the assembly.

More context:

38c3 is the 38th edition of the Chaos Communication Congress or CCC[0],
the annual hacker conference happening in Hamburg, Germany from 27th to
30th December. Roughly speaking, a Congress assembly is a space that's
made available for a self-organised group, to collaborate, organise
workshops, talks, etc. around a specific project or area of interest.

The 38c3 Lisp assembly[1] is meant as a meeting point for Lisp
aficionados of all levels as well as for the passer-by who's curious and
wants to know more. I hope this will attract friends from a variety of
Lisp dialects (e.g. Chicken, Clojure, Common Lisp, Emacs Lisp, Fennel,
Guile, Racket) and Lisp-based projects (e.g. Emacs and Guix).

I'd like to prepare a small number of activities, such as:

- micro talks,
- pair-programming sessions,
- bug-reporting/bug-fixing/patch-review sessions.

No code-of-conduct has been chosen yet but there'll be one (which can be
chosen collaboratively if you like, possibly taken from or inspired by
one particular Lisp project's CoC).

As I'm only familiar with a small fraction of Lisp languages and
projects, I'd love to hear from any fellow Lisp-minded hacker who's also
planning to be at 38c3, to join forces and plan things together.

If you're interested or have any question, you can:

- write to ~fabionatali/lisp-at-38c3@lists.sr.ht (public list[2]), or
- reply to this email (make sure to CC me please), or
- reach out on the Fediverse at @fnat@social.coop, or
- reach out on IRC at fnat at libera.chat.

Have a lovely day, cheers,

Fabio.


PS: I'm planning to send this out to the following Lisp mailing lists:

- chicken-hackers@nongnu.org
- clojure@googlegroups.com
- ~technomancy/fennel@lists.sr.ht
- guile-devel@gnu.org
- dev@racket-lang.org
- emacs-devel@gnu.org
- guix-devel@gnu.org

Apologies if you end up receiving multiple copies through different
channels. Let me know if there's any other relevant community that I
should reach out to.


- [0]: https://en.wikipedia.org/wiki/Chaos_Communication_Congress
- [1]: https://events.ccc.de/congress/2024/hub/en/assembly/lisp/
- [2]: https://lists.sr.ht/~fabionatali/lisp-at-38c3/


-- 
Fabio Natali
https://fabionatali.com



             reply	other threads:[~2024-12-06 18:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-06 18:50 Fabio Natali [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-12-06 22:23 Lisp assembly at 38c3 Christopher Howard
2024-12-07 12:02 ` Fabio Natali

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://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=87a5d88x3k.fsf@fabionatali.com \
    --to=me@fabionatali.com \
    --cc=emacs-devel@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/emacs.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).