Hi Bram The staff of GitHub, Linksvayer told[1] me about the SPDX License List Data. If the license text have substitutions. It will be great to update the license data XML[2] first. I did dome research and known how to modify it. But I don't know who submits Vim license to SPDX at first.
So I think I should ask for your permission before I contact and send PR to SPDX. [1]:https://github.com/licensee/licensee/issues/385#issuecomment-506386613 [2]:https://github.com/spdx/license-list-XML/blob/master/src/Vim.xml othree於 2019年6月25日星期二 UTC+8下午11時38分46秒寫道： > Thank you > > Now I can understand which part can be modify. > I create a new template LICENSE text[1]. > And will use it for following process. > > Hope everything goes well. > > > [1]:https://othree.github.io/vim-license/?project=[project]#license-preview > > Bram Moolenaar於 2019年6月25日星期二 UTC+8上午10時13分15秒寫道： > > > 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? > > > > If that plugin is distributed, yes. If someone only makes changes for > > themselves, then publishing is not required. > > > > Note that since Vim plugins only work with Vim script, thus anybody who > > gets the plugin also implicitly gets the source code. It could be > > obfuscated, but that's about it. > > > > > * Is every "maintainer" in license text means "Vim Maintainer"? Or some > > > "maintainer" are "[Project] Maintainer"? > > > > All the occurences of "maintainer" in the license refer to the Vim > > 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. > > > > If not otherwise published, yes. But as mentioned, it would be > > difficult to create a Vim script and distributed it without implicitly > > distributing the source code. > > > > > > -- > > XML is a nice language for computers. Not for humans. > > > > /// 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/b8f0e421-83e7-4819-abab-5bd383aa030b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
