Minor copyedits - 4.2.2 software citation

This reduces the length by about 70 words.

The biggest change is to remove what looks like a citation from
`parallel'. I couldn't find the citation in GNU parallel
20161222-1 (Debian/stretch), nor with search engines.
I don't think that the quote is really so useful (even assuming
it's a valid quote from somewhere): citation practices are a mix
between ethics, preparation to convince referees, citing those who
are already cited frequently, and the practicality of searching for
and verifying references against the information for which they
are used. Showing that Maneage makes citation not only easy, but
more or less automatic, bypasses some of the compromises between
practicality and ethics.

1 files changed, 12 insertions, 14 deletions

diff --git a/paper.tex b/paper.tex
index 8bc4205..90efacd 100644
--- a/paper.tex
+++ b/paper.tex
@@ -429,21 +429,19 @@ Therefore, each project has to identify its high-level software in the \inlineco
 \subsubsection{Software citation}
 \label{sec:softwarecitation}
 
-Maneage contains the full list of built software for each project, their versions and their configuration options, but this information is buried deep into each project's source.
-Therefore Maneage also prints a distilled fraction of this information in the project's final report, blended into the narrative, as seen in the Acknowledgments of this paper.
-Furthermore, when the software is associated with a published paper, that paper's Bib\TeX{} entry is also added to the final report and is duly cited with the software's name and version.
-This paper uses basic software without a paper, for software citation examples see \citet{akhlaghi19} and \citet{infante20}.
-
-This is particularly important in the case for research software, where citation is critical to justify continued development.
-One notable example is GNU Parallel \citep{tange18}: it prints the citation information everytime it starts.
-Users can disable the notice, with the \inlinecode{--citation} option and accept to cite its paper, or support its development directly by paying $10000$ euros!
-This is justified by an uncomfortably true statement ``\emph{history has shown that researchers forget to [cite software] if they are not reminded explicitly. ... If you feel the benefit from using GNU Parallel is too small to warrant a citation, then prove that by simply using another tool}''.
-Most software do not resort to such drastic measures, however, proper citation is not only important but also ethical.
-
-Given the increasing number and role of software in research \citep{clement19}, automatic citation (as presented here) is a step forward.
-The necessity and basic elements in software citation are reviewed, inter alia, by \citet{katz14} and \citet{smith16} and CodeMeta and Citation file format (CFF) are projects specifically tailored to expand software citation beyond a Bib\TeX.
+Maneage contains the full list of software that is built, with versions and configuration options, but this information is buried deep into the source.
+Maneage prints a simplified description of this information in the project's final report, blended into the narrative, as in the Acknowledgments of this paper.
+Furthermore, when the software is associated with a published paper, that paper's Bib\TeX{} entry is added to the final report and is duly cited with the software's name and version.
+This paper uses basic software without associated scientific papers. For software citation examples, see \citet{akhlaghi19} and \citet{infante20}.
+
+This is particularly important for research software, where citation is critical to justify continued development.
+GNU Parallel \citep{tange18} prints citation information each time it is run, proposing to either cite the paper or provide substantial financial support, and provides a \inlinecode{--citation} option to disable the notice.
+Most software does not resort to such drastic measures. However, proper citation is not only useful practically, it is also an ethical imperative.
+
+Given the increasing role of software in research \citep{clement19}, automatic citation (as presented here) is a step forward.
+The necessity and basic elements of software citation are reviewed by (e.g.) \citet{katz14} and \citet{smith16}. The CodeMeta and Citation file format (CFF) aim to expand software citation beyond Bib\TeX.
 A very robust approach that also includes archival, is Software Heritage \citep{dicosmo18}.
-They will be tested and enabled in Maneage.
+These will be tested and enabled in Maneage.