All of lore.kernel.org
 help / color / mirror / Atom feed
From: Don Slutz <dslutz@verizon.com>
To: lars.kurth@xen.org,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
	"xen-api@lists.xen.org" <xen-api@lists.xen.org>,
	"mirageos-devel@lists.xenproject.org"
	<mirageos-devel@lists.xenproject.org>,
	Russell Pavlicek <russell.pavlicek@citrix.com>
Subject: Re: [vote on timing] Xen Project Developer Meeting on August 20th AM in Chicago
Date: Thu, 05 Jun 2014 09:51:31 -0400	[thread overview]
Message-ID: <539075E3.9070007@terremark.com> (raw)
In-Reply-To: <53905933.2040000@xen.org>

On 06/05/14 07:49, Lars Kurth wrote:
> Hi everyone,
>
> I have more information related to the meeting.
> * I have space for a maximum of 40 people
> * I have the room from 8:30 - 18:30 - so we can be flexible on times
> * I have to use the same room for a board meeting. For the board meeting, I was thinking of a 8:00 - 9:00 or 9:00 - 10:00 (TBD, but the 9:00 slot is our normal board meeting time), starting the dev meeting 30 minutes after
> * LinuxCon is going on in parallel and the schedule has been published at http://events.linuxfoundation.org/events/linuxcon-north-america/program/schedule yesterday
> * Apart from Russell and me who both have talks from 12:15 - 13:05 no-one else has really an overlap.
>
> So what I am asking is for options: please vote
> +1 "09:30 - 13:00"
> +1 "10:30 - 14:00"
> +1 "13:00 - 16:30"
>

+1 10:30 - 14:00
    -Don Slutz

> Best Regards
> Lars
>
> On 02/06/2014 17:22, Lars Kurth wrote:
>> Hi all,
>>
>> I am pleased to announce that I secured space for a 1/2 day developer meeting the day after the Xen Project Developer Summit. As in the past, I suggest that the meeting lasts 3.5 - 4 hours. I suggest we start at 9:30 and run until 1pm, but could start a little bit later. If you have any preferences, let me know. As I will need to get a sense re numbers and order food and drinks, please reply to the thread for now, if you are planning to attend the meeting. Once I have more information, I will create a wiki page, and you can sign up on the wiki page.
>>
>> We will also have an Advisory Board meeting either before or after.
>>
>> Best Regards
>> Lars
>>
>>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel

  parent reply	other threads:[~2014-06-05 13:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <538CA4E3.40506@xen.org>
2014-06-05 11:49 ` [vote on timing] Xen Project Developer Meeting on August 20th AM in Chicago Lars Kurth
     [not found] ` <53905933.2040000@xen.org>
2014-06-05 13:51   ` Don Slutz [this message]
2014-06-05 14:08   ` Jan Beulich
     [not found]   ` <539096150200007800018468@mail.emea.novell.com>
2014-06-05 14:29     ` George Dunlap
2014-06-05 17:54   ` Jim Fehlig
2014-06-06  9:49     ` Lars Kurth
2014-06-06  9:59   ` Ian Campbell

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=539075E3.9070007@terremark.com \
    --to=dslutz@verizon.com \
    --cc=lars.kurth@xen.org \
    --cc=mirageos-devel@lists.xenproject.org \
    --cc=russell.pavlicek@citrix.com \
    --cc=xen-api@lists.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 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.