Hello, im new to this group but just wanted to put my two cents in.... People have forked or linked to nathanmarz/storm. Maybe down the road this could be a plan. If you woried about peoples forks somone could perpare them instructions if it where possible to rebase their forks on github to Apache/storm instead of its current place for thoose that want to continue to stay on GitHub; others may just want to natively just pull from the Apache Git instance.
-----Original Message----- From: Matt Franklin [mailto:[email protected]] Sent: Tuesday, December 10, 2013 9:27 AM To: [email protected] Subject: Re: [DISCUSS] Prepare for Apache Release 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? >
