From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: Expert track at yocto dev day?
Date: Wed, 08 Feb 2012 15:37:06 +0000 [thread overview]
Message-ID: <1328715426.3164.13.camel@ted> (raw)
In-Reply-To: <C13FAF30-26F8-4435-A2F8-DCD3F65876EA@dominion.thruhere.net>
On Tue, 2012-02-07 at 22:27 +0100, Koen Kooi wrote:
> Op 7 feb. 2012, om 22:22 heeft Saul Wold het volgende geschreven:
> > On 02/07/2012 01:18 PM, Koen Kooi wrote:
> >> Do we have enough people present to do an expert track at the yocto
> dev days next week? I bet we can do a nice code sprint :)
> >>
> > Many of the experts will be working the dev days presenting, and
> > sharing during the advanced session (which may be doing some work)!
> > It was a thought at one point.
>
> I know at least one expert that will not be presenting for sure :)
The developer day has sections which are of a hands on labs format and
we're trying to ensure there are people around to help out with those.
I'd love to get people together to do code sprint type activities but
there isn't really enough time to do everything and I know my schedule
has many meetings already spread over the conference. I wouldn't want to
do the code sprint at the expense of the developer day.
If we had a list of things we wanted to discuss/work on and an idea of
who needed/wanted to be involved, we probably could find a corner
somewhere and some time to look at things though.
Cheers,
Richard
next prev parent reply other threads:[~2012-02-08 15:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-07 21:18 Expert track at yocto dev day? Koen Kooi
2012-02-07 21:22 ` Saul Wold
2012-02-07 21:27 ` Koen Kooi
2012-02-08 15:37 ` Richard Purdie [this message]
2012-02-08 15:54 ` McClintock Matthew-B29882
2012-02-08 18:16 ` Philip Balister
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=1328715426.3164.13.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox