Re: [DISCUSS] Meerkat as a Hama sub-module or sub-project

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

Re: [DISCUSS] Meerkat as a Hama sub-module or sub-project

Thanks Ted. I generally agree with your suggestion. On Mon, Apr 28, 2014 at 5:45 PM, Ted Dunning ted.dunn...@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.

Re: [DISCUSS] Meerkat as a Hama sub-module or sub-project

2014-04-28 10:45 GMT+02:00 Ted Dunning ted.dunn...@gmail.com: 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

Re: [DISCUSS] Meerkat as a Hama sub-module or sub-project

I am also agree with suggestions of Ted and Tommas. Since Meerkat will be developed on top of Hama, it can be managed under Hama project like hama-graph. In addition, developing Meerkat will not make Hama changed largely (even not at all), because Hama is generic BSP framework. On Mon, Apr 28,

[DISCUSS] Meerkat as a Hama sub-module or sub-project

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,