nathank
November 17, 2023, 9:04pm
1
Why does this plugin have the MIT license instead of the usual GPLv2?
The MIT License (MIT)
Copyright (c) 2015 TAN GUO XIANG
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in
all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
show original
I wonder if this should be brought back in line with the rest of the Discourse code.
1 Like
They updated recently the license of all plugins and theme components in favor of MIT, adding any missing ones.
I don’t know the specific reason behind, but I think this change makes sense. The MIT license is simple, straight, and permissive. Less friction and ambiguity. It matches well the Discourse’s open-source philosophy.
3 Likes
