From: "Bradley M. Kuhn" <bkuhn@sfconservancy.org>
To: gcc@gcc.gnu.org
Cc: Eric Gallager <egall@gwmail.gwu.edu>,
Jeremy Bennett <jeremy.bennett@embecosm.com>,
Jan Hubicka <honza.hubicka@gmail.com>
Subject: 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)
Date: Fri, 29 Mar 2024 10:01:03 -0700 [thread overview]
Message-ID: <ZgbzzwYBPGFtq/qJ@ebb.org> (raw)
In-Reply-To: <0793e75d2c7085853edfb68e3d829868f70aea46.camel@klomp.org>
Eric Gallager wrote:
>>> I would greatly appreciate a US option [in addition to GNU Cauldron in
>>> Europe], and having it in Portland would be especially convenient for me.
On Wed, 2024-03-06 at 12:47 -0800, Bradley M. Kuhn via Gcc wrote:
> > To have a track at FOSSY, it is somewhat similar to FOSDEM in that regard
> > — so it can be done grassroots. The volunteer help SFC needs is minimal:
> > we'd need some accomplished folks in the GNU toolchain projects to step
> > forward to do review and selection of talks, and at least one person who
> > is coming in-person that will coordinate with the speakers in the track
> > for the day.
Mark Wielaard replied:
> This has been confirmed now:
> https://sfconservancy.org/news/2024/mar/28/fossy-2024/
> FOSSY is back in Portland - August 1-4th at Portland State University
> To propose a GNU toolchain community track go here:
> https://sfconservancy.org/fossy/community-tracks/
While I'm not directly involved much with FOSSY organization, my colleagues
at SFC are. I did talk with them about the idea of having a GNU toolchain
track at FOSSY, and we'd very much welcome it.
If anyone with the sufficient expertise to do talk review for such a track
would like to do it, but needs a little help (or has concerns about the time
commitment, or anything like that), please feel free to write to me
privately.
--
Bradley M. Kuhn - he/them
Policy Fellow & Hacker-in-Residence at Software Freedom Conservancy
========================================================================
Become a Conservancy Sustainer today: https://sfconservancy.org/sustainer
prev parent reply other threads:[~2024-03-29 17:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-04 15:10 GNU Tools Cauldron 2024 Jeremy Bennett
2024-03-06 3:57 ` Bradley M. Kuhn
2024-03-06 19:02 ` Eric Gallager
2024-03-06 20:47 ` Bradley M. Kuhn
2024-03-29 14:44 ` Mark Wielaard
2024-03-29 17:01 ` Bradley M. Kuhn [this message]
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=ZgbzzwYBPGFtq/qJ@ebb.org \
--to=bkuhn@sfconservancy.org \
--cc=egall@gwmail.gwu.edu \
--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).