News for hackers. Stuff that matters.

A comment on Zen project forks Zig, relicenses, and “moves” original license to separate file. Parent comment

Re:Zen project forks Zig, relicenses, and “moves” original l... by mobinmob on Wednesday December 04, 2019 @09:38AM (#21702485)
It does, with really minimal conditions (keep the license text and copyrights intact). I do not understand what the problem is. Zen seems to be a hard fork that uses the zig code and sub-licenses it. That may be unfortunate, but it seems perfectly legal.
[ Parent | on HN ]
Re:Zen project forks Zig, relicenses, and “moves” original l... by ksec on Wednesday December 04, 2019 @01:21PM (#21705177)
Not only that, Zen were one of the Top Contributors and Top Sponsors before the fork.

Not only is it legal, normal, and also morally correct.

I just cant see the problem.

[ Parent | on HN ]
Re:Zen project forks Zig, relicenses, and “moves” original l... by stock_toaster on Wednesday December 04, 2019 @03:07PM (#21706362)
I think the expectation was the part of the MIT license which says:

> keep the license text and copyrights intact

It sounds like the Zen project removed/moved license text itself. Is it ok to fork a project and rename a LICENSE file to ACKNOWLEDGMENTS and then add your own LICENSE file? Or does the MIT imply that you must retain the original license text in the LICENSE file?

IANAL so I have no clue as to the legality of that aspect in particular, but it sure /seems/ a bit unsavory, even if it may be legally ok.

[ Parent | on HN ]
Re:Zen project forks Zig, relicenses, and “moves” original l... by mobinmob on Thursday December 05, 2019 @09:58AM (#21712760)
The text of the MIT licence specifies that: "The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software." So, yes they can rename and move the license file. The ACKNOWLEDGEMENTS.md file includes all other licenses for code.
[ Parent | on HN ]