That would work for me. Thanks for the guidance!<br><br><div class="gmail_quote">On Tue, Dec 22, 2009 at 2:23 AM, William Leibzon <span dir="ltr"><<a href="mailto:william@leibzon.org">william@leibzon.org</a>></span> wrote:<br> <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">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 <a href="http://exchange.nagios.org" target="_blank">exchange.nagios.org</a>. 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.<br> <br>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.<br> <br>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.<div> <div></div><div class="h5"><br> <br><div class="gmail_quote">On Mon, Dec 21, 2009 at 12:42 AM, shoks <span dir="ltr"><<a href="mailto:lowbotskie@gmail.com" target="_blank">lowbotskie@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> <br><br><div class="gmail_quote"><div>On Mon, Dec 21, 2009 at 3:10 PM, William Leibzon <span dir="ltr"><<a href="mailto:william@leibzon.org" target="_blank">william@leibzon.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> Release under any license you like if its not based on any other plugin code.<br></blockquote></div><div>It will be developed from scratch and will not use or invoke any plugin code. Will it not<br>be infected if being called upon, that being the framework is under GPL?<br> </div><div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>P.S. What license are you planning on using and why?<br></blockquote> </div><div>Similar to the BSD license. The goal is not to impose any restriction on the application<br> and use of the plugin, for commercial, proprietary or any purpose.<br><br>Thanks<br></div><div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> <br> <div class="gmail_quote"><div><div></div><div>On Sun, Dec 20, 2009 at 10:24 PM, shoks <span dir="ltr"><<a href="mailto:lowbotskie@gmail.com" target="_blank">lowbotskie@gmail.com</a>></span> wrote:<br> </div></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div><div></div><div>Hi,<br><br>Is it accepted to release a plug-in under a non-GPL license? What is<br> the license requirement of such?<br> <br>Thanks,<br><font color="#888888">shoks<br> </font><br></div></div>------------------------------------------------------------------------------<br> This SF.Net email is sponsored by the Verizon Developer Community<br> Take advantage of Verizon's best-in-class app development support<br> A streamlined, 14 day to market process makes app distribution fast and easy<br> Join now and get one step closer to millions of Verizon customers<br> <a href="http://p.sf.net/sfu/verizon-dev2dev" target="_blank">http://p.sf.net/sfu/verizon-dev2dev</a> <br>_______________________________________________________<br> Nagios Plugin Development Mailing List <a href="mailto:Nagiosplug-devel@lists.sourceforge.net" target="_blank">Nagiosplug-devel@lists.sourceforge.net</a><br> Unsubscribe at <a href="https://lists.sourceforge.net/lists/listinfo/nagiosplug-devel" target="_blank">https://lists.sourceforge.net/lists/listinfo/nagiosplug-devel</a><br> ::: Please include plugins version (-v) and OS when reporting any issue.<br> ::: Messages without supporting info will risk being sent to /dev/null<br></blockquote></div><br> <br>------------------------------------------------------------------------------<br> This SF.Net email is sponsored by the Verizon Developer Community<br> Take advantage of Verizon's best-in-class app development support<br> A streamlined, 14 day to market process makes app distribution fast and easy<br> Join now and get one step closer to millions of Verizon customers<br> <a href="http://p.sf.net/sfu/verizon-dev2dev" target="_blank">http://p.sf.net/sfu/verizon-dev2dev</a> <br>_______________________________________________________<br> Nagios Plugin Development Mailing List <a href="mailto:Nagiosplug-devel@lists.sourceforge.net" target="_blank">Nagiosplug-devel@lists.sourceforge.net</a><br> Unsubscribe at <a href="https://lists.sourceforge.net/lists/listinfo/nagiosplug-devel" target="_blank">https://lists.sourceforge.net/lists/listinfo/nagiosplug-devel</a><br> ::: Please include plugins version (-v) and OS when reporting any issue.<br> ::: Messages without supporting info will risk being sent to /dev/null<br></blockquote></div></div><br> <br>------------------------------------------------------------------------------<br> This SF.Net email is sponsored by the Verizon Developer Community<br> Take advantage of Verizon's best-in-class app development support<br> A streamlined, 14 day to market process makes app distribution fast and easy<br> Join now and get one step closer to millions of Verizon customers<br> <a href="http://p.sf.net/sfu/verizon-dev2dev" target="_blank">http://p.sf.net/sfu/verizon-dev2dev</a> <br>_______________________________________________________<br> Nagios Plugin Development Mailing List <a href="mailto:Nagiosplug-devel@lists.sourceforge.net" target="_blank">Nagiosplug-devel@lists.sourceforge.net</a><br> Unsubscribe at <a href="https://lists.sourceforge.net/lists/listinfo/nagiosplug-devel" target="_blank">https://lists.sourceforge.net/lists/listinfo/nagiosplug-devel</a><br> ::: Please include plugins version (-v) and OS when reporting any issue.<br> ::: Messages without supporting info will risk being sent to /dev/null<br></blockquote></div><br> </div></div><br>------------------------------------------------------------------------------<br> This SF.Net email is sponsored by the Verizon Developer Community<br> Take advantage of Verizon's best-in-class app development support<br> A streamlined, 14 day to market process makes app distribution fast and easy<br> Join now and get one step closer to millions of Verizon customers<br> <a href="http://p.sf.net/sfu/verizon-dev2dev" target="_blank">http://p.sf.net/sfu/verizon-dev2dev</a> <br>_______________________________________________________<br> Nagios Plugin Development Mailing List <a href="mailto:Nagiosplug-devel@lists.sourceforge.net">Nagiosplug-devel@lists.sourceforge.net</a><br> Unsubscribe at <a href="https://lists.sourceforge.net/lists/listinfo/nagiosplug-devel" target="_blank">https://lists.sourceforge.net/lists/listinfo/nagiosplug-devel</a><br> ::: Please include plugins version (-v) and OS when reporting any issue.<br> ::: Messages without supporting info will risk being sent to /dev/null<br></blockquote></div><br>