@mattdm Do you mean the cotent of the whole site, or just pages under the /project space?

For the whole website, I could add that to the page footer. If it's just the /project space, I'd advise adding it to those pages on the content side (can help with that).

Hmm, that makes me wonder, should we put LICENSE files in all our repos, too? Right now, most repos don't have one, only the standard user guides (not quick-docs) have a Legal Notice file and they're not in the repo root.

I think we want this globally. Something like:

All Fedora Documentation content available under CC-BY-SA 3.0 or, when specifically noted, under another accepted free and open content license.

Also, yes, we should put license files in all of our repos.

@mattdm Thanks for the clarification, I'll put it in the footer, then!

Done, see the bottom of the page: https://docs.fedoraproject.org/en-US/docs/

@pbokoc Did I get it right you'll take care of the LICENSE files? When that's done, we can close this issue.

@asamalik Yeah, I'll do that and close the issue when I'm done.

Thinking about this further I think I'm going to need some guidance.

• Some docs (the Install Guide, Sysadmin Guide, likely others) are based on Red Hat documentation. They have had this legal notice in them since age immemorial. It does seem to fullfill the attribution part of the license by asserting RH names Fedora as the attribution party - but it's not a license per se, it's a legal notice. Should use this as the LICENSE, or should I put the unmodified text of CC-BY-SA 3.0 as the LICENSE in those repos? If the latter is correct, should I preserve the legal notice as it is (rendered inside the book), or should I move it into another plaintext file in the repo root so it's next to the LICENSE?

• Regarding content that was written from scratch for Fedora (= the legal notice above shouldn't be necessary), can I use the unmodified text of CC-BY-SA 3.0 as LICENSE there?

Can anyone give me an authoritative answer? @mattdm @bex

@pbokoc Maybe we could email legal?