Skip to content

Commit f110e18

Browse files
shanecoughlanshanecoughlan
committed
Updated REUSE 3.0 md, added HTML and DOCX versions
1 parent 119b668 commit f110e18

File tree

4 files changed

+174
-1
lines changed

4 files changed

+174
-1
lines changed

‎General-Compliance-Support-Material/REUSE.software/en/REUSE.software-3.0.docx

19.4 KB
Binary file not shown.

‎General-Compliance-Support-Material/REUSE.software/en/REUSE.software-3.0.html

Lines changed: 173 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,173 @@
1+
<!DOCTYPE html>
2+
<html>
3+
<head>
4+
</head>
5+
6+
<body>
7+
<html>
8+
9+
<h1>REUSE Specification – Version 3.0</h1>
10+
11+
<p>This document is based on REUSE.software, a project launched by FSFE, and redistributed under CC-0 with their kind permission.</p>
12+
13+
14+
<p>This specification defines a standardized method for declaring copyright and
15+
licensing for software projects. The goal of the specification is to have
16+
unambiguous, human- and machine-readable copyright and licensing information for
17+
each individual file in a project. Ideally this information is embedded into
18+
every file, so that the information is preserved when the file is copied and
19+
reused by third parties.</p>
20+
<p>This specification implements <a href="https://tools.ietf.org/html/rfc2119">IETF RFC 2119: Key words for use in RFCs to
21+
Indicate Requirement Levels</a>.</p>
22+
<p>For the revision history of this specification, please see <a href="https://git.fsfe.org/reuse/docs/src/branch/main/CHANGELOG.md">the change
23+
log</a>.</p>
24+
<h2 id="definitions">Definitions</h2>
25+
<p>These are the definitions for some of the terms used in this specification:</p>
26+
<ul>
27+
<li>
28+
<p>REUSE Tool &mdash; helper tool for compliance with this Specification; available
29+
at <a href="https://github.com/fsfe/reuse-tool">https://github.com/fsfe/reuse-tool</a>.</p>
30+
</li>
31+
<li>
32+
<p>Project &mdash; any unit of content that can be associated with a distribution of
33+
software. Typically, a Project is composed of one or more files. Also
34+
sometimes called a package.</p>
35+
</li>
36+
<li>
37+
<p>License File &mdash; a file containing the text of a license.</p>
38+
</li>
39+
<li>
40+
<p>Copyright and Licensing Information &mdash; the information that lists the
41+
copyright holders of a file or work, and describes under which licenses the
42+
file or work is made available.</p>
43+
</li>
44+
<li>
45+
<p>Covered File &mdash; any file in a Project, except for</p>
46+
<ul>
47+
<li>The License Files.</li>
48+
<li>The files belonging to the Project&rsquo;s version control system (example:
49+
<code>.git/</code>).</li>
50+
<li>The files ignored by the version control system (example: Files listed in
51+
<code>.gitignore</code>).</li>
52+
<li>The files in the <code>.reuse/</code> directory in the root of the Project. This
53+
directory MUST contain only files relevant for the operation of the REUSE
54+
Tool.</li>
55+
</ul>
56+
</li>
57+
<li>
58+
<p>SPDX Specification &mdash; SPDX specification, version 2.1; as available on
59+
<a href="https://spdx.org/specifications">https://spdx.org/specifications</a>.</p>
60+
</li>
61+
<li>
62+
<p>SPDX License Identifier &mdash; SPDX short-form identifier, as defined in SPDX
63+
Specification. See also <a href="https://spdx.org/ids">https://spdx.org/ids</a> for a short introduction and
64+
examples.</p>
65+
</li>
66+
<li>
67+
<p>SPDX License Expression &mdash; as defined in SPDX Specification, Appendix IV, at <a href="https://spdx.org/spdx-specification-21-web-version#h.jxpfx0ykyb60">https://spdx.org/spdx-specification-21-web-version#h.jxpfx0ykyb60</a>.</p>
68+
</li>
69+
<li>
70+
<p>SPDX License List &mdash; a list of commonly found licenses and exceptions; as
71+
available on <a href="https://spdx.org/licenses/">https://spdx.org/licenses/</a>.</p>
72+
</li>
73+
<li>
74+
<p>DEP5 &mdash; <a href="https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/">Machine-readable <code>debian/copyright</code> file, Version
75+
1.0</a>.
76+
Where the REUSE Specification and DEP5 state different things, the REUSE
77+
Specification takes precedence. Specifically in the case of the <code>Copyright</code>
78+
and <code>License</code> tags.</p>
79+
</li>
80+
</ul>
81+
<h2 id="license-files">License Files</h2>
82+
<p>A Project MUST include a License File for every license under which Covered
83+
Files are licensed.</p>
84+
<p>Each License File MUST be placed in the <code>LICENSES/</code> directory in the root of
85+
the Project. The name of the License File MUST be the SPDX License Identifier of the
86+
license followed by an appropriate file extension (example:
87+
<code>LICENSES/GPL-3.0-or-later.txt</code>). The License File MUST be in plain text format.</p>
88+
<p>If a license does not exist in the SPDX License List, its SPDX License Identifier
89+
MUST be <code>LicenseRef-[idstring]</code> as defined by the SPDX Specification, Section 6 available at <a href="https://spdx.org/spdx-specification-21-web-version#h.1v1yuxt">https://spdx.org/spdx-specification-21-web-version#h.1v1yuxt</a>.</p>
90+
<p>A Project MUST NOT include License Files for licenses under which none of the
91+
files in the Project are licensed.</p>
92+
<p>Everything that applies to licenses in this section also applies to license
93+
exceptions, with the exception that it is NOT possible to have a license
94+
exception that does not exist in the SPDX License List.</p>
95+
<p>For avoidance of doubt, in practice this means that for every license and exception
96+
that is part of any SPDX License Expression in any Copyright and Licensing Information
97+
associated with any Covered File, there MUST exist a License File as defined in this section.</p>
98+
<h2 id="copyright-and-licensing-information">Copyright and Licensing Information</h2>
99+
<p>Each Covered File MUST have Copyright and Licensing Information associated with
100+
it. There are two ways to associate Copyright and Licensing Information with a
101+
file.</p>
102+
<h3 id="comment-headers">Comment headers</h3>
103+
<p>To implement this method, each plain text file that can contain comments MUST
104+
contain comments at the top of the file (comment header) that declare that
105+
file&rsquo;s Copyright and Licensing Information.</p>
106+
<p>If a file is not a plain text file or does not permit the inclusion of
107+
comments, the comment header that declares the file&rsquo;s Copyright and Licensing
108+
Information SHOULD be in an adjacent file of the same name with the
109+
additional extension <code>.license</code> (example: <code>cat.jpg.license</code> if the original
110+
file is <code>cat.jpg</code>).</p>
111+
<p>The comment header MUST contain one or more <code>SPDX-FileCopyrightText</code> tags, and one or
112+
more <code>SPDX-License-Identifier</code> tags. A tag is followed by a colon, followed by
113+
a text value, and terminated by a newline.</p>
114+
<p>The <code>SPDX-FileCopyrightText</code> tag MUST be followed by a copyright notice.</p>
115+
<p>Instead of the <code>SPDX-FileCopyrightText</code> tag, the symbol <code>©</code>, or the word <code>Copyright</code> MAY
116+
be used, in which case a colon is not needed.</p>
117+
<p>The <code>SPDX-License-Identifier</code> tag MUST be followed by a valid SPDX License
118+
Expression describing the licensing of the file (example:
119+
<code>SPDX-License-Identifier: GPL-3.0-or-later OR Apache-2.0</code>). If separate sections
120+
of the file are licensed differently, a different <code>SPDX-License-Identifier</code> tag
121+
MUST be included for each section.</p>
122+
<p>An example of a comment header:</p>
123+
<pre tabindex="0"><code># SPDX-FileCopyrightText: 2016, 2018-2019 Jane Doe &lt;[email protected]&gt;
124+
# SPDX-FileCopyrightText: 2019 Example Company
125+
#
126+
# SPDX-License-Identifier: GPL-3.0-or-later
127+
</code></pre><h3 id="dep5">DEP5</h3>
128+
<p>Alternatively, Copyright and Licensing Information MAY be associated with a
129+
file through a DEP5 file. The intended use case of this method is large
130+
directories where including a comment header in each file (or in <code>.license</code>
131+
companion files) is impossible or undesirable.</p>
132+
<p>The DEP5 file MUST be named <code>dep5</code> and stored in the <code>.reuse/</code> directory in the
133+
root of the Project (i.e. <code>.reuse/dep5</code>).</p>
134+
<p>The <code>License</code> tag MUST be followed by a valid SPDX License Expression describing
135+
the licensing of the associated files.</p>
136+
<p>The <code>Copyright</code> tag MUST be followed by a copyright notice.</p>
137+
<p>An example of a DEP5 file:</p>
138+
<pre tabindex="0"><code>Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
139+
Upstream-Name: Project
140+
Upstream-Contact: Jane Doe &lt;[email protected]&gt;
141+
Source: https://example.com/jane/project
142+
143+
Files: po/*
144+
Copyright: 2019 Translation Company
145+
License: GPL-3.0-or-later
146+
</code></pre><h2 id="format-of-copyright-notices">Format of copyright notices</h2>
147+
<p>A copyright notice MUST be prefixed by a tag, symbol or word denoting a
148+
copyright notice as described in this specification.</p>
149+
<p>The copyright notice MUST contain the name of the copyright holder. The
150+
copyright notice SHOULD contain the year of publication and the contact address
151+
of the copyright holder. The order of these items SHOULD be: year, name, contact
152+
address.</p>
153+
<p>The year of publication MAY be a single year, multiple years, or a span of
154+
years.</p>
155+
<p>The copyright holder MAY be an individual, list of individuals, group, legal
156+
entity, or any other descriptor by which one can easily identify the
157+
copyright holder(s).</p>
158+
<p>Any contact address SHOULD be in between angle brackets.</p>
159+
<p>Examples of valid copyright notices:</p>
160+
<pre tabindex="0"><code>SPDX-FileCopyrightText: 2019 Jane Doe &lt;[email protected]&gt;
161+
SPDX-FileCopyrightText: © 2019 John Doe &lt;[email protected]&gt;
162+
© Example Corporation &lt;https://corp.example.com&gt;
163+
Copyright 2016, 2018-2019 Joe Anybody
164+
Copyright (c) Alice
165+
</code></pre>
166+
</div>
167+
168+
</div>
169+
</div>
170+
</div>
171+
172+
</html>
173+
</body>

‎General-Compliance-Support-Material/REUSE.software/en/REUSE.software-3.0.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
# REUSE.software
22

3-
This document is based on reuse.software, a project launched by FSFE, and redistributed under CC-0 with their kind permission.
3+
This document is based on REUSE.software, a project launched by FSFE, and redistributed under CC-0 with their kind permission.
44

55
---
66
# SPDX-FileCopyrightText: 2019 Free Software Foundation Europe e.V.

‎General-Compliance-Support-Material/REUSE.software/en/~$USE.software-3.0.docx

162 Bytes
Binary file not shown.

0 commit comments

Comments
 (0)