Erik Jaegervall (Jägervall)

I do not know the background on why `#include` was selected originally. I guess any proposal that easily could be integrated by existing tooling could be considered. There is by...

I came to to think about this issue when working on vss-tools code. There is a method `yamilify_includes`, currently at https://github.com/COVESA/vss-tools/blob/master/vspec/__init__.py#L665 that contains the following comment. So I assume it...

Meeting comments: - Shall individual files be added separately? (i.e. not in *.tar.gz)

So far for our releases we typically summarize the changes in a few lines and then also include an auto-generated release note ("What's Changed") with the headers of all commits....

Hi @nijicompany - Contribution to VSS is welcome (but note that VSS is managed by the COVESA organization, not Eclipse, even if there are some Eclipse projects that use VSS,...

Next time we discuss this we could also discuss if we would need (in long term) possibility to cross-reference trees. A hypothetical example could be that VSS specifies a signal...

I am not sure that I fully understand your comment, I think we need better examples on how the "proxy" concept in your proposal is supposed to be used. Assume...

Meeting notes: - Good topic for next AMM.

It is true that `validate` is not a VSS standard atttribute. The VSS Makefile is mostly intended for testing of the VSS standard catalog. If you modify VSS in your...

Do we generally see a need to have more detailed unit descriptions? I can see that there in some cases are ambiguities, but for a general example like "Mass measured...