Re: [PROPOSAL] Heron

2017-06-15 Thread P. Taylor Goetz
t;>>>>> post-open sourcing marketing around Heron seemed, at least to me, >>>>>> somewhat >>>>>>> aggressively negative toward Storm. >>>>>>> >>>>>>> As a peer to Apache Storm, how would the proposed "Apac

Re: [PROPOSAL] Heron

2017-06-15 Thread Ashvin A
al. The pre- and > > >>>>> post-open sourcing marketing around Heron seemed, at least to me, > > >>>> somewhat > > >>>>> aggressively negative toward Storm. > > >>>>> > > >>>>> As a peer to Apache Storm, how would the

Re: [PROPOSAL] Heron

2017-06-15 Thread Ashvin A
"Apache Heron" > > > >> community > > > >>> work to collaborate with the Storm community? If Heron is adopting > > API > > > >>> changes in Storm, then it seems there is an opportunity for > > > >> collaboration. > > > >>&

Re: [PROPOSAL] Heron

2017-06-15 Thread Bill Graham
; As a peer to Apache Storm, how would the proposed "Apache Heron" > >>>> community > >>>>> work to collaborate with the Storm community? If Heron is adopting > API > >>>>> changes in Storm, then it seems there is an opportunity for > >&

Re: [PROPOSAL] Heron

2017-06-15 Thread Debo Dutta (dedutta)
s there is an opportunity for >>>> collaboration. >>>>> >>>>> Don't take any of this as an objection to incubating the project. I >> would >>>>> support it. I would also be willing to be a mentor, if you would >> consider >>>>> taking on

Re: [PROPOSAL] Heron

2017-06-15 Thread Supun Kamburugamuve
as an objection to incubating the project. I > > would > > >>> support it. I would also be willing to be a mentor, if you would > > consider > > >>> taking on another. > > >>> > > >>> -Taylor > > >>> > >

Re: [PROPOSAL] Heron

2017-06-14 Thread William Markito Oliveira
>> support it. I would also be willing to be a mentor, if you would > consider > >>> taking on another. > >>> > >>> -Taylor > >>> > >>>> On Jun 8, 2017, at 1:23 PM, Bill Graham wrote: > >>>> >

Re: [PROPOSAL] Heron

2017-06-14 Thread P. Taylor Goetz
real-time, distributed, >>>> fault-tolerant stream processing engine. >>>> >>>> Our proposal can be found at https://wiki.apache.org/ >>> incubator/HeronProposal >>>> and is included below. >>>> >>>> >>>> Thank you,

Re: [PROPOSAL] Heron

2017-06-14 Thread Supun Kamburugamuve
can be found at https://wiki.apache.org/ > > incubator/HeronProposal > > > and is included below. > > > > > > > > > Thank you, > > > > > > Bill Graham on behalf of the Heron developers > > > > > > > > > #

Re: [PROPOSAL] Heron

2017-06-12 Thread Bill Graham
tream processing engine. > > > > Our proposal can be found at https://wiki.apache.org/ > incubator/HeronProposal > > and is included below. > > > > > > Thank you, > > > > Bill Graham on behalf of the Heron developers > > > > > > #

Re: [PROPOSAL] Heron

2017-06-09 Thread P. Taylor Goetz
gt; ## Abstract > Heron is a real-time, distributed, fault-tolerant stream processing engine > initially developed by Twitter. > > ## Proposal > > Heron is a real-time stream processing engine built for high performance, > ease of manageability, performance predictability an

Re: [PROPOSAL] Heron

2017-06-09 Thread Bill Graham
> >> # Heron Proposal >> >> ## Abstract >> Heron is a real-time, distributed, fault-tolerant stream processing engine >> initially developed by Twitter. >> >> ## Proposal >> >> Heron is a real-time stream processing engine built for high performance,

Re: [PROPOSAL] Heron

2017-06-09 Thread Supun Kamburugamuva
half of the Heron developers > > > # Heron Proposal > > ## Abstract > Heron is a real-time, distributed, fault-tolerant stream processing engine > initially developed by Twitter. > > ## Proposal > > Heron is a real-time stream processing engine built for high per

[PROPOSAL] Heron

2017-06-08 Thread Bill Graham
included below. Thank you, Bill Graham on behalf of the Heron developers # Heron Proposal ## Abstract Heron is a real-time, distributed, fault-tolerant stream processing engine initially developed by Twitter. ## Proposal Heron is a real-time stream processing engine built for high performance