From: Vagrant Cascadian <vagrant@debian.org>
To: Timothy Sample <samplet@ngyro.com>
Cc: guix-devel@gnu.org
Subject: Re: Guix meetup at FOSSY?
Date: Tue, 04 Jul 2023 10:54:10 -0700 [thread overview]
Message-ID: <87cz17y33x.fsf@wireframe> (raw)
In-Reply-To: <87ilazogx4.fsf@ngyro.com>
[-- Attachment #1: Type: text/plain, Size: 1100 bytes --]
On 2023-07-04, Timothy Sample wrote:
> Vagrant Cascadian <vagrant@debian.org> writes:
>> On 2023-06-29, Timothy Sample wrote:
>>> The first FOSSY (Free and Open Source [Software] Yearly) conference
>>> is coming up in two weeks! It’s being hosted in Portland, OR by the
>>> Software Freedom Conservancy.
>>>
>>> Why don’t we plan a little Guix meetup?
>>
>> Sounds great!
>
> Well, I was waiting to hear from more folks, but maybe not that many of
> us are going to FOSSY. Either way, I still think we should plan
> something.
>
> What about having a Guix lunch on Friday? I don’t really have strong
> feelings, but I thought I’d propose something concrete to get things
> going. I’ve never been to Portland, so I don’t have thoughts about
> where to meet. Do you know the city at all?
I have a couple decades of experience in Portland... :)
There are not a lot of things near the venue, but I will look for
options that are nearby and/or quick to get to by public transit ... and
ideally with outdoor seating or takeaway options.
live well,
vagrant
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2023-07-04 17:54 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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87cz17y33x.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 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.