Mailing-List: contact dev-help@reef.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@reef.apache.org
MIME-Version: 1.0
In-Reply-To: <56fec7a4.5a50620a.56a07.1681@mx.google.com>
References: <56FD9D89.7020207@weimo.de>
	<CADq0cj4+KU05OyB+EPajzpd5T_11zRSCq=mLvBKQ84X=NDsjbg@mail.gmail.com>
	<56FEBFE8.5050807@weimo.de>
	<56fec7a4.5a50620a.56a07.1681@mx.google.com>
Date: Fri, 1 Apr 2016 12:44:52 -0700
Message-ID: 
 <CAFu6yH1BSTCiaUGGnKJ4f_wrOUV167We+XWeYTvGtM-wqg6+9w@mail.gmail.com>
Subject: Re: [DISCUSS] Apache REEF is ...
From: Dongjoon Hyun <dongjoon@apache.org>
To: dev@reef.apache.org
Content-Type: multipart/alternative; boundary=001a113e4c6ed8a76d052f719cd8

--001a113e4c6ed8a76d052f719cd8
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

+1 for Option F.

It becomes conciser and stronger!

Dongjoon.

On Fri, Apr 1, 2016 at 12:10 PM, Boris Shulman <shulmanb@gmail.com> wrote:

> +1 for the latest version.
>
> -----Original Message-----
> From: "Markus Weimer" <markus@weimo.de>
> Sent: =E2=80=8E4/=E2=80=8E1/=E2=80=8E2016 11:37 AM
> To: "dev@reef.apache.org" <dev@reef.apache.org>
> Subject: Re: [DISCUSS] Apache REEF is ...
>
> On 3/31/2016 3:54 PM, Byung-Gon Chun wrote:
> > "standard" implies there's consensus among many parties. "common" may
> > be more accurate.
>
> Good point. It is a fine line between "standard library in the sense of
> stdlib.so" and "the *standard* off all the libraries for the purpose."
>
> How about dropping all qualifiers:
>
> > Apache REEF is a library for building distributed applications on top
> > of cluster resource managers (e.g., Apache Hadoop YARN and Apache
> > Mesos).
>
> I like this, because it simplifies the statement. And if all goes well,
> we can add back `the standard library` in a while, once we've earned it :=
-)
>
> On 3/31/2016 3:54 PM, Byung-Gon Chun wrote:
> > Instead of saying "standard library", perhaps we can say
> > "meta-framework".
>
> I'm not a fan of that term. It makes it less clear of what the immediate
> utility of REEF is: If you need an AM, you are best served writing it in
> REEF.
>
> > Do we want to say "distributed applications"? This's broad.
>
> We initially had "Big Data applications" there. I dropped it, because
> for example Azure Stream Analytics scales all the way from tiny to Big
> Data. Also, I don't like the hype connotation of "Big Data".
>
> > Mostly we're focusing on "distributed data processing applications".
> >  Perhaps we can narrow the scope.
>
> Yes, that is the current focus. At the same time, REEF is currently
> sparse in data primitives, and rich in control flow primitives. And
> those apply more broadly than to data processing apps. However, I am not
> set on this. If we find a concise and precise way to narrow it, I am all
> for it. I'd even be OK with dropping the "distributed" as it is implied
> by running on resource managers.
>
> Which brings me to a new, extremely concise Option F:
>
> > Apache REEF is a library for application development on cluster
> > resource managers (e.g., Apache Hadoop YARN and Apache Mesos).
>
> What do you think?
>
> Markus
>

--001a113e4c6ed8a76d052f719cd8--