From: Lars Kurth <lars.kurth@xen.org>
To: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Reminder: Xen Dev Meeting before XenSummit
Date: Mon, 13 Aug 2012 13:25:46 +0100 [thread overview]
Message-ID: <5028F24A.7090307@xen.org> (raw)
Hi,
just a quick reminder that we do have the Xen Dev Meeting the Sunday
before XenSummit. The event is invite only, but you can request an
invite. For more information see here
http://wiki.xen.org/wiki/Xen_Maintainer,_Committer_and_Developer_Meeting/XenSummit_NA_2012
We are almost full, but can accomodate another 5 or so maybe 10 maximum.
Regarding agenda: I originally was going to propose an agenda, but I got
feedback from attendees that this is not the right approach. What I will
be doing today is to go through the proposed topics and create a survey
for attendees. Each attendee can choose 10 topics in the survey (about
as much as we can handle in the time we have). Based on the results, I
will create an ordered list of topics and we will work through these in
order.
Best Regards
Lars
reply other threads:[~2012-08-13 12:25 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=5028F24A.7090307@xen.org \
--to=lars.kurth@xen.org \
--cc=xen-devel@lists.xen.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).