You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Greetings! This library is excellent and I've been happily using it on Windows for a while. However, I would like to have it compiled and used on a Linux environment, but the license (MS-LPL) doesn't allow that freedom. If it makes no difference to you, can you change the license to a very similar, but more permissive one such as MS-PL?
@EricWhiteDev, it is not difficult if you are the only author.
So, you control the license of your own code, and if you change the license (or simply give a written permission to UNIT6-open to reuse the code under the terms of MIT or whatever), then it's up to the current maintainers to relicense their parts of the code.
A formal permission from every of the contributors would be required to relicense their contributions, and since GitHub only shows a handful of contributors, it's not impossible.
Activity
alexanium-dev commentedon Jun 7, 2018
Probably we should call @AIVolkov
AIVolkov commentedon Jun 8, 2018
Guys, I'm really don't know what to do.
As long as I remember MS-PL license got from Eric White and MSDN ToS.
This library is based on this code example: https://msdn.microsoft.com/en-us/magazine/ee532473.aspx
Did anyone have any ideas about this?
alexanium-dev commentedon Jun 8, 2018
@EricWhiteDev, would you mind to comment on this issue? What should we do to be able to change the license from MS-LPL to MS-PL?
EricWhiteDev commentedon Jun 8, 2018
Afaik, it is extremely difficult to change open-source licenses, but I have no experience with this.
AuthorProxy commentedon Jun 9, 2018
How I can use it on Linux?
ForNeVeR commentedon Jul 19, 2023
@EricWhiteDev, it is not difficult if you are the only author.
So, you control the license of your own code, and if you change the license (or simply give a written permission to UNIT6-open to reuse the code under the terms of MIT or whatever), then it's up to the current maintainers to relicense their parts of the code.
A formal permission from every of the contributors would be required to relicense their contributions, and since GitHub only shows a handful of contributors, it's not impossible.