unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Vagrant Cascadian <vagrant@debian.org>
To: Timothy Sample <samplet@ngyro.com>, guix-devel@gnu.org
Subject: Re: Guix meetup at FOSSY?
Date: Thu, 29 Jun 2023 11:02:24 -0700	[thread overview]
Message-ID: <87y1k2xi33.fsf@wireframe> (raw)
In-Reply-To: <87sfaans5k.fsf@ngyro.com>

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

On 2023-06-29, Timothy Sample wrote:
> The first FOSSY (Free and Open Source Yearly) conference is coming up in
> two weeks!  It’s being hosted in Portland, OR by the Software Freedom
> Conservancy.
>
> I was looking over the schedule and I spotted a few familiar names from
> the Guix community.  Why don’t we plan a little Guix meetup?  It could
> be as simple as a Guix luncheon or we could try to find time for some
> sort of hackathon (though it’s getting to be short notice for that...).
> Let’s take this opportunity to bring some Guixers together in North
> America for a change!
>
> Who’s in?

Sounds great!

Will present a talk Sunday in which I will definitely be mentioning the
Guix bootstrapping work!

  Breaking the Chains of Trusting Trust: Reproducible Builds and More!
  https://2023.fossy.us/schedule/presentation/118/

live well,
  vagrant

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]

  reply	other threads:[~2023-06-29 18:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-29 16:35 Guix meetup at FOSSY? Timothy Sample
2023-06-29 18:02 ` Vagrant Cascadian [this message]
2023-07-04 15:05   ` Timothy Sample
2023-07-04 17:54     ` Vagrant Cascadian
2023-07-06 18:38       ` Timothy Sample
2023-07-07 16:31         ` Vagrant Cascadian
2023-07-11 18:19           ` Timothy Sample
2023-07-11 21:49             ` Vagrant Cascadian

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=87y1k2xi33.fsf@wireframe \
    --to=vagrant@debian.org \
    --cc=guix-devel@gnu.org \
    --cc=samplet@ngyro.com \
    /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).