New Feature: Sub-licensing

A feature for Sublicensing an open-source product/project(which is under MIT License) whenever we make changes to it and redistribute it. As MIT License Quotes: " the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell"

[merrcury]

A developer uses Open-Source Softwares in two way:

• Firstly, Importing it as a dependency and not changing anything in base file (eg. npm or pip package).
• Secondly, You use that Software as the base of your project and change X% of files according to you then starting redistributing it in some other license or same license.

Here my concern is related to Second Use.

Suppose Someone utilized an MIT program as a base for another project and adjusted about half of the program records. Now, that person wants to redistribute that in GNU GPL v3.

As MIT License Quote: " the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell"

We need sublicensing for this. So, New feature has to deal with:

• A manner advisable for a person to indicate that the program is a subordinate work?
• All the changed file should be mentioned as derivative work.

More Extended Approach:

• If, Someone utilizes a part of two MIT authorized projects in a similar document. So, the Program needs to generate sublicense keeping both things in records.

In this whole scenario, when redistributing in the Same License (say GPL v3), we need basic additions to sublicense but redistributing in the different license(say MIT to GPL v3 or vice versa) will require calculations and complex changes.

[plibither8]

Closing due to inactivity. If and when you work on this, do reopen it 😄