From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Matthew Wilcox <willy@infradead.org>, Josef Bacik <josef@toxicpanda.com>
Cc: 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 09:37:59 -0800 [thread overview]
Message-ID: <1583516279.3653.71.camel@HansenPartnership.com> (raw)
In-Reply-To: <20200306160548.GB25710@bombadil.infradead.org>
On Fri, 2020-03-06 at 08:05 -0800, Matthew Wilcox wrote:
[...]
> 2. Charge attendees $300 for a 3-day conference. This seems to be
> the going rate (eg BSDCan, PGCon). This allows the conference to be
> self-funding without sponsors, and any sponsorship can go towards
> evening events, food, travel bursaries, etc.
Can I just inject a dose of reality here: The most costly thing is
Venue rental (which comes with a F&B minimum) and the continuous Tea
and Coffee. Last year for Plumbers, the venue cost us $37k and the
breaks $132k (including a lunch buffet, which was a requirement of the
venue rental). Given we had 500 attendees, that, alone is $340 per
head already. Now we could cut out the continuous tea and coffee ...
and the espresso machines you all raved about last year cost us about
$7 per shot. But it's not just this, it's also AV (microphones and
projectors) and recording, and fast internet access. That all came to
about $100k last year (or an extra $200 per head). So you can see,
running at the level Plumbers does you're already looking at $540 a
head, which, co-incidentally is close to our attendee fee. To get to
$300 per head, you lot will have to give up something in addition to
the espresso machines, what is it to be?
James
next prev parent reply other threads:[~2020-03-06 17:38 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 [this message]
2020-03-06 18:06 ` Jason Gunthorpe
2020-03-06 19:07 ` Martin K. Petersen
2020-03-06 19:15 ` James Bottomley
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=1583516279.3653.71.camel@HansenPartnership.com \
--to=james.bottomley@hansenpartnership.com \
--cc=bpf@vger.kernel.org \
--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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.