Source files of fsfe.org, pdfreaders.org, freeyourandroid.org, ilovefs.org, drm.info, and test.fsfe.org. Contribute: https://fsfe.org/contribute/web/ https://fsfe.org
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 

73 lines
2.7 KiB

<?xml version="1.0" encoding="UTF-8"?>
<html newsdate="2017-12-19">
<version>1</version>
<head>
<title>FSFE releases refreshed set of REUSE practices and a tool to help developers comply</title>
</head>
<body>
<h1>FSFE releases refreshed set of REUSE practices and a tool to help developers comply</h1>
<p>
The REUSE Initiative has received an updated set of practices that simplify
the process of declaring copyright and licence information. To help
facilitate developers with updating their projects, the FSFE has also
published a tool that verifies whether a project is compliant.
</p>
<div class="captioned" style="width:80%; margin: 1.5em auto;">
<a href="https://reuse.software/">
<img src="https://pics.fsfe.org/uploads/big/a59a3b49fcf6734b8647e05adb2f1612.png" />
</a>
</div>
<p>
Copyright and licensing is difficult. Finding out the exact copyright and
licence of a piece of code is often times more difficult than it should be.
Missing or scattered licence information makes it very labour-intensive to
verify whether you can legally use a piece of code. For a thorough legal
review, you have to manually check every file for licence information, and
every file has a different way of declaring its copyright and licence.
</p>
<p>
But what if we could automate this? That is what
the <a href="https://reuse.software/">REUSE Initiative</a> postulates. By
defining a standard for copyright and licence declaration, the legal process
of complying with licences becomes a lot easier. Simply include a standard,
computer-readable header tag to every file, and extracting the licence
information should be as simple as running a parser.
</p>
<p>
Earlier in October, we released a set of practices towards that end. Now,
we have <a href="https://reuse.software/practices/2.0/">updated those
practices</a> to streamline them some. To accompany the streamlined
changes, we have published
<a href="https://git.fsfe.org/reuse/reuse">a tool</a> for developers to
check whether they comply with our recommendations.
</p>
<p>
The primary change between the old version and the new is that you no longer
need to declare two tags; only one. 'License-Filename' has been deprecated,
and instead its functionality has been rolled into
'SPDX-License-Identifier'. This is more in line with existing projects, and
is less effort to boot.
</p>
<p>
Complying with the REUSE recommendations is very simple. Why not give it a
spin? We would love to hear from you.
</p>
</body>
<tags>
<tag key="front-page"/>
<tag key="reuse"/>
</tags>
<author id="carmenbianca" />
</html>