https://reuse.software/ Recent content on REUSE Hugo en https://reuse.software/booster-confirm/ Mon, 01 Jan 0001 00:00:00 +0000 https://reuse.software/booster-confirm/ You have almost completed the process of registering your project for the REUSE Booster programme. Please take a look in your email inbox to confirm your address. In this email, you will also be able to check all entered information again. If you do not receive an email from us in the next 15 minutes, please also check your spam folder. Thank you! https://reuse.software/comparison/ Mon, 01 Jan 0001 00:00:00 +0000 https://reuse.software/comparison/ It is easy to get confused by the multitude of initiatives and tools that help with software license compliance. Provided below is a short and incomplete overview of some noteworthy projects. REUSE does not intend to replace, but rather complement them. We try to solve unclear and missing license and copyright information at the very source. We empower developers to ensure proper and exhaustive licensing of their project. SPDX is the rock upon which REUSE is built. https://reuse.software/faq/ Mon, 01 Jan 0001 00:00:00 +0000 https://reuse.software/faq/ This page lists common questions and their answers when dealing with licensing and copyright, and with the adoption of REUSE specifically. Please note that nothing here is legal advice. Table of Contents General I am short on time. Can you give me the quickest possible summary? 1. Choose and provide licenses 2. Add copyright and licensing information to each file 3. Confirm REUSE compliance What is SPDX? Copyright What is copyright? https://reuse.software/booster/ Mon, 01 Jan 0001 00:00:00 +0000 https://reuse.software/booster/ Implementing the REUSE principles is easy. Even without legal knowledge, project maintainers can massively improve the licensing and copyright declaration of their software. But sometimes, everyone needs some extra help. All you have to do is ask your friends. That is why we assist Free Software projects with making their repositories REUSE compliant! That will ensure that your project ships one or multiple licenses in a standardised location and form, and that each file is equipped with information about its license and copyright. https://reuse.software/dev/ Mon, 01 Jan 0001 00:00:00 +0000 https://reuse.software/dev/ Licensing should be easy for developers. We provide several tools and services to allow you to concentrate on coding. Contents: Helper tool, example repositories, REUSE API, CI/CD workflows REUSE Tool The REUSE tool assists with achieving and confirming REUSE compliance. It downloads the full license texts, adds copyright and license information to file headers, and contains a linter to identify problems. Eventually, you can generate a software bill of materials. https://reuse.software/resources/ Mon, 01 Jan 0001 00:00:00 +0000 https://reuse.software/resources/ You have already explored parts of the REUSE universe and would like to go one step further? Read more background, get in touch with the community and help us spread the word! Get in touch Just like Free Software, the REUSE project is based on its community and the people who support and adopt it. Become part of it by joining the mailing list to get to know other users, and influence the way REUSE evolves. https://reuse.software/booster-success/ Mon, 01 Jan 0001 00:00:00 +0000 https://reuse.software/booster-success/ You have successfully completed the process of registering your project for the REUSE Booster programme! After the deadline we will evaluate all registrations in a jury. You will hear back from us in any case. But that does not stop you to have a closer look at REUSE already and make the first steps to adopt the best practices! Check out the tutorial and FAQ, or more advanced options for developers like the helper tool, API, pre-commit hooks and CI snippets. https://reuse.software/spec-1.2/ Mon, 01 Jan 0001 00:00:00 +0000 https://reuse.software/spec-1.2/ 1. Provide the exact text of each license used Free and open source software licenses are standardised and have standard texts. Regardless of which license you use, you should include the license text in your project. You should also include the license text of any code which may be under a different license, and it’s important you do not change the license text on other software you include. If your project only includes code licensed under a single license, you may provide the text of this license in a file in the top level directory of your repository with the name LICENSE, LICENCE or COPYING (you may attach some suffix to the filename as well, such as LICENSE. https://reuse.software/spec-2.0/ Mon, 01 Jan 0001 00:00:00 +0000 https://reuse.software/spec-2.0/ 1. Provide the exact text of each license used Free and open source software licenses are standardised and have standard texts. Regardless of which license you use, you should include the license text in your project. You must include all licenses which are used in your project, and you must never change any license texts even if they are very similar to existing ones. The easiest way to make sure that you provide an unchanged license is by copying it verbatim from this repository of licenses maintained by the SPDX Workgroup. https://reuse.software/spec/ Mon, 01 Jan 0001 00:00:00 +0000 https://reuse.software/spec/ https://reuse.software/spec-3.0/ Mon, 01 Jan 0001 00:00:00 +0000 https://reuse.software/spec-3.0/ This specification defines a standardized method for declaring copyright and licensing for software projects. The goal of the specification is to have unambiguous, human- and machine-readable copyright and licensing information for each individual file in a project. Ideally this information is embedded into every file, so that the information is preserved when the file is copied and reused by third parties. This specification implements IETF RFC 2119: Key words for use in RFCs to Indicate Requirement Levels. https://reuse.software/spec-3.2/ Mon, 01 Jan 0001 00:00:00 +0000 https://reuse.software/spec-3.2/ This specification defines a standardised method for declaring copyright and licensing for software projects. The goal of the specification is to have comprehensive, unambiguous, human- and machine-readable copyright and licensing information for each individual file in a project. Ideally this information is embedded into every file, so that the information is preserved when the file is copied and reused by third parties. This specification implements IETF RFC 2119: Key words for use in RFCs to Indicate Requirement Levels. https://reuse.software/spec-3.3/ Mon, 01 Jan 0001 00:00:00 +0000 https://reuse.software/spec-3.3/ This specification defines a standardised method for declaring copyright and licensing for software projects. The goal of the specification is to have comprehensive, unambiguous, human- and machine-readable copyright and licensing information for each individual file in a project. Ideally this information is embedded into every file, so that the information is preserved when the file is copied and reused by third parties. This specification implements IETF RFC 2119: Key words for use in RFCs to Indicate Requirement Levels. https://reuse.software/specifications/ Mon, 01 Jan 0001 00:00:00 +0000 https://reuse.software/specifications/ These are the versions of the specification, listed from new to old: Version 3.3. Version 3.2. Version 3.0. Historically, the specification was less formal, and titled ‘REUSE Practices’: Version 2.0. Version 1.2. The most current specification can always be found at https://reuse.software/spec/. https://reuse.software/supporters/ Mon, 01 Jan 0001 00:00:00 +0000 https://reuse.software/supporters/ We are grateful for everyone who supports REUSE. The ever-growing ecosystem of specification, documentation, helper tool, API and a lot more demands time and funds. Thanks to volunteers, cooperating organisations and projects, as well as corporate sponsors, REUSE can constantly evolve and improve. Users and adopters A project that follows the REUSE best practices makes its licensing and copyright situation transparent, ensures that third-party code is attributed correctly, and makes it easily re-usable for other developers. https://reuse.software/tutorial/ Mon, 01 Jan 0001 00:00:00 +0000 https://reuse.software/tutorial/ This tutorial explains the basics of making a software project REUSE-compliant. The goal is to easily, comprehensively, and unambiguously declare your copyright and licensing in a way that is machine-readable. By the end of this tutorial, you will understand the three fundamental steps of REUSE: Choose and provide licenses Add copyright and license information to each file Confirm REUSE compliance For the purpose of this tutorial, we will assume that the directory of your project looks like this: