Table of Contents:
Attendance
Attended | Proxy (w/ @name) | Holiday | Did Not Attend |
|---|
Name | Company |
|---|---|
Knox Lively | |
Stephen Berard | |
Patrick Robb | UNH IOL |
Drasko Draskovic | Abstract Machines |
Dan Mihai Dumitriu | Midokura Japan K.K. |
Brad Clements | Murkworks |
Jason Shepherd | |
Lincoln Lavoie | UNH IOL |
Graeme Cloughley | Edge Inference |
Marshall Meier | Emerson |
Minutes
Time (mins) | Item | Presented By | Presos/Notes/Links/ |
|---|---|---|---|
5 | Meet and Greet/Call to Order | Knox/Stephen | |
Meeting Summary
Ocre Project Status Update
General Discussion
Action Items
Meeting Materials (recording, transcript, slides, etc.)
Recording (and transcript):
Slides:
linux port - presuming the runtime would be a userspace application, which approach would be most acceptable?
interface/shim layer in a library
interface/ship layer only via include files
lots of #ifdefs in the runtime code
would the linux port be a library itself, so that it could be embedded inside other applications
sample driver - it would be helpful to see how drivers are actually exposed by the runtime and consumed by containerized applications. Understanding this could impact how linux support is implemented
Topics to Consider
Topic | Comments | Submitted By |
|---|---|---|
Unit Tests Update | Status update on unit tests being developed by Atym and timeline for upstream contribution | |
Linux Port Considerations | Discuss approach for Linux port implementation: userspace application structure, interface design, library considerations, and driver exposure methodology with example use cases | |