From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: "Martin K. Petersen" <martin.petersen@oracle.com>,
Jason Gunthorpe <jgg@ziepe.ca>
Cc: Matthew Wilcox <willy@infradead.org>,
Josef Bacik <josef@toxicpanda.com>,
lsf-pc <lsf-pc@lists.linuxfoundation.org>,
Linux FS Devel <linux-fsdevel@vger.kernel.org>,
linux-mm@kvack.org, linux-xfs@vger.kernel.org,
Btrfs BTRFS <linux-btrfs@vger.kernel.org>,
bpf@vger.kernel.org, linux-ext4@vger.kernel.org,
linux-block@vger.kernel.org
Subject: Re: [LSFMMBPF TOPIC] Killing LSFMMBPF
Date: Fri, 06 Mar 2020 11:15:51 -0800 [thread overview]
Message-ID: <1583522151.3653.81.camel@HansenPartnership.com> (raw)
In-Reply-To: <yq1eeu51ev0.fsf@oracle.com>
On Fri, 2020-03-06 at 14:07 -0500, Martin K. Petersen wrote:
> Jason,
>
> > Yes, I can confirm this from another smaller hotel-style conference
> > I've been involved organizing on occasion. $600-$800 is required to
> > break even without major sponsorship $$ for the ~100 people mark,
> > and that is without the usual food and venue perks we see at
> > plumbers/lsfmm.
>
> Yep. Our actual per-person cost for LSF/MM/BPF is in excess of $1K.
> That limits who we can invite. Personally I absolutely hate the
> invitation aspect and process. But we are very constrained wrt. how
> many we can actually accommodate by the amount of funding we get.
> Things appear to be better this year, but sponsor mergers and
> acquisitions have been a major concern the past few years.
To be a bit mercenary (hey, it's my job, I'm Plumbers treasurer this
year) our sponsors are mostly the same companies. If we combine LSF/MM
and Plumbers, I can't see too many of them stepping up to sponsor us
twice, so we'll have a net loss of sponsor funding for the combined
event as well. This is likely another argument for doing two
separately sponsored events.
James
next prev parent reply other threads:[~2020-03-06 19:15 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-06 14:35 [LSFMMBPF TOPIC] Killing LSFMMBPF Josef Bacik
2020-03-06 15:29 ` Jason Gunthorpe
2020-03-06 15:30 ` [Lsf-pc] " Amir Goldstein
2020-03-06 15:55 ` Josef Bacik
2020-03-06 15:56 ` Theodore Y. Ts'o
2020-03-06 16:08 ` Josef Bacik
2020-03-06 19:48 ` Theodore Y. Ts'o
2020-03-06 18:30 ` Rik van Riel
2020-03-07 18:54 ` [LSFMMBPF TOPIC] LSFMMBPF 2020 COVID-19 status update Luis Chamberlain
2020-03-07 19:00 ` Josef Bacik
2020-03-07 19:12 ` James Bottomley
2020-03-06 16:04 ` [LSFMMBPF TOPIC] Killing LSFMMBPF Nikolay Borisov
2020-03-06 16:05 ` Matthew Wilcox
2020-03-06 17:04 ` Al Viro
2020-03-06 17:37 ` James Bottomley
2020-03-06 18:06 ` Jason Gunthorpe
2020-03-06 19:07 ` Martin K. Petersen
2020-03-06 19:15 ` James Bottomley [this message]
2020-03-06 19:20 ` Martin K. Petersen
2020-03-06 18:23 ` Matthew Wilcox
2020-03-06 19:25 ` James Bottomley
2020-03-06 16:15 ` James Bottomley
2020-03-06 16:28 ` Christian Brauner
2020-03-06 16:31 ` Josef Bacik
2020-03-06 19:27 ` [LSFMMBPF TOPIC] long live LFSMMBPF Chris Mason
2020-03-06 19:41 ` James Bottomley
2020-03-06 19:56 ` Chris Mason
2020-03-06 20:25 ` Theodore Y. Ts'o
2020-03-07 3:14 ` [LSFMMBPF TOPIC] Killing LSFMMBPF Steve French
2020-03-10 13:13 ` Michal Hocko
2020-03-10 13:40 ` Josef Bacik
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=1583522151.3653.81.camel@HansenPartnership.com \
--to=james.bottomley@hansenpartnership.com \
--cc=bpf@vger.kernel.org \
--cc=jgg@ziepe.ca \
--cc=josef@toxicpanda.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-xfs@vger.kernel.org \
--cc=lsf-pc@lists.linuxfoundation.org \
--cc=martin.petersen@oracle.com \
--cc=willy@infradead.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).