Clarify that the CoC texts are under a Creative Commons license

[lattner]

Thank you for driving this Kristof

[efriedma]

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.

[kristof.beyls]

In D148121#4263216, @efriedma wrote:

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]

Sure, that looks fine.

llvm/docs/CodeOfConduct.rst

+..
+   This work is licensed under a Creative Commons Attribution 3.0 Unported License.
+   SPDX-License-Identifier: CC-BY-3.0
+
 ==============================
 LLVM Community Code of Conduct
 ==============================
 
 The LLVM community has always worked to be a welcoming and respectful
 community, and we want to ensure that doesn't change as we grow and evolve. To
 that end, we have a few ground rules that we ask people to adhere to:
 

 For details about what a Transparency Report is and what it contains, please see the :doc:`Response Guide<ResponseGuide>`.
 
 Questions?
 ==========
 
 If you have questions, please feel free to contact the LLVM Foundation Code of
 Conduct Committee by emailing [e-mail].
 
+Thanks!
+=======
+
+This text is based on the `Django Project`_ Code of Conduct, which is in turn
+based on wording from the `Speak Up! project`_.
+
+License
+=======
 
-(This text is based on the `Django Project`_ Code of Conduct, which is in turn
-based on wording from the `Speak Up! project`_.)
+All content on this page is licensed under a `Creative Commons Attribution 3.0
+Unported License`_.
 
 .. _Django Project: https://www.djangoproject.com/conduct/
 .. _Speak Up! project: http://speakup.io/coc.html
 .. _sexual and gender-based violence:
 .. _hate crimes: https://hatecrime.osce.org
 .. _hate speech: https://www.un.org/en/genocideprevention/documents/UN%20Strategy%20and%20Plan%20of%20Action%20on%20Hate%20Speech%2018%20June%20SYNOPSIS.pdf
+.. _Creative Commons Attribution 3.0 Unported License: http://creativecommons.org/licenses/by/3.0/

llvm/docs/ReportingGuide.rst

+..
+   This work is licensed under a Creative Commons Attribution 3.0 Unported License.
+   SPDX-License-Identifier: CC-BY-3.0
+
 =================================
 LLVM CoC Incident Reporting Guide
 =================================
 
 First of all, please do not feel like you may be a burden to us by reporting
 incidents. We consider reports an opportunity for us to act: by knowing about
 an incident, we can act on it if appropriate, and reduce continuation of
 problematic behavior.  If we don't know, we can't learn or take any appropriate

 
 Once a report is filed, the Code of Conduct committee will handle the review
 and follow up according to the procedures in the :doc:`Response Guide
 <ResponseGuide>`. 
 
 
 Thanks!
 =======
+
 This guide was created and inspired by the following: the `Django Project`_,
 `Carpentries Response Guide`_, and the `Write The Docs Response Guide`_.
 
+License
+=======
+
+All content on this page is licensed under a `Creative Commons Attribution 3.0
+Unported License`_.
+
+
 .. _Django Project: https://www.djangoproject.com/conduct/
 .. _Carpentries Response Guide: https://docs.carpentries.org/topic_folders/policies/enforcement-guidelines.html
 .. _Write The Docs Response Guide: https://www.writethedocs.org/code-of-conduct/#guidelines-for-reporting-incidents
+.. _Creative Commons Attribution 3.0 Unported License: http://creativecommons.org/licenses/by/3.0/
 

llvm/docs/ResponseGuide.rst

+..
+   This work is licensed under a Creative Commons Attribution 3.0 Unported License.
+   SPDX-License-Identifier: CC-BY-3.0
+
 ===============
 Response Guide
 ===============
 
 This is a :doc:`Code of Conduct<CodeOfConduct>` (CoC) incident response guide
 used by the Code of Conduct Committee and LLVM event organizers.
 
 Code of Conduct Committee

 A transparency report consists of 2 parts:
 
 * An overview of the reports received, and resolutions.
 * A more detailed summary of each reported incident and the resolution while
   maintaining confidentiality.
 
 These reports will be published on the LLVM website.
 
+Thanks!
+=======
+
 
 This guide was created and inspired by the following: the `Django Project`_,
 `Carpentries Response Guide`_, and the `Write The Docs Response Guide`_.
 
+License
+=======
+
+All content on this page is licensed under a `Creative Commons Attribution 3.0
+Unported License`_.
+
+
 .. _Django Project: https://www.djangoproject.com/conduct/
 .. _Carpentries Response Guide: https://docs.carpentries.org/topic_folders/policies/enforcement-guidelines.html
 .. _Write The Docs Response Guide: https://www.writethedocs.org/code-of-conduct/#guidelines-for-reporting-incidents
+.. _Creative Commons Attribution 3.0 Unported License: http://creativecommons.org/licenses/by/3.0/