Clean up config.yml

[baentsch]

This is to suggest at least a one-time clean-up of the file -- possibly creating a more regular/codified way to keep this file current with people leaving for good, e.g., Thomas and Pravek).

[dstebila]

Do you mean a restructuring? Or just a pass through to check if the right people are still in the right places?

[baentsch]

The latter. As mentioned above, Pravek and Thomas are no more participating but are still in config.yml. Removing Pravek will immediately "orphan" liboqs-cupqc-maintainers -- given there's anyway no active development (see NVIDIA announcement on a new library without corresponding OQS update) I wonder what's the right solution here --> Worthwhile a discussion. Norm is doing releases but no contributions, nor maintenance as per oqs-provider GOVERNANCE and definitely has no code ownership whatsoever so why isn't he in oqs-release-managers instead? Another discussion. My absence documented in liboqs GOVERNANCE also isn't reflected in the file (but arguably should be better corrected there than in config.yml) -- but anyway worth while another conversation (how to handle absences).