You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@storm.apache.org by "P. Taylor Goetz" <pt...@gmail.com> on 2013/12/10 01:29:18 UTC
[DISCUSS] Prepare for Apache Release
Now that we’ve released 0.9.0, it’s time to start moving into our new home, and getting ready for our first Apache release.
Off the top of my head, and in no particular order, here are some of the tasks we need to accomplish:
1. Shutter the storm-user google group and direct people to the user@ and dev@ mailing lists. (I think Nathan is the only one who has permissions to do this).
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).
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.
4. Move all dependencies off of storm-specific builds (groupId=storm/backtype) and on to specific releases. (Nathan can probably best answer to which ones involve changes, and which ones are just point-in-time forks).
5. Figure out what to do with Thrift. Right now we’re using a forked version with packages renamed to avoid conflicts, which I could potentially cause problems with releasing under Apache. One potential fix would be to use a stock Thrift version and repackage it using jarjar.
6. Add apache headers to all source files. This is done [1]. I also need to figure out if we need the license header in generated (Thrift) files that are checked in to SCM.
7. Sort out the LICENSE and NOTICE files. I’ve started on this as well [1] (though I’ve ignored 0MQ for the moment). For a source-only release, I think we only need entries for jQuery and jQuery-cookie in the LICENSE file, which I’ve added. I’m also not sure if we have to put anything in LICENSE/NOTICE
8. Migrate github issues to JIRA
9. Setup storm webpage at Apache. We need to figure out what we want to do here: Migrate the existing storm-project.net site? Move existing wiki into Apache web site or cwiki, etc.?
That’s all I can think of for now. When I get a chance I’ll throw them in JIRA.
In the meantime, if anyone has any input on the above list, please share it.
Thanks,
Taylor
[1] https://github.com/ptgoetz/storm/tree/apache-headers
Re: [DISCUSS] Prepare for Apache Release
Posted by "P. Taylor Goetz" <pt...@gmail.com>.
Thanks for taking this on James, and especially for your effort to preserve all the discussions. It helps a lot. I can only imagine how tedious that was. ;)
I think for existing pull requests, we should let the author (pull request initiator) handle the migration. That will help weed out some of the older pull requests that are obsolete, etc., and allow those who are passionate about a patch push for it.
Taylor
> On Dec 15, 2013, at 3:37 AM, James Xu <xu...@gmail.com> wrote:
>
> Github issues are all migrated to JIRA now. What do we do to the Pull Requests in github?
>
>> On 2013年12月11日, at 下午10:56, P. Taylor Goetz <pt...@gmail.com> wrote:
>>
>>
>>> On Dec 11, 2013, at 8:59 AM, Gianmarco De Francisci Morales <gd...@apache.org> wrote:
>>>
>>> 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.
>>>>
>>>
>>> There has been some discussion around this issue. See, e.g.,
>>> http://mail-archives.apache.org/mod_mbox/www-legal-discuss/200508.mbox/%3cc5e63255050802170438fce46e@mail.gmail.com%3e
>>
>> Our solution for 0mq is to move that code out to a separate, non-Apache project. If users want to use the 0mq transport they can download/build it and install it themselves.
>>
>>>
>>> 5. Figure out what to do with Thrift. Right now we’re using a forked
>>>> version with packages renamed to avoid conflicts, which I could potentially
>>>> cause problems with releasing under Apache. One potential fix would be to
>>>> use a stock Thrift version and repackage it using jarjar.
>>>
>>>
>>> Would solving the more general class loader issue also solve this specific
>>> issue?
>>> https://github.com/nathanmarz/storm/issues/115
>>
>> Yes it would. But solving that issue is easier said than done. We’re currently exploring the use of jarjar to repackage it until a time when #115 can be properly addressed.
>>
>> - Taylor
>>
>
Re: [DISCUSS] Prepare for Apache Release
Posted by James Xu <xu...@gmail.com>.
Github issues are all migrated to JIRA now. What do we do to the Pull Requests in github?
On 2013年12月11日, at 下午10:56, P. Taylor Goetz <pt...@gmail.com> wrote:
>
> On Dec 11, 2013, at 8:59 AM, Gianmarco De Francisci Morales <gd...@apache.org> wrote:
>
>> 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.
>>>
>>
>> There has been some discussion around this issue. See, e.g.,
>> http://mail-archives.apache.org/mod_mbox/www-legal-discuss/200508.mbox/%3cc5e63255050802170438fce46e@mail.gmail.com%3e
>
> Our solution for 0mq is to move that code out to a separate, non-Apache project. If users want to use the 0mq transport they can download/build it and install it themselves.
>
>>
>> 5. Figure out what to do with Thrift. Right now we’re using a forked
>>> version with packages renamed to avoid conflicts, which I could potentially
>>> cause problems with releasing under Apache. One potential fix would be to
>>> use a stock Thrift version and repackage it using jarjar.
>>
>>
>> Would solving the more general class loader issue also solve this specific
>> issue?
>> https://github.com/nathanmarz/storm/issues/115
>
> Yes it would. But solving that issue is easier said than done. We’re currently exploring the use of jarjar to repackage it until a time when #115 can be properly addressed.
>
> - Taylor
>
Re: [DISCUSS] Prepare for Apache Release
Posted by "P. Taylor Goetz" <pt...@gmail.com>.
On Dec 11, 2013, at 8:59 AM, Gianmarco De Francisci Morales <gd...@apache.org> wrote:
> 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.
>>
>
> There has been some discussion around this issue. See, e.g.,
> http://mail-archives.apache.org/mod_mbox/www-legal-discuss/200508.mbox/%3cc5e63255050802170438fce46e@mail.gmail.com%3e
Our solution for 0mq is to move that code out to a separate, non-Apache project. If users want to use the 0mq transport they can download/build it and install it themselves.
>
> 5. Figure out what to do with Thrift. Right now we’re using a forked
>> version with packages renamed to avoid conflicts, which I could potentially
>> cause problems with releasing under Apache. One potential fix would be to
>> use a stock Thrift version and repackage it using jarjar.
>
>
> Would solving the more general class loader issue also solve this specific
> issue?
> https://github.com/nathanmarz/storm/issues/115
Yes it would. But solving that issue is easier said than done. We’re currently exploring the use of jarjar to repackage it until a time when #115 can be properly addressed.
- Taylor
Re: [DISCUSS] Prepare for Apache Release
Posted by Gianmarco De Francisci Morales <gd...@apache.org>.
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.
>
There has been some discussion around this issue. See, e.g.,
http://mail-archives.apache.org/mod_mbox/www-legal-discuss/200508.mbox/%3cc5e63255050802170438fce46e@mail.gmail.com%3e
5. Figure out what to do with Thrift. Right now we’re using a forked
> version with packages renamed to avoid conflicts, which I could potentially
> cause problems with releasing under Apache. One potential fix would be to
> use a stock Thrift version and repackage it using jarjar.
Would solving the more general class loader issue also solve this specific
issue?
https://github.com/nathanmarz/storm/issues/115
Cheers,
--
Gianmarco
Re: [DISCUSS] Prepare for Apache Release
Posted by "P. Taylor Goetz" <pt...@gmail.com>.
Dane,
#115 is a longstanding and (IMHO), an important issue to tackle. But also a difficult one.
However, it has huge implications for Storm, and will probably not be addressed in the initial Apache release.
The first release out of Apache will basically be a slight variant of 0.9.0.1, but with legal/licensing issues resolved and backed by the Apache Software Foundation.
- Taylor
On Dec 9, 2013, at 10:54 PM, Dane Hammer <da...@gmail.com> wrote:
> One of the most active issues is #115, and it would solve the thrift
> versioning problem. I don't know if the aim of the first incubator release
> is to make no code changes, however.
>
> On Monday, December 9, 2013, P. Taylor Goetz wrote:
>
>> Excellent. Thanks James!
>>
>> As you migrate issues, it’s probably best to just close the github issue
>> with a comment like “Migrated to Apache JIRA”. If you want to get fancy,
>> including a link to the JIRA would be cool (but not necessary).
>>
>> This could also likely be automated. The github API exposes everything
>> needed, I’m just not sure if the JIRA api does as well (and if the Apache
>> JIRA is open for API access from committers).
>>
>> Let me know if there’s anything I can help with.
>>
>> - Taylor
>>
>>
>> On Dec 9, 2013, at 9:07 PM, James Xu <xumingmingv@gmail.com <javascript:;>>
>> wrote:
>>
>>> Thanks Taylor for doing all of these! I can help on doing the 8th:
>> Migrate github issues to JIRA.
>>>
>>> On 2013年12月10日, at 上午8:29, P. Taylor Goetz <ptgoetz@gmail.com<javascript:;>>
>> wrote:
>>>
>>>> Now that we’ve released 0.9.0, it’s time to start moving into our new
>> home, and getting ready for our first Apache release.
>>>>
>>>> Off the top of my head, and in no particular order, here are some of
>> the tasks we need to accomplish:
>>>>
>>>> 1. Shutter the storm-user google group and direct people to the user@and dev@mailing lists. (I think Nathan is the only one who has permissions to do
>> this).
>>>>
>>>> 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).
>>>>
>>>> 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.
>>>>
>>>> 4. Move all dependencies off of storm-specific builds
>> (groupId=storm/backtype) and on to specific releases. (Nathan can probably
>> best answer to which ones involve changes, and which ones are just
>> point-in-time forks).
>>>>
>>>> 5. Figure out what to do with Thrift. Right now we’re using a forked
>> version with packages renamed to avoid conflicts, which I could potentially
>> cause problems with releasing under Apache. One potential fix would be to
>> use a stock Thrift version and repackage it using jarjar.
>>>>
>>>> 6. Add apache headers to all source files. This is done [1]. I also
>> need to figure out if we need the license header in generated (Thrift)
>> files that are checked in to SCM.
>>>>
>>>> 7. Sort out the LICENSE and NOTICE files. I’ve started on this as well
>> [1] (though I’ve ignored 0MQ for the moment). For a source-only release, I
>> think we only need entries for jQuery and jQuery-cookie in the LICENSE
>> file, which I’ve added. I’m also not sure if we have to put anything in
>> LICENSE/NOTICE
>>>>
>>>> 8. Migrate github issues to JIRA
>>>>
>>>> 9. Setup storm webpage at Apache. We need to figure out what we want to
>> do here: Migrate the existing storm-project.net site? Move existing wiki
>> into Apache web site or cwiki, etc.?
>>>>
>>>> That’s all I can think of for now. When I get a chance I’ll throw them
>> in JIRA.
>>>>
>>>> In the meantime, if anyone has any input on the above list, please
>> share it.
>>>>
>>>> Thanks,
>>>>
>>>> Taylor
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> [1] https://github.com/ptgoetz/storm/tree/apache-headers
>>>
>>
>>
Re: [DISCUSS] Prepare for Apache Release
Posted by Dane Hammer <da...@gmail.com>.
One of the most active issues is #115, and it would solve the thrift
versioning problem. I don't know if the aim of the first incubator release
is to make no code changes, however.
On Monday, December 9, 2013, P. Taylor Goetz wrote:
> Excellent. Thanks James!
>
> As you migrate issues, it’s probably best to just close the github issue
> with a comment like “Migrated to Apache JIRA”. If you want to get fancy,
> including a link to the JIRA would be cool (but not necessary).
>
> This could also likely be automated. The github API exposes everything
> needed, I’m just not sure if the JIRA api does as well (and if the Apache
> JIRA is open for API access from committers).
>
> Let me know if there’s anything I can help with.
>
> - Taylor
>
>
> On Dec 9, 2013, at 9:07 PM, James Xu <xumingmingv@gmail.com <javascript:;>>
> wrote:
>
> > Thanks Taylor for doing all of these! I can help on doing the 8th:
> Migrate github issues to JIRA.
> >
> > On 2013年12月10日, at 上午8:29, P. Taylor Goetz <ptgoetz@gmail.com<javascript:;>>
> wrote:
> >
> >> Now that we’ve released 0.9.0, it’s time to start moving into our new
> home, and getting ready for our first Apache release.
> >>
> >> Off the top of my head, and in no particular order, here are some of
> the tasks we need to accomplish:
> >>
> >> 1. Shutter the storm-user google group and direct people to the user@and dev@mailing lists. (I think Nathan is the only one who has permissions to do
> this).
> >>
> >> 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).
> >>
> >> 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.
> >>
> >> 4. Move all dependencies off of storm-specific builds
> (groupId=storm/backtype) and on to specific releases. (Nathan can probably
> best answer to which ones involve changes, and which ones are just
> point-in-time forks).
> >>
> >> 5. Figure out what to do with Thrift. Right now we’re using a forked
> version with packages renamed to avoid conflicts, which I could potentially
> cause problems with releasing under Apache. One potential fix would be to
> use a stock Thrift version and repackage it using jarjar.
> >>
> >> 6. Add apache headers to all source files. This is done [1]. I also
> need to figure out if we need the license header in generated (Thrift)
> files that are checked in to SCM.
> >>
> >> 7. Sort out the LICENSE and NOTICE files. I’ve started on this as well
> [1] (though I’ve ignored 0MQ for the moment). For a source-only release, I
> think we only need entries for jQuery and jQuery-cookie in the LICENSE
> file, which I’ve added. I’m also not sure if we have to put anything in
> LICENSE/NOTICE
> >>
> >> 8. Migrate github issues to JIRA
> >>
> >> 9. Setup storm webpage at Apache. We need to figure out what we want to
> do here: Migrate the existing storm-project.net site? Move existing wiki
> into Apache web site or cwiki, etc.?
> >>
> >> That’s all I can think of for now. When I get a chance I’ll throw them
> in JIRA.
> >>
> >> In the meantime, if anyone has any input on the above list, please
> share it.
> >>
> >> Thanks,
> >>
> >> Taylor
> >>
> >>
> >>
> >>
> >>
> >> [1] https://github.com/ptgoetz/storm/tree/apache-headers
> >
>
>
Re: [DISCUSS] Prepare for Apache Release
Posted by "P. Taylor Goetz" <pt...@gmail.com>.
Excellent. Thanks James!
As you migrate issues, it’s probably best to just close the github issue with a comment like “Migrated to Apache JIRA”. If you want to get fancy, including a link to the JIRA would be cool (but not necessary).
This could also likely be automated. The github API exposes everything needed, I’m just not sure if the JIRA api does as well (and if the Apache JIRA is open for API access from committers).
Let me know if there’s anything I can help with.
- Taylor
On Dec 9, 2013, at 9:07 PM, James Xu <xu...@gmail.com> wrote:
> Thanks Taylor for doing all of these! I can help on doing the 8th: Migrate github issues to JIRA.
>
> On 2013年12月10日, at 上午8:29, P. Taylor Goetz <pt...@gmail.com> wrote:
>
>> Now that we’ve released 0.9.0, it’s time to start moving into our new home, and getting ready for our first Apache release.
>>
>> Off the top of my head, and in no particular order, here are some of the tasks we need to accomplish:
>>
>> 1. Shutter the storm-user google group and direct people to the user@ and dev@ mailing lists. (I think Nathan is the only one who has permissions to do this).
>>
>> 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).
>>
>> 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.
>>
>> 4. Move all dependencies off of storm-specific builds (groupId=storm/backtype) and on to specific releases. (Nathan can probably best answer to which ones involve changes, and which ones are just point-in-time forks).
>>
>> 5. Figure out what to do with Thrift. Right now we’re using a forked version with packages renamed to avoid conflicts, which I could potentially cause problems with releasing under Apache. One potential fix would be to use a stock Thrift version and repackage it using jarjar.
>>
>> 6. Add apache headers to all source files. This is done [1]. I also need to figure out if we need the license header in generated (Thrift) files that are checked in to SCM.
>>
>> 7. Sort out the LICENSE and NOTICE files. I’ve started on this as well [1] (though I’ve ignored 0MQ for the moment). For a source-only release, I think we only need entries for jQuery and jQuery-cookie in the LICENSE file, which I’ve added. I’m also not sure if we have to put anything in LICENSE/NOTICE
>>
>> 8. Migrate github issues to JIRA
>>
>> 9. Setup storm webpage at Apache. We need to figure out what we want to do here: Migrate the existing storm-project.net site? Move existing wiki into Apache web site or cwiki, etc.?
>>
>> That’s all I can think of for now. When I get a chance I’ll throw them in JIRA.
>>
>> In the meantime, if anyone has any input on the above list, please share it.
>>
>> Thanks,
>>
>> Taylor
>>
>>
>>
>>
>>
>> [1] https://github.com/ptgoetz/storm/tree/apache-headers
>
Re: [DISCUSS] Prepare for Apache Release
Posted by James Xu <xu...@gmail.com>.
Thanks Taylor for doing all of these! I can help on doing the 8th: Migrate github issues to JIRA.
On 2013年12月10日, at 上午8:29, P. Taylor Goetz <pt...@gmail.com> wrote:
> Now that we’ve released 0.9.0, it’s time to start moving into our new home, and getting ready for our first Apache release.
>
> Off the top of my head, and in no particular order, here are some of the tasks we need to accomplish:
>
> 1. Shutter the storm-user google group and direct people to the user@ and dev@ mailing lists. (I think Nathan is the only one who has permissions to do this).
>
> 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).
>
> 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.
>
> 4. Move all dependencies off of storm-specific builds (groupId=storm/backtype) and on to specific releases. (Nathan can probably best answer to which ones involve changes, and which ones are just point-in-time forks).
>
> 5. Figure out what to do with Thrift. Right now we’re using a forked version with packages renamed to avoid conflicts, which I could potentially cause problems with releasing under Apache. One potential fix would be to use a stock Thrift version and repackage it using jarjar.
>
> 6. Add apache headers to all source files. This is done [1]. I also need to figure out if we need the license header in generated (Thrift) files that are checked in to SCM.
>
> 7. Sort out the LICENSE and NOTICE files. I’ve started on this as well [1] (though I’ve ignored 0MQ for the moment). For a source-only release, I think we only need entries for jQuery and jQuery-cookie in the LICENSE file, which I’ve added. I’m also not sure if we have to put anything in LICENSE/NOTICE
>
> 8. Migrate github issues to JIRA
>
> 9. Setup storm webpage at Apache. We need to figure out what we want to do here: Migrate the existing storm-project.net site? Move existing wiki into Apache web site or cwiki, etc.?
>
> That’s all I can think of for now. When I get a chance I’ll throw them in JIRA.
>
> In the meantime, if anyone has any input on the above list, please share it.
>
> Thanks,
>
> Taylor
>
>
>
>
>
> [1] https://github.com/ptgoetz/storm/tree/apache-headers
Re: [DISCUSS] Prepare for Apache Release
Posted by "P. Taylor Goetz" <pt...@gmail.com>.
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 <m....@gmail.com> wrote:
> On Tue, Dec 10, 2013 at 7:56 AM, Ted Dunning <te...@gmail.com> wrote:
>
>> On Mon, Dec 9, 2013 at 4:29 PM, P. Taylor Goetz <pt...@gmail.com> 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?
>>
Re: [DISCUSS] Prepare for Apache Release
Posted by Ted Dunning <te...@gmail.com>.
On Dec 10, 2013, at 9:26, Matt Franklin <m....@gmail.com> wrote:
>> 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)
Indeed that would be the best mechanism for continuing the current name.
RE: [DISCUSS] Prepare for Apache Release
Posted by Daniel Cruver <da...@cubrc.org>.
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:m.ben.franklin@gmail.com]
Sent: Tuesday, December 10, 2013 9:27 AM
To: dev@storm.incubator.apache.org
Subject: Re: [DISCUSS] Prepare for Apache Release
On Tue, Dec 10, 2013 at 7:56 AM, Ted Dunning <te...@gmail.com> wrote:
> On Mon, Dec 9, 2013 at 4:29 PM, P. Taylor Goetz <pt...@gmail.com> 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?
>
Re: [DISCUSS] Prepare for Apache Release
Posted by Matt Franklin <m....@gmail.com>.
On Tue, Dec 10, 2013 at 7:56 AM, Ted Dunning <te...@gmail.com> wrote:
> On Mon, Dec 9, 2013 at 4:29 PM, P. Taylor Goetz <pt...@gmail.com> 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?
>
Re: [DISCUSS] Prepare for Apache Release
Posted by Ted Dunning <te...@gmail.com>.
On Mon, Dec 9, 2013 at 4:29 PM, P. Taylor Goetz <pt...@gmail.com> 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.
> 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.
Has something like netty been considered?