Skip to content
This repository was archived by the owner on Oct 10, 2025. It is now read-only.
This repository was archived by the owner on Oct 10, 2025. It is now read-only.

Choose and Add an OSS License #6

@josecelano

Description

@josecelano

Summary

This task is to select and add an open-source license to the repository. The goal is to choose a license that is as free and flexible as possible, allowing users to freely copy, modify, distribute, and use the configuration and scripts to set up their own instances of the Torrust Tracker.

License Options

We should consider a permissive license that places minimal restrictions on reuse. The most common and suitable options are:

  1. The MIT License: A very short and simple permissive license. It essentially lets people do anything they want with the code as long as they include the original copyright and license notice in any copy of the software/source. It is compatible with many other licenses.

  2. The Apache License 2.0: Another excellent permissive license. It is more verbose than MIT and includes an express grant of patent rights from contributors to users. It also requires stating significant changes made to the original software.

  3. The BSD 3-Clause "New" or "Revised" License: Similar to the MIT license, it's a simple permissive license. The main difference is a clause that restricts the use of the names of contributors for endorsement of a derived work without specific permission.

Recommendation

For the stated goal of making the code as free and flexible as possible for users to copy, paste, and adapt, the MIT License is the ideal choice.

  • Simplicity: It is easy for anyone to read and understand.
  • Permissiveness: It provides maximum freedom with minimal requirements (just keeping the copyright notice).
  • Compatibility: It is widely used and compatible with almost every other license, which is beneficial in the open-source ecosystem.

Action Items

  1. Discuss and confirm the choice of the MIT License.
  2. Create a LICENSE file in the root of the repository.
  3. Add the full text of the MIT License to the file, with the copyright year and owner updated.

cc @da2ce7

Metadata

Metadata

Assignees

Labels

LegalLicenses and other Official Documents

Type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions