A quick update The PR[1] for SPDX is already merged and released in 3.7. You can see the change is on the website[2]. I might add notes about the "Vim maintainer".
I will also start to help people to modify their license text (for those projects using Vim licenses). [1]:https://github.com/spdx/license-list-XML/pull/901 [2]:https://spdx.org/licenses/Vim.html othree於 2019年6月29日星期六 UTC+8下午11時35分00秒寫道： > > I didn't discuss with people at SPDX yet. > But I supposed it will by using XML tag <alt> > > I found BSD-3, BSD-4 uses a lot of <alt> tag[1]. > Sample code: > > <alt match=".+" name="organizationClause3">the organization</alt> > > The name is the name of this substitute slot. Match is regexp pattern. > And the content of the tag could be general value or specific value. > SPDX uses it on their website too. > > For BSD license, the content is general value, like organization, > copyright holder. And PostgreSQL[2] provides specific value like: > > <alt match=".+" name="copyrightHolderAsIs">THE UNIVERSITY OF > CALIFORNIA</alt> > > I suppose to use the second form, maybe: > > <alt match=".+" name="projectName">Vim</alt> > > Which will not change the result on the SPDX website. Won't > change the License text it self. Just define which part is the > project name and can be modified. > > [1]: > https://github.com/spdx/license-list-XML/blob/master/src/BSD-4-Clause.xml#L35 > [2]: > https://github.com/spdx/license-list-XML/blob/master/src/PostgreSQL.xml#L22 > > Bram Moolenaar <[email protected]> 於 2019年6月29日 週六 上午3:39寫道： > > > > > > > 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 > /// > > > Bram Moolenaar <[email protected]> 於 2019年6月29日 週六 上午3:39寫道： > > > > > > > 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 > /// > > > > -- > OOO > -- -- 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/47690aab-79cc-40ba-b5f4-a3e16d441da4%40googlegroups.com.
