> Because many Vim Plugins/Scripts use "same as Vim" License. And lots of Vim
> plugin manager supports install Vim plugin from GitHub. I think it will be
> great if GitHub can recognize Vim License. And I am working on this now.
> While working on this. I realized that Vim License text have many content
> directly related to Vim, such as project name, maintainer, URLs.
> So, if I as a Vim Plugin author. Want to use Vim License and create a License
> file in code base. I should update these contents to reflect my project.
> I created a modified sample online.
> My question is:
> Is this modified License still Vim License?
> (only modify project name, URL/maintainer name, email)
> Or any modification is not allowed if I want to call it "Vim License".
> I know some project modify the content and rename the license, ex: tagbar
I'm not a lawyer, but I would think that if you change "Vim" to
"[Product Name]". and fill in the product name, that is still the Vim
license, but used for another product.
Note that "Vim maintainer" is different, that is not the product name
and should remain as-is. In the bigger context this part is a bit
confusing, but we can't change it now. The basic idea is that if
someone wants to make changes to [product name] but not publish the
changed code, the maintainer will have the right to decide about that.
This if you publish a plugin with the Vim license, I get to decide what
happens when someone makes a modified version and doesn't want to
publish it. In practice this never happened, thus it's a precaution,
while keeping the door open for a commercial spin-off.
hundred-and-one symptoms of being an internet addict:
259. When you enter your name in the AltaVista search engine, the top ten
matches do indeed refer to you.
/// Bram Moolenaar -- Br...@Moolenaar.net -- http://www.Moolenaar.net
/// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/
\\\ an exciting new programming language -- http://www.Zimbu.org
\\\ help me help AIDS victims -- http://ICCF-Holland.org