Establish & document a way of working for the Cross-CQM SP API description

[tlohmar]

Problem description
Overall intention is to create an external facing description of the differed capabilities and purposes of the APIs within CQM Sub Project.

During the meeting on 12th May, we agreed to

• Develop the external facing description using markdown
• Aim to discuss newly provided text contributions and edits during the Wednesdays online meetings
• All text contributions and edits are collected using Pull Requests, preferably limited number of edits.
• It is preferred merging PRs after the weekly meetings, when possible

Expected action

• Merge the working draft into main
• Test the way of working and adjust, when needed.

Additional context

[hdamker]

• All text contributions and edits are collected on a single working branch

How should contributors provide their changes on this "working" branch? Only codeowner have the option to commit directly to the branch. Other contributors would need to open pull requests against this branch ... which defeats the purpose as they are used to do this against the main branch. If (and only if) they are providing PRs against the working branch you have two levels of discussions: which PRs are getting merged into the working branch and if the working branch gets merged into main.

In short: the purpose of the "working branch" is unclear for me, seems to exclude contributions from non-code owners, at least without further explanation how it should work.

[tlohmar]

Ok, I see your point. Better then to work with normal Pull-Requests.