From: ori@eigenstate.org
To: 9front@9front.org
Subject: [9front] hackathon the next: locations needed
Date: Tue, 06 Feb 2024 15:09:36 -0500 [thread overview]
Message-ID: <1FACB24E3BA7606B18E49DB92C0CC5B4@eigenstate.org> (raw)
It's time to start planning for the next
hackathon. Anyone able to help us get a
good space?
Hacking typically happens at all hours,
so either good shared accomodations with
a large common space, or a room with 24/7
access is ideal.
If possible there would be someone local
who could accept shipments for network gear,
knows the neighborhood, etc.
The last ones we held were in early Aug;
I think doing it at that time again works.
Once I get a few candidate locations and
times, we'll take a look and pick one that's
fun, accessible, and affordable.
next reply other threads:[~2024-02-06 20:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-06 20:09 ori [this message]
2024-02-07 8:24 ` umbraticus
2024-02-09 23:42 ` thedaemon
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=1FACB24E3BA7606B18E49DB92C0CC5B4@eigenstate.org \
--to=ori@eigenstate.org \
--cc=9front@9front.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 NNTP newsgroup(s).