Mailing-List: contact dev-help@hama.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hama.apache.org
MIME-Version: 1.0
In-Reply-To: 
 <CAJwFCa0RsM1mrMpSpdCJ0360sJgURqNnAD52+LZz-KaK5PbnQg@mail.gmail.com>
References: 
 <CAGQgZQQfWuejw4aVg8w3anPLOr=DmayGqV-aScARjc6Up7cWVg@mail.gmail.com>
	<CAJwFCa0RsM1mrMpSpdCJ0360sJgURqNnAD52+LZz-KaK5PbnQg@mail.gmail.com>
Date: Mon, 28 Apr 2014 18:01:31 +0900
Message-ID: 
 <CAGQgZQReHEyy5EVqNcis1k720eAYLwGghE1s1jTQ5xHKQ57VjA@mail.gmail.com>
Subject: Re: [DISCUSS] Meerkat as a Hama sub-module or sub-project
From: "Edward J. Yoon" <edwardyoon@apache.org>
To: "general@incubator.apache.org" <general@incubator.apache.org>
Cc: "dev@hama.apache.org" <dev@hama.apache.org>, InJun Song <ijsong@gmail.com>
Content-Type: text/plain; charset=UTF-8

Thanks Ted. I generally agree with your suggestion.


On Mon, Apr 28, 2014 at 5:45 PM, Ted Dunning <ted.dunning@gmail.com> wrote:
> Edward,
>
> Sub-projects are generally frowned on.  Incubator projects can graduate
> eventually to a top-level project, but starting a project as a sub is not
> so good.  The incubator docs on this are pretty good reading.
>
> But if the committer community for your real-time BSP is (or can be) the
> same as the committer community for Hama itself, you might want to just
> fold this new code directly into Hama itself.  No need in that case for a
> separate project.
>
> If the committer community is very different, then a separate project is
> warranted.
>
> I don't think that the Hama development is such a high bandwidth thing that
> splitting is required.  To my mind that says that joining groups together
> is better than breaking them apart.  Together, the two efforts can feed off
> each other.  Apart, they could each run down due to lack of interest.
>
> You will know much better than any of us the details of your communities.
>
>
>
>
>
> On Mon, Apr 28, 2014 at 4:23 AM, Edward J. Yoon <edwardyoon@apache.org>wrote:
>
>> Hi guys,
>>
>> As some people already might know, I'm recently working on real-time
>> data processing project on top of Hama BSP model, called Meerkat[1]
>> (currently only few developers (from two organizations, Kakaotalk and
>> DataSayer) are involved in this project).
>>
>> According to our internal study, Storm-like DAG-style and
>> fault-tolerant streaming processing framework can be implemented on
>> top of Hama BSP model. And, furthermore, we're thinking, it may be
>> possible to connect to other BSP applications using some smart input
>> and output formats in the future e.g., streaming graph or learning BSP
>> applications. Thus, we believe that we may be able to have an
>> next-generation architecture that processes and analyzes the data
>> rapidly in real-time, beyond complex old-style data collecting,
>> storing, ordering, processing, and analyzing architecture.
>>
>> Does it make sense to you? If so, I'd like to start to move from
>> github to ASF soon, although this is very *early* stage. Because, it's
>> highly related with Apache Hama and others. Hama sub-module or
>> sub-project, (or Apache incubator?). Which is best you think?
>>
>> I'm also CC'ing general@i.a.o to see more feedbacks (from Apache big
>> data OSS communities).
>>
>> 1. https://github.com/datasayer/meerkat
>>
>> --
>> Best Regards, Edward J. Yoon
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: general-help@incubator.apache.org
>>
>>


-- 
Best Regards, Edward J. Yoon
CEO at DataSayer Co., Ltd.