OEDAM 2016: Difference between revisions
Line 16: | Line 16: | ||
===BSPs & Layer Index=== | ===BSPs & Layer Index=== | ||
* oe driving toward machine readable files, can also drive from layer | |||
test (yp compat) side - KK | test (yp compat) side - KK | ||
* publicize defs of each list? discuss on members list - where to | |||
overall architecture discussions belong | overall architecture discussions belong | ||
* TSC to add new mailing list specifically about project | |||
architecture, no patches, and determine list name | architecture, no patches, and determine list name | ||
* KK bring discussion to new mailing list | |||
===BSP standards - standards exist,coming soon are methods for comparing=== | ===BSP standards - standards exist,coming soon are methods for comparing=== | ||
a given layer with the standard | a given layer with the standard |
Revision as of 12:38, 8 March 2016
Location and Time
Friday April 8 2016 (after ELC [Apr 4-6] and Yocto Project Developer Day [Apr 7])
Attendees
Armin Kuster (Armpit)
Denys Dmytriyenko (denix)
Philip Balister (Crofton|work)
Sean Hudson (darknighte)
Tim Orling (Moto-timo)
Trevor Woerner
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
Security
-> need a method for tracking CVs
Systemd
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
Advocacy
-> board to discuss advocacy/community, invite jefro to meetings Potential OE Day at ELCE next year => board: do a proper cfp