docs: Update Draft TRG 1-4

[FaGru3n]

Description

• add reference to draw.io
• add draw.io example

fixes #427

ongoing IP-Validation Checks

• https://gitlab.eclipse.org/eclipsefdn/emo-team/iplab/-/issues/11149
• https://gitlab.eclipse.org/eclipsefdn/emo-team/iplab/-/issues/11150
• https://gitlab.eclipse.org/eclipsefdn/emo-team/iplab/-/issues/11151
• https://gitlab.eclipse.org/eclipsefdn/emo-team/iplab/-/issues/11152

Preview

Pre-review checks

Please ensure to do as many of the following checks as possible, before asking for committer review:

• DEPENDENCIES are up-to-date. Dash license tool. Committers can open IP issues for restricted libs.
• Copyright and license header are present on all affected files

[stephanbcbauer]

@FaGru3n to be honest i am not sure if a change is needed :)

[Siegfriedk]

We need to clarify this TRG a little bit more:

Generally speaking i don't think its enough to just have a *.svg file available because, while you can change it (its plain text) without knowhing which tool you used to generate it, you can't really change it. You can fix existing text, you might be able to update some lines etc. but not 'change' the content.

We might even make it mandatory to have a short section in the README.md to clarify which tool they use. draw.io for example is a good option but if you need a speicifc version you might need to document how to use it with something like a container image we host ourselfes and we need to align on a version.

[stephanbcbauer]

We need to clarify this TRG a little bit more:

Generally speaking i don't think its enough to just have a *.svg file available because, while you can change it (its plain text) without knowhing which tool you used to generate it, you can't really change it. You can fix existing text, you might be able to update some lines etc. but not 'change' the content.

We might even make it mandatory to have a short section in the README.md to clarify which tool they use. draw.io for example is a good option but if you need a speicifc version you might need to document how to use it with something like a container image we host ourselfes and we need to align on a version.

@Siegfriedk not sure if this helps, but at least in the SVG file which were created by draw.io there is always this note in the header

[FaGru3n]

bfdc244

outdated branch that was checked

[stephanbcbauer]

LGTM Thank you

[FaGru3n]

I will wait for @Siegfriedk for the approval before merge 😉

[SebastianBezold]

I think if we want to restrict contributors to specific tools, then we need to provide more guidance.
Alternative would be only mention the tools as valid options (golden path) and only have mandatory guidelines, like:

• You need to contribute the "raw" editable source
• Used tools need to be usable by anyone without the need of a licence or similar (prefer open source tools)
• Tools should be OS independent

and so on

[FaGru3n]

updated my branch current view: