Difference between revisions of "OEDEM 2017"

From Openembedded.org
Jump to: navigation, search
m (Agenda Items: Add "Backwards compatibility checking sstate-cache")
Line 86: Line 86:
== Minutes ==
== Minutes ==
=== OEDEM: ===
=== Portland OEDEM AR's: ===
Looking for minutes

Revision as of 17:47, 27 September 2017

Location and Time

Sunday, 22 October 2017
Start at 0900

(before ELC-E [Oct 23-25])

Yes, we know it is Sunday. Best we could do this year.

NOTE: venue has changed, we are now at:

JURY'S INN Prague Sokolovská 204/11, 186 00 Praha 8-Florenc, Czechia

This hotel is across the street from the Hilton (ELCE venue). If you have any difficulty please let jefro know.

Planning to Attend

  • Jeff Osier-Mixon "Jefro"
  • Behan Webster (behanw)
  • Philip Balister (Crofton)
  • Martin Jansa (JaMa)
  • Scott Murray (smurray)
  • Peter Kjellerstedt (Saur)
  • Armin Kuster (Armpit)
  • Paul Barker (paulbarker)
  • Myunghun Chun
  • Changhyeok Bae (chbae)
  • Adrian Ratiu (aratiu)
  • Josef Holzmayr (LetoThe2nd)
  • Jan Leupold
  • Anders Darander
  • Sean Hudson (darknighte)
  • Tim Orling (moto-timo)
  • Ricardo Ribalda (ribalda)
  • Nicolas Dechesne (ndec)
  • Richard Purdie (RP)
  • Andrei Gherzan (agherzan)
  • Denys Dmytriyenko (denix)
  • Anton Gerasimov
  • Rich Persaud
  • Koen Kooi
  • Marek Vasut (marex)
  • Ruslan Bilovol
  • Grygorii Tertychnyi
  • Bruce Ashfield (zeddii)
  • Mark Hatle (fray)
  • Jan-Simon Möller (dl9pf)
  • Mike Looijmans flight landing at 8:15
  • Mario Domenech Goulart (mario-goulart)
  • Andrea Galbusera (gizero)
  • Michael Ho
  • David Reyna

Attending in the afternoon or not sure because landing too late

  • Marco Cavallini (mckoan)

NOTE: we will make every effort to provide a web/phone link for remote attendees

Agenda Items

  1. Review open Action items from previous meeting(s?)
  2. Stack Overflow report (From someone who regularly watches stackoverflow)
  3. Demos for FOSDEM and other events. Good chance to (discretely) show your company's work. (Philip)
  4. Long-term releases support (more than one year)
  5. Automated CVE checking, issues with cve-check-tool, alternative tools
  6. MvTest - Test Automation framework
  7. License compliance
  8. Backwards compatibility checking sstate-cache (https://lists.yoctoproject.org/pipermail/yocto/2017-June/036920.html)
    1. How do we help folks to generate a source tarball in addition to a listing of source in their build?
  1. Feedback on current stable branch maintenance (Maintainer will leave room to encourage openness)
    1. How is it working
    2. What is not working
    3. Areas to improve
  1. Meta-openembedded maintainers
    1. How is it working
    2. Areas to improve
    3. Who's willing to help?
      1. meta-oe ( armpit will take)


Portland OEDEM AR's:

Looking for minutes