From: "Scott Murray" <scott.murray@konsulko.com>
To: chris.laplante@agilent.com
Cc: Khem Raj <raj.khem@gmail.com>,
"sjolley.yp.pm@gmail.com" <sjolley.yp.pm@gmail.com>,
"yocto@yoctoproject.org" <yocto@yoctoproject.org>,
"openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] Yocto Project Status WW25'20
Date: Tue, 23 Jun 2020 18:56:20 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.22.394.2006231849410.2920@godzilla.spiteful.org> (raw)
In-Reply-To: <MW2PR12MB2474BE8BA49651369970014F8B940@MW2PR12MB2474.namprd12.prod.outlook.com>
On Tue, 23 Jun 2020, Chris Laplante via lists.openembedded.org wrote:
> > > Does anyone know what the intended audience is for the Developer Day
> > presentations? E.g. would someone who uses bitbake day-to-day but perhaps
> > doesn't edit recipes benefit?
> > >
> >
> > I would say look at the schedule and see if there are talks of interest to you.
>
> I did, but the schedule says nothing about the level of the topics.
In earlier developer days there were two tracks, one for beginners new to
the project, and one for more advanced topics. The last couple have just
had a single track that splits the difference with talks that target
users with intermediate or above experience with the project. If you're
familiar with the basic concepts of OpenEmbedded / Yocto Project, I
suspect you should have no problems.
Scott
next prev parent reply other threads:[~2020-06-23 22:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-23 14:48 Yocto Project Status WW25'20 Stephen Jolley
2020-06-23 15:58 ` [OE-core] " Chris Laplante
2020-06-23 19:52 ` Khem Raj
2020-06-23 20:05 ` Chris Laplante
2020-06-23 22:56 ` Scott Murray [this message]
2020-06-24 4:59 ` Reyna, David
2020-06-24 12:40 ` Chris Laplante
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=alpine.LFD.2.22.394.2006231849410.2920@godzilla.spiteful.org \
--to=scott.murray@konsulko.com \
--cc=chris.laplante@agilent.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.com \
--cc=sjolley.yp.pm@gmail.com \
--cc=yocto@yoctoproject.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