From 2961116a7319a961c7223f5997998f36110dd5f2 Mon Sep 17 00:00:00 2001 From: Robin Schneider Date: Sun, 14 Mar 2021 16:06:29 +0100 Subject: [PATCH] Add section to doclicense what license to use and REUSE spec Related to: #72 --- doclicense/doclicense.dtx | 20 ++++++++++++++++++++ 1 file changed, 20 insertions(+) diff --git a/doclicense/doclicense.dtx b/doclicense/doclicense.dtx index 5932dab..e70852a 100644 --- a/doclicense/doclicense.dtx +++ b/doclicense/doclicense.dtx @@ -173,6 +173,26 @@ corresponds to \PackageName\nobreakspace\fileversion, dated \printdateTeX{\filed % image of the license. Currently, only \doclicenseLongType is supported but this % package is designed to handle all kinds of licenses. See \nameref{sec:contributing}. % +% \section{What license to choose for the document?} +% +% The list of available licenses is long (see +% \href{https://spdx.org/licenses/}{SPDX License List}). Only a (small) subset +% of them are a good choice for documentation. The \doclicenseLongType family +% seem to be a common choice as contributions to this package have shown. This +% package was translated to 15+ languages but no other license families have +% been added yet. With that, a link to +% \href{https://creativecommons.org/choose/}{Creative Commons: Choose a +% License} is probably justified if you have not done that already. +% +% That clarifies the question under which license you want to put the document +% under, but in practice it might not be as easy as that. +% Under what license are the artifact (image/figure/table/source code listing) +% you are including? If you created them yourself the answer is easy. If not, +% it would probably be useful to track such metadata along with the files. +% For this, the \href{REUSE Specificatio}{https://reuse.software/} can be used. +% \PackageName{} might integrate with the REUSE Specification to automate +% proper attribution of artifacts at a later point. +% % \section{Usage} % Just load the package by placing something like this: %