GitLab

Currently the NonFreeAssets anti-feature definition reads:

the application contains and makes use of non-free assets. The most common case is apps using artwork - images, sounds, music, etc - under a non-commercial license.

Would it be possible to rephrase the definition? It would be helpful if the definition would contain general rules and not only relies on examples to explain what it could/should be.

The GNU Free System Distribution Guidelines could be helpful for this. The relevant section in the guidelines is the part about Non-functional Data:

Data that isn't functional, that doesn't do a practical job, is more of an adornment to the system's software than a part of it. Thus, we don't insist on the free license criteria for non-functional data. It can be included in a free system distribution as long as its license gives you permission to copy and redistribute, both for commercial and non-commercial purposes. For example, some game engines released under the GNU GPL have accompanying game information—a fictional world map, game graphics, and so on—released under such a verbatim-distribution license. This kind of data can be part of a free system distribution, even though its license does not qualify as free, because it is non-functional.

My suggestion would be this formulation:

the application contains and makes use of assets that are not allowed to be copied and redistributed for commercial and non-commercial purposes. Assets are non-functional data that doesn't do a practical job, such as artwork - images, sounds, music, etc.

Does this formulation still retain the original meaning of the definition?