We're sorry but this page doesn't work properly without JavaScript enabled. Please enable it to continue.
Feedback

REUSE: Best practices for declaring copyright and licenses

Formale Metadaten

Titel
REUSE: Best practices for declaring copyright and licenses
Serientitel
Anzahl der Teile
637
Autor
Mitwirkende
N. N.
Lizenz
CC-Namensnennung 2.0 Belgien:
Sie dürfen das Werk bzw. den Inhalt zu jedem legalen Zweck nutzen, verändern und in unveränderter oder veränderter Form vervielfältigen, verbreiten und öffentlich zugänglich machen, sofern Sie den Namen des Autors/Rechteinhabers in der von ihm festgelegten Weise nennen.
Identifikatoren
Herausgeber
Erscheinungsjahr
Sprache

Inhaltliche Metadaten

Fachgebiet
Genre
Abstract
Why is it so hard to detect the licensing and copyright information of source code? Because it is a tedious and often confusing task for developers to provide this information. The REUSE project changes that! With three simple steps, it makes adding and reading licensing and copyright information easy for both humans and machines. This presentation will guide you through the REUSE best practices and presents how to make clear licensing simple. In 2017, the FSFE started the REUSE initiative. The main goal is to make it easier for developers to declare the licensing and copyright situation for their code. Especially in common scenarios where a repository contains code from various sources under different licenses with multiple copyright holders, it often becomes complex for everyone who wants to legally reuse code. Therefore, REUSE provides best practices that aim to be compatible with already existing recommendations and still cover also complex projects and their edge cases. The result is that for a REUSE compatible repository, every single file in some way carries information about its license and copyright holder(s), with the full license text(s) available. To make adoption as easy as possible, REUSE offers tools and accompanying documentation. Thanks to this, we already see hundreds of projects being REUSE compliant already. The more projects follow the best practices, the easier developers can reuse their code safely and thereby contribute to a system in which you do not need a lawyer to license your code.