Hi Bram Thank you for reply so quick. That's very helpful.
Still have two questions: * Follow your example. I develop a plugin with Vim License and published. Someone modified it but not open source. Based on the Vim License. Someone should provide what he modified to Vim Maintainer(you). And you will decide what to do. Is it correct? * Is every "maintainer" in license text means "Vim Maintainer"? Or some "maintainer" are "[Project] Maintainer"? What I cared about most is `III)` which also includes a email address in the text. If this is also a "Vim Maintainer". Is it means every project(not Vim) with Vim License, have a modified version. You encourage people mail those changes to you. Bram Moolenaar於 2019年6月24日星期一 UTC+8上午11時08分12秒寫道： > > 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[1]. 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[2]. > > > > 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[3] > > 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 -- [email protected] -- 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 /// -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_dev/51dd0db1-735a-4fa3-ad02-ea082ca5338b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
