OEDEM 2015

From Openembedded.org
Revision as of 10:30, 9 October 2015 by Jefro (talk | contribs) (Proceedings)
Jump to: navigation, search

The 2015 OpenEmbedded Developer's European Meeting will take place Friday, Oct 9, 2015 in Dublin, Ireland. Part of this meeting will also constitute the annual OE General Assembly, and some corporation/eV matters will be discussed.

Location and Time

The Gibson Hotel
Point Village
Dublin 1, Ireland
+353 1 681 5000

9am - 5pm (note: times may change)

Gibson Hotel is at the end of the red LUAS line, adjacent to the stadium. Come up to the 3rd floor and follow the signs for the Cordoba room. (the sign says "Mtg", that's us) There is coffee here. See you all soon

OpenEmbedded eV General Assembly

We have a short administrative meeting before starting the Developer meeting. All are welcome for this.

  • Proposal to dissolve the current e.V. and re-constituting it in the U.S. to reduce the administrative burden for the project.
  • Define a method for identifying lapsed memberships.
  • Proxy form File:Proxy instructions-oe.pdf
  • Meeting Minutes


  • Metadata
    • OVERRIDE syntax: is it time to reconsider _?
    • meta-yocto -> meta-poky. People are still spending too much time explaining reality. (Crofton)
  • BSPs (tlwoerner)
    • Standards for BSP behavior. (Crofton)
    • feedback on layerindex to indicate BSP:
      • last successful compile (feedback from outside builders?)
      • last successful boot
      • master branch parsability (perhaps ties into bugzilla 7792?)
    • several BSP layers to choose from for some boards, none for others (linux.com SBC survey)
    • guidelines/requirements for setting up a new BSP on layerindex
      • bugzilla
      • mailing list (use general mailing list(s) for patches?)
      • git.yoctoproject.org/<yourbsplayer>
    • making sure BSP layers only touch the variables/settings they should touch
      • should a BSP layer ever use = ?
    • does/should a BSP produce artifacts that are easy to install to SD cards? (Crofton)
  • Processes
    • LayerIndex feature requests (tlwoerner)
    • build feedback (autobuilders and off-site)
    • Build and test failures on the public Autobuilder (Bluelightening)
  • Systemd
    • Systemd packaging. As new things appear, they are lumped into one package. Update split? (Crofton relaying info)
    • Can we get systemd's first-boot support to work? It is currently disabled in the systemd recipe by touching /etc/machine-id. (Saur)
    • How to make it easy to setup a system "the systemd way"? New DISTRO_FEATURE or IMAGE_FEATURE? (Saur)
      • Link /bin -> /usr/bin, /lib -> /usr/lib, etc.
      • Change ${systemd_unitdir} to /usr/lib.
      • Make the systemctl wrapper install in ${systemd_unitdir} rather than ${systemconf}/systemd.
        • This should also happen when installing a package in runtime.
  • Advocacy
    • There are still a lot of projects (too many?) not using OE (tlwoerner)
    • why aren't more projects using OE?
    • how can we get more people using OE?
    • who should we be targeting? (build people (obviously), kernel devs? user-space devs?)


If you plan to attend, please list your name below.

  1. Jeff Osier-Mixon (jefro)
  2. Philip Balister (Crofton)
  3. Trevor Woerner (tlwoerner)
  4. Anders Darander (andersd)
  5. Marco Cavallini (mckoan)
  6. Koen Kooi (koen)
  7. Alexandre Belloni (abelloni)
  8. Armin Kuster (armpit)
  9. Belén Barros Pena (belen)
  10. Peter Kjellerstedt (Saur)
  11. Alejandro del Castillo (adelcast)
  12. Denys Dmytriyenko (denix)
  13. Sean Hudson (darknighte)
  14. Nathan Rossi (nrossi)
  15. Mark Hatle (fray)
  16. Nicolas Dechesne (ndec)
  17. Paul Eggleton (bluelightning)
  18. Andrei Gherzan (agherzan)
  19. Felipe F. Tonello (ftonello)
  20. Changhyeok Bae (chbae)
  21. Saul Wold (sgw)
  22. Ashish Shrivastava
  23. Pascal Bach (bachp)
  24. Richard Purdie (RP)
  25. Michael Halstead (halstead)


RAW notes shown in boxes like this

Introduce TSC

  • Martin Jansa (jama)
  • Mark Hatle (fray)
  • Paul Eggleton (bluelightning)
  • Richard Purdie (RP)
  • Khem Raj (khem)

go over agenda BSP topic first to accommodate member travel


Paul described layer index process & how it works
BBP layers also come into toaster, expose to people, dependency list very important - snapshot when setting up toaster
module branches - will look in repo for branches
some layers don't have a master branch, don't show content - need way to present in UI
DD automatically parse layer to check for required content? PE do want, necessitates background queuing process
parse w/dependencies