From: Theodore Tso <tytso@MIT.EDU>
To: Andreas Dilger <adilger@dilger.ca>
Cc: Theodore Tso <tytso@mit.edu>, linux-ext4@vger.kernel.org
Subject: Re: Better organizing ext4 development community
Date: Mon, 21 Nov 2011 18:48:11 -0500 [thread overview]
Message-ID: <3CE0AF24-2873-4A84-B311-1FD2ED5C64FD@mit.edu> (raw)
In-Reply-To: <DA5E3B75-913C-4F50-B3DF-DF28FFF36C89@dilger.ca>
On Nov 21, 2011, at 4:51 PM, Andreas Dilger wrote:
> At Whamcloud we have regularly scheduled concalls that cross a lot of
> timezones, and realistically the only time that allows people to join
> is early PT in the USA, end of day in Europe, and ~midnight in Asia.
What I've done (which has never been pleasant) is to alternate between 11am US/Eastern and 11pm US/Pacific. That distributes the pain a bit more equally, but yeah, it's not great.
> I'd be OK to attend such a meeting, but I agree with Amir that relatively
> few ext4 developers are invited to KS so it doesn't necessarily reduce the
> travel. In years past we would attend OLS, but that is (AFAIK) largely
> unattended by ext4 developers these days.
This is not the Kernel Summit, but LSF. And the LSF is held at the same week as the Collaboration Summit, which is a open event. Also, getting an invite to LSF really isn't that hard, if you plan ahead…
-- 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
next prev parent reply other threads:[~2011-11-22 2:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-21 15:58 Better organizing ext4 development community Theodore Ts'o
2011-11-21 20:08 ` Amir Goldstein
2011-11-21 21:51 ` Andreas Dilger
2011-11-21 23:48 ` Theodore Tso [this message]
2011-11-22 2:57 ` Tao Ma
2011-11-22 5:12 ` Dave Chinner
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=3CE0AF24-2873-4A84-B311-1FD2ED5C64FD@mit.edu \
--to=tytso@mit.edu \
--cc=adilger@dilger.ca \
--cc=linux-ext4@vger.kernel.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