4 ms·
So I read over the license and you're right, the license does need to be included. However I don't see anything wrong with the project as long as the license is
by rthomas6 13y ago
So I read over the license and you're right, the license does need to be included. However I don't see anything wrong with the project as long as the license is included in its distribution. The license doesn't go against anything Neovim is doing, provided they include the license and provide the project source.
- bigtunacan 13y agoTherein lies the problem; the license is not being included. I find this a bit concerning since the default in forking a repo would have included it. So this gives off the impression then that the license was deliberately removed. Just to make it clear (most people on Hackernews probably already know this, but for the sake of anyone that doesn’t), it would look like this. hg clone https://vim.googlecode.com/hg/ https://vim.googlecode.com/hg/ neovim cd ./neovim git init && git add . && git commit -m “First commit” git remote add origin https://github.com/neovim/neovim.git https://github.com/neovim/neovim.git git push -u origin master There you have it; an exact fork from Mercurial push out to neovim on github, everything included. Getting those license files out of there took some manual steps somewhere in between lines 1 and 3.
- lucian1900 13y agoI think it's likely that the license was accidentally removed as part of cleaning up the build system.