unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: "jgart" <jgart@dismail.de>
To: guile-devel@gnu.org
Subject: Guile Developer Meetup at Guix days 2023
Date: Wed, 28 Dec 2022 00:42:39 +0000	[thread overview]
Message-ID: <08c6e15ac2fe20e27ff10d1c64833d03@dismail.de> (raw)

Hi Guilers,

I had mentioned on IRC a few weeks ago regarding meeting up to discuss ways that we can improve the Guile debugger, be it through better documentation tutorials, patches to the C or Scheme code, etc. People seemed to be interested in meeting up.

Are people interested in doing our first meetup online for that in February?

Thursday, February 2nd or Friday, February 3rd 2023, the two days before FOSDEM

Coffee at 9:30AM, and starting at 10AM (UTC+1). 

I was thinking we can have a hybrid meetup (in-person/online) at Guix Days. I'll be there in Brussels.

Are developers who are familiar with the Guile debugger parts interested in having a round big blue button table informal discussion to talk about current development, tickets, issues, etc. regarding the Guile debugger and how people can become involved?

Andy, do you or anyone else who might be intimately familiar with the guile debugger code or has committed to it before happen to be available during Guix Days to give us a quick informal tour of that part of the codebase over Big Blue Button*?

Here's more info on Guix Days:

https://libreplanet.org/wiki/Group:Guix/FOSDEM2023

There's a matrix room for Guix Days here if you'd like to come chat there about the event:

https://matrix.to/#/#guix-days:matrix.org

all best,

jgart

https://whereis.みんな/

* https://meet.nixnet.services/



             reply	other threads:[~2022-12-28  0:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-28  0:42 jgart [this message]
2022-12-28 15:34 ` Guile Developer Meetup at Guix days 2023 Matt Wette
2022-12-30 15:19 ` Simon Tournier
2023-01-02 16:54 ` jgart

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/guile/

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

  git send-email \
    --in-reply-to=08c6e15ac2fe20e27ff10d1c64833d03@dismail.de \
    --to=jgart@dismail.de \
    --cc=guile-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.
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).