Guido Wolf Reichert

I am using Wolfram System Modeler for development and per default everything _either is one large file or gets separated into one file per class_. A comment like yours before...

[Section 18.13](https://specification.modelica.org/master/annotations.html#license-texts) makes it the developer’s sole responsibility to include required license texts. To reinforce this requirement, I believe it prudent to acknowledge the following **Tooling requirements for comments**: 1....

As they explain in the GNU FAQ, putting SPDX-headers and other legal comments into source files is _not a legal requirement per se_ if all your files are copied together...

Let’s narrow the requirement to exactly what matters for license headers then: > **Comment preservation (SPDX only).** >Any tool that re-serializes a .mo file—whether to pretty-print, split, concatenate, or export—shall...

I can completely understand what you are saying, Malte. Currently, I find GUIs great for modeling–but they tend to have some kind of _diminishing rates of utility_ once you try...

I appreciate the perspective that comment-handling borders on “tool territory,” but from a library developer’s vantage point it really feels like our source code is treated as a _second-class citizen_....

What can and should be the **next steps** in this regard?

It’s great to see this proposal being discussed. Recently, I experimented with the REUSE framework in a new Modelica project, and I’d like to share first experiences that illustrate how...

Has this been making any progress?