Commit 29b8bb71 authored by Javier Serrano's avatar Javier Serrano

Added DEP5 method for licensing information

parent 9349ac0c
...@@ -138,12 +138,15 @@ licensing information which will be easily visible to whoever opens them. For ...@@ -138,12 +138,15 @@ licensing information which will be easily visible to whoever opens them. For
file types which do not easily grant that possibility, consider using a separate file types which do not easily grant that possibility, consider using a separate
text file taking as its name the name of the original file with text file taking as its name the name of the original file with
`.license'\footnote{Here we exceptionally use US spelling for the word `licence' `.license'\footnote{Here we exceptionally use US spelling for the word `licence'
in order to be coherent with the REUSE project, which is where we got this in order to be coherent with the REUSE project.} appended to it. So if you
idea. See \href{https://reuse.software/}{https://reuse.software/} for have e.g. a file called `my\_3d\_design.FCStd', you can add another file in the
details.} appended to it. So if you have e.g. a file called same directory called `my\_3d\_design.FCStd.license' which is a text file
`my\_3d\_design.FCStd', you can add another file in the same directory called containing copyright and licensing information. If the number of files in your
`my\_3d\_design.FCStd.license' which is a text file containing copyright and project is large and the `.license' method is deemed too cumbersome, you can
licensing information. centralise all your licensing information in a single text file following the
Debian DEP5 specification. Both the `.license' and the DEP5 methods are
suggested in the REUSE guidelines. See
\href{https://reuse.software/}{https://reuse.software/} for details.
\begin{enumerate}[label=\textbf{\ref*{subsec:your-sources}.6}] \begin{enumerate}[label=\textbf{\ref*{subsec:your-sources}.6}]
\item \textbf{Rule: } include for each source file, either embedded in the file \item \textbf{Rule: } include for each source file, either embedded in the file
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment