All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philip Balister <philip@balister.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: OEDEM scheduling
Date: Mon, 10 Aug 2009 07:27:48 -0400	[thread overview]
Message-ID: <4A800434.4050603@balister.org> (raw)
In-Reply-To: <1249899969.8248.95.camel@mill.internal.reciva.com>

[-- Attachment #1: Type: text/plain, Size: 1783 bytes --]

Phil Blundell wrote:
> The November date had 100% approval among those who responded to the
> doodle poll.  (October was second best; September was least favoured,
> and in any case the proposed September date is only four weeks away
> which is probably too close for a lot of folks.)  So, I would suggest
> that we just go ahead with the November date rather than introducing new
> alternatives at this stage. 
> 
> Either way, it'd be good to try to get the date nailed down within the
> next week or two so that everyone has adequate notice.  Obviously
> there's no statutory minimum notice period for this but you probably
> need at least 6-8 weeks to avoid a large number of diary clashes.

Agreed. Do we have a place to meet for those dates?

Philip


> 
> p.
> 
> On Sat, 2009-08-08 at 09:49 -0400, Philip Balister wrote:
>> From Mickey's earlier email:
>>
>> We have proposed three weekends. If anyone of you could open a doodle for
>> that, I'd be grateful:
>>
>> * 12/13 Sept.
>> * 17/18 Oct.
>> * 7/8 Nov.
>>
>> I don't like the September weekend :) (but airfare is still OK)
>>
>> For the other two weekends, airfare from .us is not great, but not 
>> ridiculous either.
>>
>> The October data is designed for people who may come from .us for ELC 
>> Europe (http://www.embeddedlinuxconference.com/elc_europe09/), so a 
>> location "near" Grenoble would be helpful. Anyone have any ideas on that?
>>
>> For November I would assume Berlin.
>>
>> Thoughts? Any other weekends that would work well for people?
> 
> 
> 
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
> 

[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3303 bytes --]

  reply	other threads:[~2009-08-10 11:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-08 13:49 OEDEM scheduling Philip Balister
2009-08-08 15:43 ` Marcin Juszkiewicz
2009-08-10 10:26 ` Phil Blundell
2009-08-10 11:27   ` Philip Balister [this message]
2009-08-18  1:43     ` Denys Dmytriyenko
2009-08-18 11:37       ` Phil Blundell
2009-08-20  7:14         ` Denys Dmytriyenko

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=4A800434.4050603@balister.org \
    --to=philip@balister.org \
    --cc=openembedded-devel@lists.openembedded.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.