On 29 Jun 2016, at 01:21, Andriy Drozdyuk <[email protected]> wrote:

> Interesting. I'm not married to AGPL, just don't want companies hogging any 
> patches they made.

I'm not an Erlang user, but if I needed bindings for a language and
I saw an AGPL licence, I'd write my own bindings and release them
with a BSD licence - I'd do that whether I was writing something
open source or commercial. LGPL might fly if all you're worried
about is ensuring patches to the project get recycled.

Alex

> 
> On Tue, 28 Jun 2016 at 16:28 Pieter Hintjens <[email protected]> wrote:
> This is really cool.
> 
> The license choice will IMO hinder community growth around the project
> so I'd advise to you have a backup plan to switch to MPLv2 if the
> commercial uptake isn't sufficient.
> 
> On Tue, Jun 28, 2016 at 7:09 PM, Andriy Drozdyuk <[email protected]> wrote:
> > At Pieter's suggestion, I am putting this here:
> > https://github.com/chovencorp/erlangzmq
> >
> > Native erlang 18 implementation of ZMTP 3.1 (including resource property),
> > but without any security.
> >
> > Hopefully it will be useful to people. I know I'll use it myself - since all
> > (native) erlang bindings are out of date.
> >
> > This is a six month young project, so this is NOT performance or otherwise
> > tested at all, and I would appreciate any feedback (just take a second to
> > file an issue).
> >
> > Thank you,
> > --Andriy Drozdyuk
> >
> > _______________________________________________
> > zeromq-dev mailing list
> > [email protected]
> > http://lists.zeromq.org/mailman/listinfo/zeromq-dev
> _______________________________________________
> zeromq-dev mailing list
> [email protected]
> http://lists.zeromq.org/mailman/listinfo/zeromq-dev
> _______________________________________________
> zeromq-dev mailing list
> [email protected]
> http://lists.zeromq.org/mailman/listinfo/zeromq-dev

-- 
Alex Bligh




_______________________________________________
zeromq-dev mailing list
[email protected]
http://lists.zeromq.org/mailman/listinfo/zeromq-dev

Reply via email to