(Sub)license under AGPL #59

Closed
opened 2021-04-20 22:13:41 +00:00 by projectmoon · 1 comment
Owner

The MIT license allows sublicensing. It is a desirable goal of this project for the code to preserve user freedom as much as possible, and thus, use the AGPL license. Conceptually, this is a very simple matter to solve. Any code we have written can be licensed as AGPL directly. Code that remains from the original project, or modified versions of it in this project, remain under the MIT license as well as the AGPL sublicense.

Requirements:

  • Add AGPL License file as LICENSE.AGPL, rename existing LICENSE to LICENSE.MIT.
  • Add a license header to every source file, indicating it is under the AGPL license.
  • For any file containing the original MIT code, it must also be made clear that portions of the file are also subject to the MIT license. We need to identify those files.

Files subject, wholly or in part, to the MIT license:

  • Anything on the legacy side of the "legacy boundary" for parsing (AKA the Nom-based parsing code).
  • The command handlers are based on the Rust Matrix SDK example code, which is MIT licensed.
  • The command parsing code, which generates the dyn Command boxes.
  • Some of the commands themselves?
The MIT license allows sublicensing. It is a desirable goal of this project for the code to preserve user freedom as much as possible, and thus, use the AGPL license. Conceptually, this is a very simple matter to solve. Any code we have written can be licensed as AGPL directly. Code that remains from the original project, or modified versions of it in this project, remain under the MIT license as well as the AGPL sublicense. Requirements: - [X] Add AGPL License file as LICENSE.AGPL, rename existing LICENSE to LICENSE.MIT. - [X] Add a license header to every source file, indicating it is under the AGPL license. - [X] For any file containing the original MIT code, it must also be made clear that portions of the file are also subject to the MIT license. We need to identify those files. Files subject, wholly or in part, to the MIT license: - Anything on the legacy side of the "legacy boundary" for parsing (AKA the Nom-based parsing code). - The command handlers are based on the Rust Matrix SDK example code, which is MIT licensed. - The command parsing code, which generates the `dyn Command` boxes. - Some of the commands themselves?
Author
Owner

Updated license file with text of both licenses and an explanation of the sublicensing.

For files that are partially or wholly governed by the MIT license, added a header to them.

Also changed the project name, because I can.

Updated license file with text of both licenses and an explanation of the sublicensing. For files that are partially or wholly governed by the MIT license, added a header to them. Also changed the project name, because I can.
Sign in to join this conversation.
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: projectmoon/tenebrous-dicebot#59
No description provided.