Thanks Ted and Matt. So it seems 0MQ has to go, which shouldn’t be too much of a problem since we have a Netty-based transport.
Currently the default transport for Storm is 0MQ, with Netty being an optional alternative. I think we just need to reverse that, so that Netty is the default transport, and the 0MQ transport is a separate project (outside Apache, perhaps on Nathan’s github account) so that anyone hell bent on using 0MQ can do so if desired. On Dec 10, 2013, at 9:26 AM, Matt Franklin <[email protected]> wrote: > On Tue, Dec 10, 2013 at 7:56 AM, Ted Dunning <[email protected]> wrote: > >> On Mon, Dec 9, 2013 at 4:29 PM, P. Taylor Goetz <[email protected]> wrote: >> >>> 2. Close the nathanmarz/storm repo on github and direct people to >>> git://git.apache.org/incubator-storm.git (I’ve been keeping the github >>> and apache repos in sync). >>> >> >> Another option here is to simply reverse the direction of the pull here and >> leave nathanmarz/storm in place, but make it be an echo of the apache git. >> >> That allows less disruption to existing users. >> > > Keep in mind that Apache automatically mirrors git repos to GitHub under > the Apache group (Apache/Storm) > > >> >> >> >>> 3. Get an answer on whether we can continue to use 0mq as a dependency >>> given it’s LGPL license. And if so, what are the implications for >>> source-only and binary releases. >>> >> >> LGPL is a bit of a problem even if allowed. >> >> Note that depending on a modified version of 0mq that is distributed by the >> same group is even more problematic. >> > > +1. > > >> >> Has something like netty been considered? >>
signature.asc
Description: Message signed with OpenPGP using GPGMail
