It's less about whether Red Hat/Fedora runs into that restriction, and more of whether someone downstream from us might. Historically, the rule for content was "must be freely redistributable" and this fails that test, because it places a specific restriction on one method of redistribution.

I defer to Red Hat and Fedora Legal though. ;)

~spot

On Thu, Jul 15, 2021 at 4:28 PM Fabio Valentini <decathorpe@gmail.com> wrote:
On Wed, Jul 14, 2021 at 10:31 PM Ben Cotton <bcotton@redhat.com> wrote:
> Let me check with some folks on that. I'd be interested in others'
> opinions, too.
>
> If it were a code license, that's an obvious field of use restriction,
> which means we wouldn't accept it. Historically, we've permitted
> non-modification content licenses. Given the relatively narrow
> restriction here, I'm inclined to except it, too. After all, we *use*
> Unsplash photos around the project all the time: in Fedora Magazine,
> on the Flock website, etc.

Yeah, I know that pictures from unsplash.com are used in tons of
places, but this is the first case I encountered where pictures that
are licensed with their new custom license terms would end up an
actual package - so I figured I should ask here first ... especially
given the usage restrictions (though I don't think that it would apply
to our use case, but obviously IANAL).

Fabio
_______________________________________________
legal mailing list -- legal@lists.fedoraproject.org
To unsubscribe send an email to legal-leave@lists.fedoraproject.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/legal@lists.fedoraproject.org
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure