transparency about used configuration

[trittsv]

For me interop testing makes only sense if vendors are using their default values in the test.

DDS-users mainly just use the defaults and a little subset of the QoS.
So they may end up in a system which does not comply to the specification - but they think they are compliant.

Some vendors have setttings like "enable-dds-spec-compliancy" which is not enabled by default.

Questions:

• Are the used settings per dds-vendor transparent available?

What i would like:

• the interop repos should require dds-vendors to use default values.

[mitza-oci]

It's not going to be practical to mandate use of default values, that's really an implementation decision beyond the scope of the specs.

We could add a README in each product's subdirectory with build and runtime configuration needed for the test.

For OpenDDS, everything in built in public https://github.com/OpenDDS/OpenDDS/blob/master/.github/workflows/dds-rtps.yml

[angelrti]

There is a section in the produced documentation for this: https://github.com/omg-dds/dds-rtps/blob/master/doc/test_description.template.rst#considerations-per-product
Probably we can leverage this section to be a top-level section