Difference between revisions of "OEDAM 2016"

From Openembedded.org
Jump to: navigation, search
(Location and Time)
(Location and Time)
Line 3: Line 3:
Friday April 8 2016  
Friday April 8 2016  
Marriott Marquis
Marriott Marquis<br>
333 W Harbor Dr
333 W Harbor Dr<br>
San Diego, CA 92101
San Diego, CA 92101<br>
(619) 234-1500
(619) 234-1500<br>
Adjacent to the Manchester Grand Hyatt
Adjacent to the Manchester Grand Hyatt

Revision as of 05:10, 24 March 2016

Location and Time

Friday April 8 2016

Marriott Marquis
333 W Harbor Dr
San Diego, CA 92101
(619) 234-1500
Adjacent to the Manchester Grand Hyatt

(after ELC [Apr 4-6] and Yocto Project Developer Day [Apr 7])


Armin Kuster (Armpit)
Behan Webster (behanw)
Denys Dmytriyenko (denix)
Jan-Simon Möller (dl9pf)
Philip Balister (Crofton|work)
Sean Hudson (darknighte)
Tim Orling (Moto-timo)
Trevor Woerner
Tom King (ka6sox)
Mark Hatle (fray)
Jeff Osier-Mixon (jefro)
Frederick Ollinger (Follinge)
Marc Villanueva (Tentative)
Rudolf Streif (rstreif)

Agenda Items

  • Review items from last meeting in Dublin (Please add remarks)

BSPs & Layer Index

  • oe driving toward machine readable files, can also drive from layer

test (yp compat) side - KK

  • publicize defs of each list? discuss on members list - where to

overall architecture discussions belong

  • TSC to add new mailing list specifically about project

architecture, no patches, and determine list name

  • KK bring discussion to new mailing list

BSP standards - standards exist,coming soon are methods for comparing

a given layer with the standard

  • need wiki documentation for TSC to ratify
  • document distro vs. machine policies, other best practices

BSP layer availability

  • encourage board vendors to provide a BSP, make it easier to do so
  • ask yp ab to talk to linux.com [PB] - community issue
  • look at digi manual (i.e. "just add bsp changes in local.conf")

meta-yocto to meta-poky

  • RP to take action on the YP side, possibly not for 2.0
  • formalize lowercase as mandatory requirement for overrides, look

for other options in the future

Layer Index feature requests discussed with layer index build feedback>>

  • ask for cycles from employers to work on these issues
  • make people aware, help with triage, provide resources


  • need a method for tracking CVs


complaints: more package config, comments; look at packaging to have minimal systemd even with options available

  • need someone with time available to work on it
  • need to get systemd feedback, people using systemd talk to package maintainer
  • file systemctl wrapper bug


  • board to discuss advocacy/community, invite jefro to meetings

Potential OE Day at ELCE next year

  • board: do a proper cfp