> 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.
You'll have to figure out the right terminology. I see "the work" mentioned in other licenses, it's probably better than using "product". And figure out the right XML to use... I suppose they have tools to match the text against what's in a project, thus you will need to check that the XML still matches in the Vim project itself. -- Life would be so much easier if we could just look at the source code. /// 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/201906281939.x5SJdBLo028739%40masaka.moolenaar.net. For more options, visit https://groups.google.com/d/optout.
