I have a followup question to a gitlab issue [1]. There are 3 files in the SMuFL repository [2], classes.json, glyphnames.json, and ranges.json, that are currently bundled in the mscore package. It would be advantageous to break those files out into a separate package for consumption by other SMuFL-aware software. The determination in [1] is that the presence of those files does not require a change to the mscore package License field. What about if they are in their own package? What would the License field of that package be?
References: [1] https://gitlab.com/fedora/legal/fedora-license-data/-/issues/170 [2] https://github.com/w3c/smufl
On Wed, Mar 15, 2023 at 1:51 PM Jerry James loganjerry@gmail.com wrote:
I have a followup question to a gitlab issue [1]. There are 3 files in the SMuFL repository [2], classes.json, glyphnames.json, and ranges.json, that are currently bundled in the mscore package. It would be advantageous to break those files out into a separate package for consumption by other SMuFL-aware software. The determination in [1] is that the presence of those files does not require a change to the mscore package License field. What about if they are in their own package? What would the License field of that package be?
Hmm. I will follow up on this in the original issue. I was hoping to make the problem go away but that may not be possible.
Richard