Open Studio384 opened 9 years ago
You have my permission.
I give my permission for this move, to the future!
You have my permission
You have my permission
Thank you guys!
You have my permission!
And my axe permission, too.
One thing though: AFAIK the POMO library handling the gettext part is licensed under GPLv2. This could be a problem. Author is @LeoColomb.
Yep, from WordPress license. I would prefer to switch to MIT License, but sublicensing is not allowed by GPLv2.
You have my permission.
A MIT project can use a GPLv2 dependency, no?
Don't think so. I'll let anyone with more knowledge on this confirm, but GPL is more restrictive than MIT, a project embedding GPL license code has to be distributed under GPL too.
There might be some rewriting to do on that part.
According to the FSF, MIT is compatible, so it should be legal to do. On the other hand, more MIT the better... So if you've time... I would say: have fun.
MIT is GPL-compatible indeed, but it just means MIT licensed code can be included in a GPL licensed project; I think the opposite is not true: a MIT licensed project including GPL code can't be full MIT licensed. There's an interesting discussion on StackOverflow about that point.
That being said, I'll try to find some time to work on fixing this.
As I understand it, you can release a project under the MIT license with GPL dependencies as long as you release every revision of this code (because GPL requires that). Not sure if that will require the package itself to be GPL too. Either way, as we're rewriting most part of the code anyway, not much GPL will be left over and the parts that still are GPL, can be replaced.
To bad there is no concluding text on this subject.
Oh, I'm still listed. :)
You have my permission to release my code, if anything else is left (grin), under MIT license.
@oldhobbyist - Uhm, sure there is, prety much the whole template system is based on your code. Based works also need to request permission. :)
Well, that leaves 2.
:+1:
Whatever I've contributed I consider inconsequential and not capable of having any copyright to begin with, so personally, you didn't need to ask.
but for legal reasons I say yes; one of the other projects I work with uses MIT too.
Well, we need to ask permission for every single line and otherwise rewrite it (through most of it will)...
Anyway, thanks! Now @oppdelta, only you're vote is required to MIT-isez all changes made since FluxBB 1.4.9.
I missed the email for this. Sorry for keeping you waiting but you have my permission. If you haven't moved on by now. Again, sorry.
No worry, you're in time. Still didn't get there... :)
With Luna 2.0, we'll move to a new license: MIT (we now use GPLv3). For this, major parts of the code will have to be rewritten. This already happens in #861, #881, #883, #1297 and #1299. However, we would like to ask permission to rerelease the code of our contributors under the MIT license (it makes it easier for us). Otherwise, we will scrap the contributed code and start over for these parts.
Hereby, I ask permission from
to rerelease their respective contributions under the MIT license. Note that this doesn't mean that it your code will still be part of Luna in later releases, I'm just preparing in case it is. :) Another note is that all contributions made to Luna as of July 22, 2014 are already permitted to be released under the MIT-license as noted by our contribution documentation.
For all contributors mentioned above that apply to the notes as mentioned above, I request your permission to release your contribution(s) to the Luna-codebase prior to July 22, 2014 or the code that was applied to ModernBB and earlier under the MIT license for Luna 2.0 and onwards. In case your code already falls under the rule mentioned above, you can also still give permission, for the fun of it. In case you do not give permission, please mention it here too.