From: Zach Brown <zach.brown@oracle.com>
To: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-scsi@vger.kernel.org, linux-nfs@vger.kernel.org
Subject: [CFP, 2 days left] 2009 Linux Storage and Filesystem Workshop
Date: Thu, 26 Feb 2009 11:44:14 -0800 [thread overview]
Message-ID: <49A6F10E.6010100@oracle.com> (raw)
This is a reminder that this weekend marks the deadline for accepting
proposals for the upcoming Linux storage and filesystem workshop. If
you want to come contribute to Linux storage then we want to hear from you!
The initial call for proposals follows.
----
Hello storage and filesystem friends,
This year's storage and filesystem workshop is being held in San
Francisco on April 6th and 7th. It's being held on the Monday and
Tuesday immediately preceding the Linux Foundation Collaboration
Summit, in the same hotel.
You can find all the details on the workshop's web site:
http://events.linuxfoundation.org/events/lsf-workshop
The workshop focuses on collaboration and discussion. There will be no
refereed papers and few presentations with slides will be accepted.
To attend we ask that you use the CFP interface on the web site to
submit a short proposal for a topic to discuss during the workshop. The
program committee will send invitations to the workshop based on these
proposals. The CFP and FAQ tabs on the web site describe this in more
detail.
For reference, there are writeups of previous workshops available
online:
http://lwn.net/Articles/226351/
http://www.usenix.org/publications/login/2008-06/openpdfs/lsf08reports.pdf
This year we'll be adding time to the schedule specifically for hands-on
development with your colleagues.
Please let me know if there are any questions about the workshop.
- z
reply other threads:[~2009-02-26 19:44 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=49A6F10E.6010100@oracle.com \
--to=zach.brown@oracle.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=linux-scsi@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;
as well as URLs for NNTP newsgroup(s).