Date:
Participants:
Filled from Google report
Slides:
Notes:
LM: To recap the content - do you have a list of tools to be included in the repo?
JK: buildmgr, packgen - packcheck is on the roadmap for end of Sept
LM: (shared libraries libs/rtemodel) Does it correspond to one release of CMSIS build?
EF: Project manager proposed here is the spec around cprog or it’s a tool?
JK: It’s a tool
EF: The approach for the project manager will be to handle first configuration and after other topics like multicontext
JK: Need to keep the end goal in mind but start with a level of complexity we can handle. Wouldn’t say we have a big plan for this yet. Everyone can contribute a strategy.
RK: Need to lay out the end goals so we don’t forget requirements. If you think there are gaps, please raise it. Will still be an iterative approach
DJ: Think this is aligned with the original MVP approach.
JK: Don’t want to be nailed down vs what we have previously said. Still need to define what’s the best starting point. Could start from user-driven or from a yaml file.
proposal from Reinhard in GitHub (#21):
MD: Need to take some time to understand what you mean.
RK: Don’t rule out that there’s a gap/misunderstanding.
JK: Not seeing the link to the actual device.
RK: This would be part of a condition. Maybe middleware doesn’t care what device it runs on. Requirements can be nested.
AOB
JK: cpackget - release