VIM License Clarification: How does the license mean to interact with configs, plugins, etc?

Greetings Vim Users,

I have a question about the license at http://vimdoc.sourceforge.net/htmldoc/uganda.html.


http://vimhelp.appspot.com/if_lua.txt.html
http://vimhelp.appspot.com/if_pyth.txt.html
http://vimhelp.appspot.com/if_ruby.txt.html

Does / could scripting with viml, if_lua if_pyth trigger the II section in the VIM license?

There are a lot of superb plugins on vim.org and elsewhere that are licensed MIT, BSD and Apache. Among them, they utilize vimscript. Some of them further extend vim's functionality through import vim's lua, ruby or python libraries.

Is there any case where the Uganda license would conflict with MIT/BSD/Apache-licensed configs?

Can anything be done to strengthen the language that plugins, configuration, scripts do (or don't) fall under an "extended" version of vim?

--
--
You received this message from the "vim_use" 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_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.