unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Timothy Sample <samplet@ngyro.com>
To: Vagrant Cascadian <vagrant@debian.org>
Cc: guix-devel@gnu.org
Subject: Re: Guix meetup at FOSSY?
Date: Tue, 11 Jul 2023 12:19:16 -0600	[thread overview]
Message-ID: <87351ujopn.fsf@ngyro.com> (raw)
In-Reply-To: <87bkgnheeg.fsf@wireframe> (Vagrant Cascadian's message of "Fri,  07 Jul 2023 09:31:19 -0700")

Hi,

Vagrant Cascadian <vagrant@debian.org> writes:

> My current best idea is the handful of food carts at pioneer courthouse
> square, with a few different carts that cater to various dietary needs
> and appetites... about 10-15 minutes on the MAX, with stops right at
> both endpoints!

This sounds great, but I just remembered that FOSSY provides lunch!
Maybe we should roll with that – it would make the timing a little
easier.  Also, I guess Friday lunch is a breakfast buffet, which sounds
pretty nice.  If that doesn’t work for you for whatever reason, I’m
happy to hit up some food trucks with a local.  :)  Otherwise, it’s
probably simpler just to set up a “Guix table” at the regular lunch.

As an aside, I don’t know how the lunches are going to work with the
health and safety measures or whether we could sit outside or whether a
buffet runs against a lot of the other precautions they’re taking....
For my part, I’m happy to take my queues from the organizers and I
respect that they have policies in place.  I don’t have a lot
expectations beyond that.


-- Tim


  reply	other threads:[~2023-07-11 18:20 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
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 [this message]
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=87351ujopn.fsf@ngyro.com \
    --to=samplet@ngyro.com \
    --cc=guix-devel@gnu.org \
    --cc=vagrant@debian.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/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).