Apache-2.0 license clarification

#7
by Araki - opened

The model includes an extensive end user license agreement Model Acceptable Use Policy. It applies to the weights themselves, not only to the API access.

It must be carried over to the finetunes and possibly generated synthetic data too, making it so the AUP should be preserved as a mandatory addendum to Apache-2.0 when disturbing the model.

the conditions under which you may access and use the model weights, parameters, and associated materials, and any modified version (the “Model Materials”)

I believe either there should be a more explicit clarification that additional terms apply to this model for compliance purposes (e.g. a "NOTICE" file the Apache-2.0 license supports), or it shouldn't have an Apache-2.0 license at all, as in the current state it's obviously out of sync from being a FOSS project an Apache-2.0 license might wrongly imply.

Araki changed discussion title from The model is not Apache-2.0 licensed to Apache-2.0 license clarification

Sign up or log in to comment