From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Christian Brauner <brauner@kernel.org>,
linux-fsdevel@vger.kernel.org, linux-mm@kvack.org,
linux-block@vger.kernel.org, linux-ide@vger.kernel.org,
linux-scsi@vger.kernel.org, linux-nvme@lists.infradead.org,
bpf@vger.kernel.org, lwn@lwn.net
Cc: lsf-pc@lists.linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: LSF/MM/BPF: 2026: Call for Proposals
Date: Tue, 24 Feb 2026 08:37:31 -0500 [thread overview]
Message-ID: <72f731b8153106fd32ee991da10f847a3a8d768a.camel@HansenPartnership.com> (raw)
In-Reply-To: <20260224-sangen-aufatmen-06ba16719f33@brauner>
On Tue, 2026-02-24 at 10:53 +0100, Christian Brauner wrote:
> > Don't forget to pester^wask^wremind your respective organizations
> > to sponsor LSF/MM/BPF 2026! If it helps, you can tell them that
> > we're considering renaming it LSF/MM/BPF/AI.
>
> I have just looked at the sponsorship site for LSF/MM/BPF/AI again
> and we all really need to go out and go steal some of that AI funding
> money and funnel it into one of the conferences that really drives
> development of the operating system that drives the compute for all
> of this.
>
> Please go and remind your organizations to sponsor. They should know
> how to get in touch with the Linux Foundation. Just going by the
> sponsorship page we're missing a bunch of large organizations that we
> would appreciate if they decided to pitch in. :)
Just on this point, at least for Linux Plumbers Conference, we've found
that increasingly OSPOs (which usually hold the LF contacts) are
aligned with Marketing organizations and don't see as much value in
sponsoring pure engineering events (like LSF and LPC). We've thus
started getting our money from the Engineering organizations themselves
(where you are all better placed to wield influence). To convince your
engineering management chain (who may never have done this before) you
need to articulate the value (it's the place where Linux features
you're working on get presented, discussed and decided so a good
showing by your engineers can drastically shorten the time to
acceptance of something, or actually set direction better than a
mailing list discussion, which provides more roadmap certainty for VPs)
and provide the details, so the sponsor prospectus is here:
http://events.linuxfoundation.org/sponsor-lsfmm-bp-f26
You have to go high enough in your organization to find someone with an
actual budget, which can be a bit daunting, so if you need outside
help, the PC (lsf-pc@lists.linuxfoundation.org) will be able to help
articulate the value once you've found the person to convince.
If you manage to convince them to sponsor, the address to request a
contract and a PO is
sponsorships@linuxfoundation.org
Regards,
James
next prev parent reply other threads:[~2026-02-24 13:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-10 13:24 Christian Brauner
2026-01-19 14:26 ` Christian Brauner
2026-01-29 16:13 ` Christian Brauner
2026-02-16 14:25 ` Christian Brauner
2026-02-17 10:37 ` Haris Iqbal
2026-02-18 9:56 ` Christian Brauner
2026-02-24 9:53 ` Christian Brauner
2026-02-24 13:37 ` James Bottomley [this message]
2026-01-22 3:22 ` Al Viro
2026-01-23 10:16 ` Christian Brauner
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=72f731b8153106fd32ee991da10f847a3a8d768a.camel@HansenPartnership.com \
--to=james.bottomley@hansenpartnership.com \
--cc=bpf@vger.kernel.org \
--cc=brauner@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-nvme@lists.infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=lwn@lwn.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