This is an archive of the discontinued LLVM Phabricator instance.

Clarify that the CoC texts are under a Creative Commons license
ClosedPublic

Authored by kristof.beyls on Apr 12 2023, 6:04 AM.

Diff Detail

Event Timeline

kristof.beyls created this revision.Apr 12 2023, 6:04 AM
Herald added a project: Restricted Project. · View Herald TranscriptApr 12 2023, 6:04 AM
kristof.beyls requested review of this revision.Apr 12 2023, 6:04 AM
Herald added a project: Restricted Project. · View Herald TranscriptApr 12 2023, 6:04 AM
lattner accepted this revision.Apr 12 2023, 2:31 PM
lattner added a subscriber: lattner.

Thank you for driving this Kristof

This revision is now accepted and ready to land.Apr 12 2023, 2:31 PM

llvm-project/LICENSE.txt says:

==============================================================================
Software from third parties included in the LLVM Project:
==============================================================================
The LLVM Project contains third party software which is under different license
terms. All such code will be identified clearly using at least one of two
mechanisms:
1) It will be in a separate directory tree with its own `LICENSE.txt` or
   `LICENSE` file at the top containing the specific license and restrictions
   which apply to that software, or
2) It will contain specific license and restriction terms at the top of every
   file.

Putting a license blob at the end of the file doesn't comply with that.

llvm-project/LICENSE.txt says:

==============================================================================
Software from third parties included in the LLVM Project:
==============================================================================
The LLVM Project contains third party software which is under different license
terms. All such code will be identified clearly using at least one of two
mechanisms:
1) It will be in a separate directory tree with its own `LICENSE.txt` or
   `LICENSE` file at the top containing the specific license and restrictions
   which apply to that software, or
2) It will contain specific license and restriction terms at the top of every
   file.

Putting a license blob at the end of the file doesn't comply with that.

Thanks for pointing that out, @efriedma .
I've now added the license info also at the top of the files as a RestructuredText comment.
I think that's the best way to comply in RestructuredText files with what's written in the top-level LICENSE.txt.

efriedma accepted this revision.Apr 13 2023, 10:41 AM

Sure, that looks fine.

This revision was landed with ongoing or failed builds.Apr 14 2023, 2:09 AM
This revision was automatically updated to reflect the committed changes.