We talked about this in the meeting this morning. It makes sense to proceed stepwise: First, having consistent descriptions and Lena's feedback (T27677) integrated for release v1.0. We should not reuse text from the paper until it is accepted. Once it is accepted, we can still decide on the revision of the report text (T27420).

As unknown sites are appearing on our dashboard, we should introduce authentication:
https://blog.kitware.com/cdash-authenticated-submissions/

Finally!

Discussion result: if GDCM does not fix it fast enough, we should take option 3 (as we very likely need a dedicated DICOM US mime type anyways).

Deleted branch release/T27784-2020-Week-39.

Whitespaces should be trimmed here as well, e.g. if a space character is entered and report generated, this error also occurs.

@nolden I tried the "make package" and it went through without any issues.
Should I upload the result here? Or is it just about the information that there are no error?
Could you please explain what you mean with "target machine"?

Pushed new branch release/T27784-2020-Week-39.

@schererj we looked at the debug output, thanks. Unfortunately it seems to be complicated ... I would ask you to try another thing:

@kislinsk : I just noticed we had some earlier discussions and there is a branch which fixes two minor issues, not sure if relevant for option (1):

Request discussion result:

We discussed this task in the MITK meeting and we want to go with option (1). In addition, we want to syncronize the branches of rMITK MITK and rMPT MITK-ProjectTemplate and add the project template as extension to all of our CI clients. We should also look into the new template repository feature of GitHub.

Same for "Introduce the number of samples and click >>".

In my opinion, this sentence can be removed in general. At this stage the user should already know how to navigate. It does not add any valuable information.