Profile operations mk202602

[mkurzman]

This branch was created from develop as of today.
The draw.io file was extended by the OpenSourceProject Class and merely the md-file for OpenSourceProject was added in the model section as base for next review round.
This is merely a PR as base for common review in the operations profile group.
The missing md-files for properties etc. still need to be added in the next iteration after the high-level discussion on Class-level have been done.

[bact]

I would suggest to leave draw.io diagram unchanged in this PR.

And once everything is settled, update the diagram in another PR.

Or there will be a difficult to manage conflicts over the diagram file.

We now have one PR pending for diagrams changes
#1220

[bact]

Looking forward, we may like to put one diagram per one file in the future, so it will be easier to manage.

Or rely on "text based" descriptive diagram (like PlantUML and Mermaid), which is more friendly to text version control system.

[zvr]

+1 for having different .drawio files, one per profile. That's how they are being used, anyway: each one in a separate chapter in annex A.

FYI, spec-parser already produces a complete "text-based" diagram, in PlantUML format (command line switches -P or --output-plantuml, IIRC). But manually creating/manipulating in diagrams.net results in a more aesthetically appealing diagram.

[umm0]

Just FYI, I needed to switch the base branch back and forth to update the file diff view to show the correct state after #1228 .
Github apparently does not do this automatically.

[bact]

FYI #1220 (that modifies diagram) has just merged (thanks all the reviewers). So it should be good now to edit the diagram file -- please merge from develop again one more time.