From: Eric Gallager <egall@gwmail.gwu.edu>
To: "Bradley M. Kuhn" <bkuhn@sfconservancy.org>
Cc: Jeremy Bennett <jeremy.bennett@embecosm.com>,
gcc@gcc.gnu.org, David Edelsohn <dje.gcc@gmail.com>,
"Carlos O'Donell" <carlos@redhat.com>,
Jan Hubicka <honza.hubicka@gmail.com>
Subject: Re: GNU Tools Cauldron 2024
Date: Wed, 6 Mar 2024 14:02:35 -0500 [thread overview]
Message-ID: <CAMfHzOvtiRMuYfx4_aDEXMVvvb--cH6rbpvZi58P12gAhZwCVw@mail.gmail.com> (raw)
In-Reply-To: <Zefpm+iPwvHBnGBI@ebb.org>
On Tue, Mar 5, 2024 at 11:01 PM Bradley M. Kuhn via Gcc <gcc@gcc.gnu.org> wrote:
>
> Jeremy, David, Carlos, and the GCC Community,
>
> Jeremy Bennett wrote yesterday:
> > We are starting to put together the plans for this year's Cauldron. We
> > have a suggested date of 13-15 September, the weekend before LPC.
>
> > We have not finalized a host for the meeting. If you wish to host, please
> > let me, David Edelsohn, Carlos O'Donnell or Jan Hubicka know ASAP.
>
> During the open session at the of Cauldron in 2023, I offered that Software
> Freedom Conservancy could offer hosting for a “Cauldron USA” — in conjunction
> with the annual FOSSY (Free and Open Source Software Yearly) conference that
> we organize and host in each year in Portland, Oregon, USA.
>
> There seemed some interest to that. We're just a few days away from
> finalizing the date and venue for FOSSY. It's similar to FOSDEM in
> that we organize and pay for the venue, handle on-site logistics, and
> provide the usual logistics — and then volunteers need to handle review
> of talk proposals for the track and be on site to introduce speakers, etc.
>
> This would be different dates (it's likely to be in mid-to-late northern
> hemisphere summer), and in the USA, so it would complement the usual
> Cauldron.
>
> Let me know if any of you are interested in this, and I can put you in touch
> with the staff at SFC who orgainze FOSSY.
>
> Let me know!
Hi, I would greatly appreciate a US option, and having it in Portland
would be especially convenient for me, as then I could stay with
family, so I would like to express my interest in it and would hope
that such an option can go forwards
> --
> Bradley M. Kuhn - he/them
> Policy Fellow & Hacker-in-Residence at Software Freedom Conservancy
> ========================================================================
> Become a Conservancy Sustainer today: https://sfconservancy.org/sustainer
next prev parent reply other threads:[~2024-03-06 19:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-04 15:10 Jeremy Bennett
2024-03-06 3:57 ` Bradley M. Kuhn
2024-03-06 19:02 ` Eric Gallager [this message]
2024-03-06 20:47 ` Bradley M. Kuhn
2024-03-29 14:44 ` Mark Wielaard
2024-03-29 17:01 ` Submission Deadline 2024-04-18, GNU toolchain track at FOSSY in Portland, OR, USA (Conference date: 2024-08-01 to 2024-08-04) (was Re: GNU Tools Cauldron 2024) Bradley M. Kuhn
2024-05-09 15:48 GNU Tools Cauldron 2024 Jan Hubicka
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=CAMfHzOvtiRMuYfx4_aDEXMVvvb--cH6rbpvZi58P12gAhZwCVw@mail.gmail.com \
--to=egall@gwmail.gwu.edu \
--cc=bkuhn@sfconservancy.org \
--cc=carlos@redhat.com \
--cc=dje.gcc@gmail.com \
--cc=gcc@gcc.gnu.org \
--cc=honza.hubicka@gmail.com \
--cc=jeremy.bennett@embecosm.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.
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).