The LICENSE file is currently a stand in file with details of a different project.
You also may not be able to use the MIT license for your whole distribution because your plugin.js is based on the code from ckeditor which as linked (https://ckeditor.com/legal/ckeditor-oss-license/) is licensed under the GPLv2 and can not be re-licensed as MIT.
If the plugin was from CK4,then it's GPLv2, LGPLv2 or MPL 1.1; non of which can be downgraded to MIT.
I believe you can keep the plugin.js as GPLv2 and the rest of your code as MIT, but the whole project (as defined in setup.py) should be labeled as GPLv2 as it's the license with the highest precedence.
But I am not a lawyer, you could also ask at the Software Freedom Law Center to see if this is correct.
The LICENSE file is currently a stand in file with details of a different project.
You also may not be able to use the MIT license for your whole distribution because your plugin.js is based on the code from ckeditor which as linked (https://ckeditor.com/legal/ckeditor-oss-license/) is licensed under the GPLv2 and can not be re-licensed as MIT.
If the plugin was from CK4,then it's GPLv2, LGPLv2 or MPL 1.1; non of which can be downgraded to MIT.
I believe you can keep the plugin.js as GPLv2 and the rest of your code as MIT, but the whole project (as defined in setup.py) should be labeled as GPLv2 as it's the license with the highest precedence.
But I am not a lawyer, you could also ask at the Software Freedom Law Center to see if this is correct.