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 2016/09/02 19:59:08 UTC
[DISCUSS] storm-jms Code Donation
I’d like to start a discussion around adding storm-jms as an external module. I’ve gotten a few request to do so and the only thing that’s held me back is tracking down contributors and having them submit ICLAs.
The code can be found here:
https://github.com/ptgoetz/storm-jms <https://github.com/ptgoetz/storm-jms>
If there’s support for adding it, I’ll track down contributors and handle the IP clearance process.
-Taylor
Re: [DISCUSS] storm-jms Code Donation
Posted by Bobby Evans <ev...@yahoo-inc.com.INVALID>.
+1 my group has used it and would love to see it as an official part of storm.
- Bobby
On Monday, September 5, 2016 11:40 PM, Satish Duggana <sa...@gmail.com> wrote:
+1 for getting this into Apache Storm.
I looked at this project earlier and I am open to be a committer sponsor
for storm-jms.
Thanks,
Satish.
On Tue, Sep 6, 2016 at 7:15 AM, P. Taylor Goetz <pt...@gmail.com> wrote:
> I'm totally open to sponsoring/supporting it. The code is fairly stable
> and hasn't changed much for years.
>
> The open pull requests are largely on hold pending a move to Apache. They
> are from new contributors that would potentially require an additional
> icla. Moving it to Apache would simplify the contribution process.
>
> -Taylor
>
> > On Sep 5, 2016, at 7:45 PM, Jungtaek Lim <ka...@gmail.com> wrote:
> >
> > This is good to merge since this is not duplicated / conflicted to
> anything
> > on current Apache Storm project.
> >
> > I would be +1 if any committer/PMCs is/are supportive and add themselves
> to
> > committer sponsor. There're a few issues and pull requests, and most of
> > them are stalled (several things are more than a year). If we adopt this
> to
> > Apache Storm someone should handle these and further works.
> >
> > - Jungtaek Lim (HeartSaVioR)
> >
> > 2016년 9월 3일 (토) 오전 8:36, S G <sg...@gmail.com>님이 작성:
> >
> >> I would love to see it part of storm/external and can volunteer to
> provide
> >> any help if required during the migration.
> >>
> >> -SG
> >>
> >> On Fri, Sep 2, 2016 at 12:59 PM, P. Taylor Goetz <pt...@gmail.com>
> >> wrote:
> >>
> >>> I’d like to start a discussion around adding storm-jms as an external
> >>> module. I’ve gotten a few request to do so and the only thing that’s
> held
> >>> me back is tracking down contributors and having them submit ICLAs.
> >>>
> >>> The code can be found here:
> >>>
> >>> https://github.com/ptgoetz/storm-jms
> >>>
> >>> If there’s support for adding it, I’ll track down contributors and
> handle
> >>> the IP clearance process.
> >>>
> >>> -Taylor
> >>>
> >>
>
Re: [DISCUSS] storm-jms Code Donation
Posted by Satish Duggana <sa...@gmail.com>.
+1 for getting this into Apache Storm.
I looked at this project earlier and I am open to be a committer sponsor
for storm-jms.
Thanks,
Satish.
On Tue, Sep 6, 2016 at 7:15 AM, P. Taylor Goetz <pt...@gmail.com> wrote:
> I'm totally open to sponsoring/supporting it. The code is fairly stable
> and hasn't changed much for years.
>
> The open pull requests are largely on hold pending a move to Apache. They
> are from new contributors that would potentially require an additional
> icla. Moving it to Apache would simplify the contribution process.
>
> -Taylor
>
> > On Sep 5, 2016, at 7:45 PM, Jungtaek Lim <ka...@gmail.com> wrote:
> >
> > This is good to merge since this is not duplicated / conflicted to
> anything
> > on current Apache Storm project.
> >
> > I would be +1 if any committer/PMCs is/are supportive and add themselves
> to
> > committer sponsor. There're a few issues and pull requests, and most of
> > them are stalled (several things are more than a year). If we adopt this
> to
> > Apache Storm someone should handle these and further works.
> >
> > - Jungtaek Lim (HeartSaVioR)
> >
> > 2016년 9월 3일 (토) 오전 8:36, S G <sg...@gmail.com>님이 작성:
> >
> >> I would love to see it part of storm/external and can volunteer to
> provide
> >> any help if required during the migration.
> >>
> >> -SG
> >>
> >> On Fri, Sep 2, 2016 at 12:59 PM, P. Taylor Goetz <pt...@gmail.com>
> >> wrote:
> >>
> >>> I’d like to start a discussion around adding storm-jms as an external
> >>> module. I’ve gotten a few request to do so and the only thing that’s
> held
> >>> me back is tracking down contributors and having them submit ICLAs.
> >>>
> >>> The code can be found here:
> >>>
> >>> https://github.com/ptgoetz/storm-jms
> >>>
> >>> If there’s support for adding it, I’ll track down contributors and
> handle
> >>> the IP clearance process.
> >>>
> >>> -Taylor
> >>>
> >>
>
Re: [DISCUSS] storm-jms Code Donation
Posted by "P. Taylor Goetz" <pt...@gmail.com>.
I'm totally open to sponsoring/supporting it. The code is fairly stable and hasn't changed much for years.
The open pull requests are largely on hold pending a move to Apache. They are from new contributors that would potentially require an additional icla. Moving it to Apache would simplify the contribution process.
-Taylor
> On Sep 5, 2016, at 7:45 PM, Jungtaek Lim <ka...@gmail.com> wrote:
>
> This is good to merge since this is not duplicated / conflicted to anything
> on current Apache Storm project.
>
> I would be +1 if any committer/PMCs is/are supportive and add themselves to
> committer sponsor. There're a few issues and pull requests, and most of
> them are stalled (several things are more than a year). If we adopt this to
> Apache Storm someone should handle these and further works.
>
> - Jungtaek Lim (HeartSaVioR)
>
> 2016년 9월 3일 (토) 오전 8:36, S G <sg...@gmail.com>님이 작성:
>
>> I would love to see it part of storm/external and can volunteer to provide
>> any help if required during the migration.
>>
>> -SG
>>
>> On Fri, Sep 2, 2016 at 12:59 PM, P. Taylor Goetz <pt...@gmail.com>
>> wrote:
>>
>>> I’d like to start a discussion around adding storm-jms as an external
>>> module. I’ve gotten a few request to do so and the only thing that’s held
>>> me back is tracking down contributors and having them submit ICLAs.
>>>
>>> The code can be found here:
>>>
>>> https://github.com/ptgoetz/storm-jms
>>>
>>> If there’s support for adding it, I’ll track down contributors and handle
>>> the IP clearance process.
>>>
>>> -Taylor
>>>
>>
Re: [DISCUSS] storm-jms Code Donation
Posted by Jungtaek Lim <ka...@gmail.com>.
This is good to merge since this is not duplicated / conflicted to anything
on current Apache Storm project.
I would be +1 if any committer/PMCs is/are supportive and add themselves to
committer sponsor. There're a few issues and pull requests, and most of
them are stalled (several things are more than a year). If we adopt this to
Apache Storm someone should handle these and further works.
- Jungtaek Lim (HeartSaVioR)
2016년 9월 3일 (토) 오전 8:36, S G <sg...@gmail.com>님이 작성:
> I would love to see it part of storm/external and can volunteer to provide
> any help if required during the migration.
>
> -SG
>
> On Fri, Sep 2, 2016 at 12:59 PM, P. Taylor Goetz <pt...@gmail.com>
> wrote:
>
> > I’d like to start a discussion around adding storm-jms as an external
> > module. I’ve gotten a few request to do so and the only thing that’s held
> > me back is tracking down contributors and having them submit ICLAs.
> >
> > The code can be found here:
> >
> > https://github.com/ptgoetz/storm-jms
> >
> > If there’s support for adding it, I’ll track down contributors and handle
> > the IP clearance process.
> >
> > -Taylor
> >
>
Re: [DISCUSS] storm-jms Code Donation
Posted by S G <sg...@gmail.com>.
I would love to see it part of storm/external and can volunteer to provide
any help if required during the migration.
-SG
On Fri, Sep 2, 2016 at 12:59 PM, P. Taylor Goetz <pt...@gmail.com> wrote:
> I’d like to start a discussion around adding storm-jms as an external
> module. I’ve gotten a few request to do so and the only thing that’s held
> me back is tracking down contributors and having them submit ICLAs.
>
> The code can be found here:
>
> https://github.com/ptgoetz/storm-jms
>
> If there’s support for adding it, I’ll track down contributors and handle
> the IP clearance process.
>
> -Taylor
>