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

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

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

Tony
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 [hidden email].
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

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

Bram Moolenaar

Tony wrote:

> 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?

What is distributed with Vim is under the Vim license.  With perhaps
some exceptions for where we have been unable to contact the author, and
we have to rely on the intention of the author.  And some parts that
come under a compatible license. Scripts you find elsewhere can go under
any license.  Since they are not compiled with Vim this doesn't matter.

--
hundred-and-one symptoms of being an internet addict:
46. Your wife makes a new rule: "The computer cannot come to bed."

 /// Bram Moolenaar -- [hidden email] -- 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_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 [hidden email].
For more options, visit https://groups.google.com/d/optout.