LM: 1. Don’t think the split is so clear in today’s solutions. We have a “config template”. Want to see some structure in example projects. RT folder doesn’t appear in any of our specifications. Would like to replicate existing project structure since it’s well-known. 2. In CubeMX can have many files that get generated. Sometimes depending on the origin of the file they might need to end up in a different target folder. Example - I2C.
JK: Next step to create a proposal and specification for these extensions. Create a separate issue for this so we look at it in isolation.
Potential Tool Flow - input from STMicroelectronics
JK: Next steps?
LM: Frederick needs to join us to introduce the concept.
JK: Put on the agenda for next week. Good to agree the vocabulary (e.g. “what is a project”) and what’s in scope.
EF: Important to find a common ground on the way we define projects and elements.
JK: Benefit of using YAML vs JSON
LM: Suggest a pros and cons table
JK: Raise as an action for people
LM: Interesting to review the decision making process. Have people contribute pros and cons and then take a vote - or we appoint a tech lead to take a decision?
GH: Pros and cons sounds sensible but also look at general usage. Ease of use is a big thing here.
JK: Input from Linaro on decision making?
BF: (from Linaro p.o.v.) no magic solution: as discussed pros and cons and usage examples → then decision taken ideally on technical merit.
JK: Need also attending companies to think about representation for e.g. approving pull requests - propose someone to get the necessary permissions.