The created documentation from the pull request is available at: docu-html

Should this not rather be in docs-as-code?

Should this not rather be in docs-as-code?

I asked for the place in the last process community meeting, there was different opinions, as I understood, @aschemmel-tech wanted it all in the score repo, but we can discuss it again

Should this not rather be in docs-as-code?

I asked for the place in the last process community meeting, there was different opinions, as I understood, @aschemmel-tech wanted it all in the score repo, but we can discuss it again

I mean we can always move it afterwards, so it's not too much of an issue.

I just think it would make sense to have the tool qualification in the tool repository it qualifies, like from a logical standpoint.

Should this not rather be in docs-as-code?

I asked for the place in the last process community meeting, there was different opinions, as I understood, @aschemmel-tech wanted it all in the score repo, but we can discuss it again

Just to explain my reasoning: we will have also tool evaluation and even qualification for external tools like Bazel where we will not have an own Repo for it. Where to put those documents? I think somewhere centrally. And then it is better to have one place and not several to look for.

Should this not rather be in docs-as-code?

I asked for the place in the last process community meeting, there was different opinions, as I understood, @aschemmel-tech wanted it all in the score repo, but we can discuss it again

Just to explain my reasoning: we will have also tool evaluation and even qualification for external tools like Bazel where we will not have an own Repo for it. Where to put those documents? I think somewhere centrally. And then it is better to have one place and not several to look for.

I mean from my side, both is fine.
We can easily link from the repositories (where we do have one) to the score place.
So let's have it all in here then.