I've followed this email thread relatively closely with the arguments for spark
versus h2o and the future of mahout and it doesn't seem like there's consensus
between different sets of people on the overall vision behind mahout, I'm
trying to spend some time contributing but it seems to me that there are
somewhat diverging viewpoints on what types of use cases should be targeted.
Given that this is the case I think both spark and h2o should live underneath
mahout for potentially solving different use cases but with a higher level
vision that unifies the 2 components, from a user's perspective its somewhat
confusing to use an open source framework that doesn't have a higher level
vision (needs to be a bit more than running ML algorithms at scale and should
be somewhat targeting specific business oriented use cases that brings the
underlying frameworks together) and frankly is lacking in ease of usability to
plug into existing infrastructure.
My 2 cents even though I'm not a committer but am deeply interested in working
with and adding to mahout.
> Date: Sun, 6 Apr 2014 10:16:39 -0500
> Subject: Re: Board Report
> From: andrew.mussel...@gmail.com
> To: dev@mahout.apache.org
>
> >
> > We have participated more than any organization, and argued for and
> > contributed to standardizing, fixing, improving or else retiring
> > existing code. It doesn't seem to catch on. I recognize it's always
> > more interesting to look past obligations, to a next thing. It's about
> > as popular as mom saying "you have to finish your broccoli before
> > dessert!" even if she's right. If the reaction is just "let's talk
> > about dessert" then you'll continue to see the, um, consumers of the
> > broccoli leave, as we've observed internally. Thanks for not shooting
> > the messenger, but maybe the messenger deserves a line in the board
> > report?
>
>
> Seems to me there has been a renewed effort to eat our broccoli, along with
> the other ideas people have been bringing on board.
>
> What are you proposing to put in the board report?
