<br><br><div class="gmail_quote">On Tue, Feb 9, 2010 at 9:44 AM, Alexis Richardson <span dir="ltr"><<a href="mailto:alexis.richardson@gmail.com">alexis.richardson@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Marcus<br>
<div class="im"><br>
On Tue, Feb 9, 2010 at 8:24 AM, Marcus Eriksson <<a href="mailto:krummas@gmail.com">krummas@gmail.com</a>> wrote:<br>
> Hi<br>
</div><div class="im">> No, I dont think they have to be GPL. Is, for example, BSD licensing my<br>
> plugin a solution to this problem?<br>
<br>
</div>It might be, if librabbitmq could be BSD licensed. That's one route.<br>
Equally we could use 'section 13' of the MPL to allow use of<br>
librabbitmq under the GPL, or if we felt perverse, the LGPL. Or, it<br>
may be possible to use MPL here.<br>
<br>
Can you tell me:<br>
<br>
1. if your plugin must be distributed with Drizzle?<br></blockquote><div><br></div><div>Not really, but it would be nice of course. The long term plan for drizzle is to have a plugin site where users can download plugins (like <a href="https://addons.mozilla.org/en-US/firefox/">https://addons.mozilla.org/en-US/firefox/</a>).</div>
<div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
2. how your plugin uses librabbitmq?<br></blockquote><div><br></div><div><a href="http://bazaar.launchpad.net/~krummas/drizzle/rabbitmq/annotate/head:/plugin/rabbitmq/rabbitmq_handler.cc">http://bazaar.launchpad.net/~krummas/drizzle/rabbitmq/annotate/head:/plugin/rabbitmq/rabbitmq_handler.cc</a></div>
<div><br></div><div>May I ask why you picked MPL? I'm a total newbie on licensing issues, but to me it feels quite hostile, I would expect client libs to be as open as possible to enable more products using the "main" product.</div>
<div><br></div><div>/Marcus</div></div>