From: "Darrick J. Wong" <djwong@kernel.org>
To: linux-fsdevel <linux-fsdevel@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-block@vger.kernel.org, linux-mm@kvack.org, x86@kernel.org,
netdev@vger.kernel.org
Cc: Zach Brown <zab@zabbo.net>, Matthew Wilcox <willy@infradead.org>
Subject: Re: Call for Proposals for fossy.us 2025
Date: Sun, 27 Apr 2025 21:07:28 -0700 [thread overview]
Message-ID: <20250428040728.GA1035866@frogsfrogsfrogs> (raw)
In-Reply-To: <20250422033344.GI25700@frogsfrogsfrogs>
On Mon, Apr 21, 2025 at 08:33:44PM -0700, Darrick J. Wong wrote:
> Hi folks,
>
> I'd like to (very belatedly) invite you all to the 2025 fossy.us
> conference that's being put on by Software Freedom Conservancy:
>
> https://2025.fossy.us/
>
> This is their third year of operation, and this time they've added a
> track for Linux kernel topics! Originally the track was going to be run
> by willy and I, but he had to drop out for various reasons. zab has
> stepped up to fill the gap.
>
> We're looking for people to propose sessions for the track. These can
> be informal presentations, discussion sections, or even a panel. In the
> past two editions, the attendees have ranged from technical folks from
> userspace projects to free software advocates who operate in the
> political and legal spheres. I think the most interesting topics would
> involve the kernel <-> userspace barrier, or technical deep-dives into
> how do the more complex parts of the kernel actually work, but I
> obviously have kernel-tinted glasses and welcome any strong proposal.
>
> Anyhow, the CfP deadline is April 28th, so please lob whatever proposals
...and has now been extended until May 5th. We've gotten a few
proposals and look forward to the rest! ;)
--D
> you have soon. The conference is in Portland, Oregon (USA) at the end
> of July, which ... I know is going to be problematic for a lot of
> people. This is a tough year for conferences (both planning and
> attending) so if you have questions, please feel free to ask them here
> or privately.
>
> --Darrick (and Zach)
>
prev parent reply other threads:[~2025-04-28 4:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-22 3:33 Darrick J. Wong
2025-04-28 4:07 ` Darrick J. Wong [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=20250428040728.GA1035866@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=netdev@vger.kernel.org \
--cc=willy@infradead.org \
--cc=x86@kernel.org \
--cc=zab@zabbo.net \
/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