From: Jes Sorensen <Jes.Sorensen@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: "Chris Wright" <chrisw@redhat.com>,
"wolfgang mueller" <wolfgang@acm.org>,
"Frédéric Pétrot" <Frederic.Petrot@imag.fr>,
"Alexander Graf" <agraf@suse.de>,
"QEMU-devel Developers" <qemu-devel@nongnu.org>,
"Andreas Färber" <andreas.faerber@web.de>
Subject: Re: [Qemu-devel] CFP: 1st International QEMU Users Forum
Date: Fri, 26 Nov 2010 15:15:04 +0100 [thread overview]
Message-ID: <4CEFC0E8.5060306@redhat.com> (raw)
In-Reply-To: <4CEFC085.9080603@codemonkey.ws>
On 11/26/10 15:13, Anthony Liguori wrote:
> On 11/26/2010 07:39 AM, Alexander Graf wrote:
>>
>> I can certainly get in touch with the organizers, but I can't answer
>> the latter question. There are usually at least ~10-20 kernel
>> developers around and it's easy to get most of the German qemu people
>> there too I assume (which is quite a significant number, though mostly
>> kvm focused).
>>
>
> An alternative (or maybe just addition) would be to organize a
> virtualization conference next year instead of just doing another KVM
> Forum. The idea would be to make it 3 days, have dedicated tracks for
> management (libvirt/Open Stack?), QEMU, and KVM and Xen.
>
> I think as an overall community, we're large enough that we could
> support a pretty sizable conference and I think everyone would benefit
> from being more exposed to other aspects of the stack.
I would be all in favor of this! Do you want to attach it to another
conference or totally standalone?
Cheers,
Jes
next prev parent reply other threads:[~2010-11-26 14:15 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-19 13:42 [Qemu-devel] CFP: 1st International QEMU Users Forum Wolfgang Mueller
2010-11-23 11:25 ` Alexander Graf
2010-11-25 10:30 ` wolfgang mueller
2010-11-25 11:03 ` Alexander Graf
2010-11-25 14:54 ` wolfgang mueller
2010-11-25 23:42 ` Alexander Graf
2010-11-26 13:54 ` Alexander Graf
2010-11-26 14:33 ` Peter Maydell
2010-11-26 15:18 ` Alexander Graf
2010-11-26 16:34 ` wolfgang mueller
2010-11-27 19:00 ` Peter Maydell
2010-11-27 22:26 ` Alexander Graf
2010-11-28 0:09 ` Nathan Froyd
2010-11-28 8:20 ` Frédéric Pétrot
2010-11-28 11:00 ` Alexander Graf
2010-11-29 0:06 ` Nathan Froyd
2010-11-29 6:43 ` Frédéric Pétrot
2010-11-29 13:58 ` Alexander Graf
2010-11-29 14:08 ` Peter Maydell
2010-11-29 15:27 ` Nathan Froyd
2010-11-28 10:55 ` Alexander Graf
2010-11-25 22:53 ` Andreas Färber
2010-11-25 23:17 ` Alexander Graf
2010-11-25 23:48 ` Alexander Graf
2010-11-26 7:56 ` Jes Sorensen
2010-11-26 11:53 ` Alexander Graf
2010-11-26 12:29 ` Jes Sorensen
2010-11-26 13:39 ` Alexander Graf
2010-11-26 14:13 ` Anthony Liguori
2010-11-26 14:15 ` Jes Sorensen [this message]
2010-11-26 14:21 ` Anthony Liguori
2010-11-26 15:10 ` Peter Maydell
2010-11-26 15:19 ` Alexander Graf
2010-11-29 9:53 ` Jes Sorensen
2010-11-26 15:15 ` Alexander Graf
2010-11-26 16:03 ` Anthony Liguori
2010-11-29 7:44 ` Jes Sorensen
2010-12-01 17:57 ` Jes Sorensen
2010-11-29 10:13 ` Stefano Stabellini
2010-11-29 11:30 ` [Qemu-devel] " Paolo Bonzini
[not found] <20101125233507.0D49927D48@zimbra14-e2.priv.proxad.net>
2010-11-26 0:05 ` [Qemu-devel] " François Revol
[not found] <20101125235615.157DC28C0F@zimbra14-e2.priv.proxad.net>
2010-11-26 0:26 ` François Revol
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=4CEFC0E8.5060306@redhat.com \
--to=jes.sorensen@redhat.com \
--cc=Frederic.Petrot@imag.fr \
--cc=agraf@suse.de \
--cc=andreas.faerber@web.de \
--cc=anthony@codemonkey.ws \
--cc=chrisw@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=wolfgang@acm.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).