Meeting Location:
Fira Congress Hotel (200 m to the Fira Congress Grand Via)
Room Name: Paris Meeting Room
Requested: To RSVP for the in-person meeting, please email info@edgexfoundry.org by September 28
*** To be added directly to the meeting invite (for dial-in or in-person participation), please email info@edgexfoundry.org
Meeting Dial-in:
Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/863393388
Or iPhone one-tap (US Toll): +16465588656,,863393388# or +16699006833,,863393388#
Or Telephone:
Dial: +1 646 558 8656 (US Toll) or +1 669 900 6833 (US Toll)
+1 877 369 0926 (US Toll Free)
+1 877 853 5247 (US Toll Free)
Meeting ID: 863 393 388
International numbers available: https://zoom.us/zoomconference?m=FfYBnfu_ng3R-fnTJLnKFcUYmKzDUNuq
Tentative Agenda:
- 8am - 9am: Access to meeting room + Continental Breakfast
- 9am - 12pm: Meeting
- 12pm - 1pm: Working Lunch
- 1pm - 5pm: Meeting
- 5pm - 5:30pm: Meeting Close / Recap AI's
- 9pm: Optional Dinner for TSC F2F attendees - location TBD
Proposed Agenda Topics
Barcelona Release
Release/Availability Plan
Performance against original plan
- Moved to California release task list
- Lessons Learned
Upcoming Release Strategy
Discussion & Decisions
Late January or Early Feb 2018 – Specific date and any method of release to be discussed and ratified
Proposed for reaction/discussion/ratification
June 2018 – California @ IoT DevCon, Santa Clara, CA June 5-6 (https://www.iot-devcon.com/)
- Nov 2018 – IoT Tech Expo (Santa Clara) or IoT World (London)
EdgeX Real Time
Presentation from Samsung on potential new EdgeX real time track & Factory Automation Vertical market domain
Discussion on new working groups
- Discussion on inclusion in California plan
California Preview Release (Jan 2018)
Go Services (core data, core metadata, command, export client, and elements of Go SDK) and Testing - Can Go services be “certified” as drop in replacements by our test framework(s) by that time?
ARM versions of these and other services
C SDK availability
Demos
Security and System Management API’s
implementation strategy?
California Release Target Functionality
California Release
Target deliverables
First security and system management capabilities (what are they?)
Footprint and performance targets (what are they and how achieved?)
Full Arm support (what does this mean?)
Additional OS support (which specific OS?
Additional north bound connectivity (to what?)
Additional south bound connectivity (to what?)
Additional SDK’s?
Real Time Version
- Vertical Domain Functionality
Releases after California
Suggested Names
Release Frequency
- High level roadmap targets
Working Group Elections in Jan/Feb meeting
Formal Process
What to know
- How accomplished
Meeting Slide Deck:
TBD
Meeting Recording:
TBD