All of lore.kernel.org
 help / color / mirror / Atom feed
From: Trevor Woerner <twoerner@gmail.com>
To: yocto@yoctoproject.org, openembedded-core@lists.openembedded.org,
	yocto-advocacy@yoctoproject.org
Subject: OEDAM @ SCaLE 2019
Date: Thu, 1 Nov 2018 10:04:17 -0400	[thread overview]
Message-ID: <20181101140417.GA12376@linux-uys3> (raw)

Hello Fellow YP/OE Enthusiasts!

There were discussions at our recent OEDEM regarding:
- our next developers meeting
- SCaLE 2019
- expanding/adding to the YP/OE presence at conferences (i.e. our own
  miniconf?)

Please see time indices: 12:13 and 16:45
https://docs.google.com/document/d/1YDAHjIOXCIgvSZVOKCYLxa8h26dkruX8zspoge7zCpk

Unfortunately, although lots of opinions were expressed, nothing concrete was
decided. Many people pointed out that their travel budgets are already
strained or maxed out, so adding another conference would be difficult if not
impossible. It's unclear how many "core" YP/OE people might show up at next
year's SCaLE. Also, given that this year's ELC scheduling hiccup is a one-off,
maybe it doesn't make as much sense to put in all the work required to run an
OEDAM at SCaLE if it's only ever going to happen once. Therefore I think I can
safely say the organizing committee for YP/OE Things at SCaLE 2019 is leaning
towards not running an OEDAM.

It's not too late to change our plans. If a large number of core people reply
to this email saying they want and OEDAM in March and will be available in
Pasadena, then we could accommodate it. It's just that we didn't leave
Edinburgh with the feeling that an OEDAM at SCaLE was feasible. Also, at this
point SCaLE isn't on the radars of many of the core YP/OE people, and
currently the conference tends to attract users rather than developers (or so
is my impression).

Thoughts?

Best regards,
	Trevor


             reply	other threads:[~2018-11-01 14:04 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-01 14:04 Trevor Woerner [this message]
2018-11-01 15:32 ` OEDAM @ SCaLE 2019 akuster808
2018-11-01 15:32   ` [OE-core] " akuster808
2018-11-01 15:48   ` Trevor Woerner
2018-11-01 15:48     ` [OE-core] " Trevor Woerner
2018-11-01 19:56 ` Jon Mason
2018-11-01 19:56   ` [OE-core] " Jon Mason
2018-11-01 20:00   ` darknighte
2018-11-01 20:00     ` [OE-core] " darknighte
2018-11-02  2:27   ` Trevor Woerner
2018-11-02  2:27     ` [OE-core] " Trevor Woerner
2018-11-02 15:57     ` akuster808
2018-11-02 15:57       ` [OE-core] " akuster808
2018-11-02 21:51       ` Sean Hudson
2018-11-02 21:51         ` [OE-core] " Sean Hudson

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=20181101140417.GA12376@linux-uys3 \
    --to=twoerner@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=yocto-advocacy@yoctoproject.org \
    --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 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.