[Nagiosplug-devel] plug-in license

[shoks]

That would work for me. Thanks for the guidance!

On Tue, Dec 22, 2009 at 2:23 AM, William Leibzon <william at leibzon.org>wrote:

> Since no new plugins are being added to standard nagos-plugins distribution
> (which is under GPL) you should release new plugin on your own put it on
> exchange.nagios.org. You can use libraries available but you don't have to
> and I think no matter if you do or not you can release your plugin under any
> license including entirely commercial one.
>
> As far as BSD vs GPL it makes a difference only when some commercial
> company is going to integrate it into their own distribution with only
> binary being there (i.e. if plugin is written in C and only compiled version
> is released). If plugin is written in interpreted language (Perl) then even
> if they include it in their own distribution, the code is available for
> anyone and they can't put it under different license. Similarly they can
> include GPL plugin in their own distribution too (Redhat is commercial
> distro but obviously includes mostly GPL code) and because of what plugins
> really are, I can't see where the above would ever make a difference so I
> think releasing all plugins under GPL is fine even if you envision
> commercial use and distribution.
>
> Some of my own plugins are included in commercial (or semi-commercial since
> they make most code available as open-source) distributions - Groundwork and
> Zenoss. Nobody ever told me or asked for my permission but I don't see any
> issue either.
>
>
> On Mon, Dec 21, 2009 at 12:42 AM, shoks <lowbotskie at gmail.com> wrote:
>
>>
>>
>> On Mon, Dec 21, 2009 at 3:10 PM, William Leibzon <william at leibzon.org>wrote:
>>
>>> Release under any license you like if its not based on any other plugin
>>> code.
>>>
>> It will be developed from scratch and will not use or invoke any plugin
>> code. Will it not
>> be infected if being called upon, that being the framework is under GPL?
>>
>>
>>>
>>> P.S. What license are you planning on using and why?
>>>
>> Similar to the BSD license. The goal is not to impose any restriction on
>> the application
>> and use of the plugin, for commercial, proprietary or any purpose.
>>
>> Thanks
>>
>>>
>>> On Sun, Dec 20, 2009 at 10:24 PM, shoks <lowbotskie at gmail.com> wrote:
>>>
>>>> Hi,
>>>>
>>>> Is it accepted to release a plug-in under a non-GPL license? What is
>>>> the license requirement of such?
>>>>
>>>> Thanks,
>>>> shoks
>>>>
>>>>
>>>> ------------------------------------------------------------------------------
>>>> This SF.Net email is sponsored by the Verizon Developer Community
>>>> Take advantage of Verizon's best-in-class app development support
>>>> A streamlined, 14 day to market process makes app distribution fast and
>>>> easy
>>>> Join now and get one step closer to millions of Verizon customers
>>>> http://p.sf.net/sfu/verizon-dev2dev
>>>> _______________________________________________________
>>>> Nagios Plugin Development Mailing List
>>>> Nagiosplug-devel at lists.sourceforge.net
>>>> Unsubscribe at
>>>> https://lists.sourceforge.net/lists/listinfo/nagiosplug-devel
>>>> ::: Please include plugins version (-v) and OS when reporting any issue.
>>>> ::: Messages without supporting info will risk being sent to /dev/null
>>>>
>>>
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> This SF.Net email is sponsored by the Verizon Developer Community
>>> Take advantage of Verizon's best-in-class app development support
>>> A streamlined, 14 day to market process makes app distribution fast and
>>> easy
>>> Join now and get one step closer to millions of Verizon customers
>>> http://p.sf.net/sfu/verizon-dev2dev
>>> _______________________________________________________
>>> Nagios Plugin Development Mailing List
>>> Nagiosplug-devel at lists.sourceforge.net
>>> Unsubscribe at
>>> https://lists.sourceforge.net/lists/listinfo/nagiosplug-devel
>>> ::: Please include plugins version (-v) and OS when reporting any issue.
>>> ::: Messages without supporting info will risk being sent to /dev/null
>>>
>>
>>
>>
>> ------------------------------------------------------------------------------
>> This SF.Net email is sponsored by the Verizon Developer Community
>> Take advantage of Verizon's best-in-class app development support
>> A streamlined, 14 day to market process makes app distribution fast and
>> easy
>> Join now and get one step closer to millions of Verizon customers
>> http://p.sf.net/sfu/verizon-dev2dev
>> _______________________________________________________
>> Nagios Plugin Development Mailing List
>> Nagiosplug-devel at lists.sourceforge.net
>> Unsubscribe at
>> https://lists.sourceforge.net/lists/listinfo/nagiosplug-devel
>> ::: Please include plugins version (-v) and OS when reporting any issue.
>> ::: Messages without supporting info will risk being sent to /dev/null
>>
>
>
>
> ------------------------------------------------------------------------------
> This SF.Net email is sponsored by the Verizon Developer Community
> Take advantage of Verizon's best-in-class app development support
> A streamlined, 14 day to market process makes app distribution fast and
> easy
> Join now and get one step closer to millions of Verizon customers
> http://p.sf.net/sfu/verizon-dev2dev
> _______________________________________________________
> Nagios Plugin Development Mailing List
> Nagiosplug-devel at lists.sourceforge.net
> Unsubscribe at
> https://lists.sourceforge.net/lists/listinfo/nagiosplug-devel
> ::: Please include plugins version (-v) and OS when reporting any issue.
> ::: Messages without supporting info will risk being sent to /dev/null
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://nagios-plugins.org/archive/devel/attachments/20091222/ec577b49/attachment.html>