From: Eric Sandeen <sandeen@redhat.com>
To: "Ted Ts'o" <tytso@mit.edu>
Cc: Ric Wheeler <ricwheeler@gmail.com>,
ext4 development <linux-ext4@vger.kernel.org>
Subject: Re: Ext4 developer's workshop website is now up
Date: Tue, 14 Feb 2012 15:14:21 -0800 [thread overview]
Message-ID: <4F3AEACD.9040507@redhat.com> (raw)
In-Reply-To: <20120202153052.GA4308@thunk.org>
On 2/2/12 7:30 AM, Ted Ts'o wrote:
> On Wed, Feb 01, 2012 at 03:44:03PM -0500, Ric Wheeler wrote:
>>
>> One question, any chance to pull it back closer in to LSF or have it
>> on one of the collab summit days? Having it take place on the Friday
>> adds several hotel nights I suspect for non-locals (and significant
>> cost)....
>
> Well, keep in mind that LSF is starting Sunday already, so it means
> for people who are from out of town, the weekend[1] is already shot;
> there were issues with hotel space, from what I was told when I asked
> Angela, which is why it's Sunday and Monday as opposed to Monday and
> Tuesday.
>
> [1] Which for me means I miss participating in my church's Palm Sunday
> celebration, and LSF and the Collab Summit overlaps with Holy Week.
> On the other hand I believe it was last year that Collab Summit
> overlaps with Passover, so I guess it's equal-opportunity stomping on
> religious holdays. :-/
>
> So it's really only two extra hotel nights; if we met on Saturday
> instead of Friday, it gets hard for people who are local to the bay
> area, as well as people who might be conferencing continuously from
> the Ext4 Workshop, through LSF, through to the Collab Summit. And
> meeting during the LSF gets hard from a scheduling point of view,
> especially since XFS is already meeting (all day?) during Collab
> Summit already.
>
> Also, there are some relatively inexpensive hotels (under $100/day) in
> the South Bay, and if necessary I would be happy to organize some car
> pools so that people can get back and forth from their hotels to the
> Google Campus, and from Mountain View up to San Francisco on Saturday
> to save on ground transportation results.
Ted, I'm curious about how many (who?) have indicated that they'll attend
on Friday so far?
I had indicated that I'd like to attend; however, I don't have the travel
budget* to go 2 days earlier, I'm afraid. I probably won't even stay for all
of collab summit.
I thought it worked pretty well before when we just grabbed a room for
a couple hours... doing that on the first day of collab summit (avoiding
the xfs timeslot... whenever that is) would work a lot better for me.
Thanks,
-Eric
* or the spousal-tolerance budget, TBH
> Regards,
>
> - Ted
> --
> To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2012-02-14 23:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-01 4:46 Ext4 developer's workshop website is now up Theodore Ts'o
2012-02-01 20:44 ` Ric Wheeler
2012-02-02 15:30 ` Ted Ts'o
2012-02-14 23:14 ` Eric Sandeen [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=4F3AEACD.9040507@redhat.com \
--to=sandeen@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=ricwheeler@gmail.com \
--cc=tytso@mit.edu \
/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.