Future of vspec2aaproperties (branch code_generation) and other branches

[erikbosch]

As of today we have a half finished (?) tool vspec2aaproperties in branch code_generation. We also have some issued related to it, like #145 and #148

Some thoughts:

• Is it likely that anyone will contribute something more to this branch?
• Is it worth saving?
• How shall we document the branches we have, i.e. purpose and content? In the wiki? We have some other branches (see below) that are not actively used. What is our policy for keeping them?

If we want to keep it I would suggest renaming it, as the current name code_generation does not really say much about the content/intent. Something like feature/vspec2aaproperties would make more sense, or if we want to create an issue to track the work and call the branch issue/<number> or similar. I assume that we also in the future now and then might need temporary collaboration branches, so having a naming standard could make sense.

https://github.com/COVESA/vss-tools/tree/serialization
https://github.com/COVESA/vss-tools/tree/temp_csv2pdf_test_branch

(@gunnarx - you maybe know the history/status of the branches above)

[erikbosch]

Discussed at meeting - should at least be refactored so names are more clear.

@gunnarx - could you provide a short description of what each of the branches contain, and comment on if all of them are valuable to keep

[erikbosch]

@gunnarx - could you possibly comment on the content of those branches