3 ms·

I'm a hardcore Vim user and I just don't see the point of this. Not only that, but Vim is charity ware and requires the license to be included. The license is

I'm a hardcore Vim user and I just don't see the point of this. Not only that, but Vim is charity ware and requires the license to be included. The license is most notably absent from the Neovim fork. Wonder if that will be added any time soon...

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 ago
  Therein 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 ago
    I think it's likely that the license was accidentally removed as part of cleaning up the build system.
tarruda 13y ago
The license removal was completely accidental, I will include it as soon as I get back to it.
- jbranchaud 13y ago
  As promised, here is the commit with the origin Vim license -- https://github.com/neovim/neovim/commit/7cadf15eee1f377e9a7bb147180b86cf9637b2c6 https://github.com/neovim/neovim/commit/7cadf15eee1f377e9a7b...

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 ago
Therein 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 ago
  I think it's likely that the license was accidentally removed as part of cleaning up the build system.

tarruda 13y ago

The license removal was completely accidental, I will include it as soon as I get back to it.

jbranchaud 13y ago
As promised, here is the commit with the origin Vim license -- https://github.com/neovim/neovim/commit/7cadf15eee1f377e9a7bb147180b86cf9637b2c6 https://github.com/neovim/neovim/commit/7cadf15eee1f377e9a7b...