How to proceed with code conformance fixes upstream

[roncapat]

Simple question, but I think we may establish a standard approach on this (unless there isn't one already and I missed it).

Take as an example: #7

How to proceed upstream? I propose by issuing PRs with a sort of Space ROS standard text like:

SpaceROS Code Conformance

This PR addresses a code conformance issue detected by Space ROS code analysis tools.

Tool: eg. clang-tidy
Issue: eg. default arguments on virtual methods
Full (SARIF?) output:
....

...and then from #7 add a post referencing the opened PR for tracking purposes?

Since there are many things to fix upstream, I think we need an easy way to track the PRs and from time to time step over all the still to-be-merged ones to check if further support/info is needed upstream or simply to kindly trigger the maintainers.

We may expand on this in sort of CONTRIBUTING.md file to be linked on top of each meta-issue like #7.

[EzraBrooks]

Action item from July 27 meeting: document standard processes with templates, etc. for code conformance PRs upstream

[roncapat]

Since I have not been able to join the meeting, is there some additional feedback / something on which you could expand a bit? how may I help?