all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Steve George <steve@futurile.net>
To: Tanguy LE CARROUR <tanguy@bioneland.org>,
	Pjotr Prins <pjotr.public12@thebird.nl>
Cc: help-guix@gnu.org, guix-devel@gnu.org
Subject: Re: Collecting Guix talks at FOSDEM
Date: Tue, 6 Feb 2024 10:17:42 +0000	[thread overview]
Message-ID: <303eb859-cfa9-4bf1-8636-38d88cfc889e@futurile.net> (raw)
In-Reply-To: <170720755500.31230.7066751393054209652@bioneland.org>

Hi Tanguy,

On 06/02/2024 08:19, Tanguy LE CARROUR wrote:
(...)
> Quoting Pjotr Prins (2024-02-06 08:39:25)
>> It would also be nice to write a BLOG about what was discussed at Guix
>> days
> 
> I have notes about what sessions took place during the Guix days.
> I was planning to send (tomorrow?) a patch for the Guix Foundation website
> to make it available, like "GNU Guix Days FOSDEM 2023" [1].
> 
> [1]: https://foundation.guix.info/events/index.html
> 
> I don’t know if it’s the right place to put notes about the content,
> though? 🤔

Ludo said they put them into this repo:

https://git.savannah.gnu.org/cgit/guix/maintenance.git/tree/doc/guix-days-2024

Do you have access to this? (I do not).

We can ask people on the channel / this list to put their notes - or 
integrate their notes into the existing ones there (as it's a shared 
endeavour).

Does that work?

Steve



  parent reply	other threads:[~2024-02-06 10:37 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-16 15:35 Collecting Guix talks at FOSDEM Steve George
2024-01-17 15:47 ` Simon Tournier
2024-01-17 21:16   ` Steve George
2024-01-18 10:51     ` Simon Tournier
2024-02-06  7:39 ` Pjotr Prins
2024-02-06  8:19   ` Tanguy LE CARROUR
2024-02-06  8:48     ` Pjotr Prins
2024-02-06  9:35       ` Tanguy LE CARROUR
2024-02-06 10:17     ` Steve George [this message]
2024-02-06 10:40       ` Tanguy LE CARROUR
2024-02-06 10:15   ` Steve George
2024-02-07 12:56   ` Steve George
2024-02-07 13:44     ` Christopher Baines

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=303eb859-cfa9-4bf1-8636-38d88cfc889e@futurile.net \
    --to=steve@futurile.net \
    --cc=guix-devel@gnu.org \
    --cc=help-guix@gnu.org \
    --cc=pjotr.public12@thebird.nl \
    --cc=tanguy@bioneland.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.