saturday06 / VRM-Addon-for-Blender

VRM Importer, Exporter and Utilities for Blender 2.93 to 4.2
https://vrm-addon-for-blender.info
MIT License
1.33k stars 142 forks source link

Request for permission to change the license of @uitcis's Pull Requests #627

Closed saturday06 closed 2 days ago

saturday06 commented 2 weeks ago

@uitcis Hello!

I request permission to change the OSS license for your Pull Request from "MIT" to "MIT or GPL-3.0-or-later multi-license" to meet The Blender Extensions platform's requirement.

Users can choose whether to use the MIT or GPL-3.0-or-later license. The copyright for the code in the Pull Request belongs to the author, @uitcis, so I need to ask for permission to change the license.

After considering it, if possible, I would like to receive a comment granting permission to change it.

saturday06 commented 2 weeks ago

Background

VRM-Addon-for-Blender is distributed on The Blender Extensions platform for Blender 4.2 and later. However, from August 22, 2024, the license for add-ons that can be distributed has been limited to GPL-3.0-or-later. The platform is very convenient, and I want to use it, so I wanted to change the license.

What kind of work is @saturday06 trying to do specifically?

In order to change the license of the source code, it is necessary to obtain consent from the person who wrote the source code (https://www.reddit.com/r/opensource/comments/aq63ow/comment/ege3pp5/). For this reason, I am working to get permission from each contributor. In addition, if consent cannot be obtained, the relevant part of the source code will be excluded or rewritten from scratch.

What is the impact of the license change on the code that @uitcis sent as a pull request?

At present, there will be no impact. In the future, when a new GPL license is issued, there is a minimal possibility of an effect, less than 0.001%. The GNU site currently says the MIT (X11) license is compatible with the GNU GPL license.

https://www.gnu.org/licenses/license-list.en.html#X11License

However, this will not be the case in the future. Because Blender requires a license of GPL-3.0-or-later, it is unclear what the licenses of GPL-4.0 and GPL-99.99, which have not yet been issued, will be. For example, if GPL-4.0 is published as public domain, there is a risk that the MIT license's restriction to "keep the original author's copyright notice" will become invalid.

But if that were to happen, the "compatible" statement on the GNU website would be retracted, and I think there would be a huge fuss involving Blender itself and OSS around the world, so I guess it's a risk that can be ignored.

Why not switch completely to the GPL but instead use "multi-license"?

The main reason is that the impact on users of the license change is less. To be honest, I also wanted to try using a special license, and I also had an excuse to use it.

See also

The information is also summarized in the following issue:

That's all. Thank you for reading this far and for your understanding. Please consider my request.

uitcis commented 2 days ago

当然可以

saturday06 commented 2 days ago

Thank you for your cooperation! I'll get the translation files back to you soon.

uitcis commented 2 days ago

抱歉才看到 我实在是很少看github的通知

saturday06 commented 2 days ago

No problem! Thanks!

saturday06 commented 2 days ago

Released in https://github.com/saturday06/VRM-Addon-for-Blender/releases/tag/v2.29.0 !