So, anyone is interested to maintain Mahout and a thing of similar nature?

Cos

On Sat, Mar 07, 2015 at 02:13AM, Konstantin Boudnik wrote:
> I think it eventually boils down to who will be maintaining the component.
> 
> As Jay said - there's maintainer for the component and if it will continue
> like this we might have no choice but delete it: I think right now it blocks
> the release.
> 
> Cos
> 
> On Fri, Mar 06, 2015 at 02:29PM, Ed - 0x1b wrote:
> > some links to some of Mahout's replacements - not all Apache projects.
> > 
> > https://gigaom.com/2014/03/27/apache-mahout-hadoops-original-machine-learning-project-is-moving-on-from-mapreduce/
> > http://0xdata.com/
> > https://spark.apache.org/mllib/
> > https://databricks.com/blog/2014/06/30/sparkling-water-h20-spark.html
> > https://github.com/apache/mahout/tree/master/h2o
> > 
> > and
> > 
> > https://gigaom.com/2014/02/28/cloudera-is-rebuilding-machine-learning-for-hadoop-with-oryx/
> > 
> > On Fri, Mar 6, 2015 at 12:47 PM, Konstantin Boudnik <[email protected]> wrote:
> > > Thanks man! I've heard that there's a new project that picks up where 
> > > Mahout
> > > left of wrt Hadoop2.x support. But might be I am just delusional from
> > > hunger...?
> > >
> > > On Fri, Mar 06, 2015 at 02:32PM, jay vyas wrote:
> > >>    i sent a email to mahout-dev... maybe someone will ping back :)
> > >>    On Fri, Mar 6, 2015 at 2:25 PM, Jay Vyas <[email protected]>
> > >>    wrote:
> > >>
> > >>      Iirc we don't have any maintainers for it.
> > >>      Is anyone interested in maintaining it?
> > >>      > On Mar 6, 2015, at 2:23 PM, Konstantin Boudnik <[email protected]> 
> > >> wrote:
> > >>      >
> > >>      > Does anyone know what's the story with Mahout? Has it been fixed 
> > >> to be
> > >>      working
> > >>      > with Hadoop2 or shall we remove it from the BOM?
> > >>      >
> > >>      > Cos
> > >>      >
> > >>      >> On Sat, Feb 28, 2015 at 06:56PM, Konstantin Boudnik wrote:
> > >>      >> Guys,
> > >>      >>
> > >>      >> It'd be great if we can have the next release ready by ApacheCon 
> > >> in
> > >>      April.
> > >>      >> Think about all the PR and publicity we can get without any 
> > >> effort on
> > >>      our own.
> > >>      >> And perhaps from the tactical standpoint we shall call this 
> > >> release
> > >>      1.0?
> > >>      >>
> > >>      >> I believe the only major hurdle between us and the release is CI.
> > >>      Roman, I
> > >>      >> understand you're busy elsewhere, but could you please let us 
> > >> know
> > >>      what else
> > >>      >> needs to be done before we can start doing the regular builds 
> > >> and how
> > >>      the
> > >>      >> community can help. That's the highest priority, IMO.
> > >>      >>
> > >>      >> There a couple of the tickets left unfixed/unassigned on 
> > >> BIGTOP-1480,
> > >>      and if
> > >>      >> they aren't resolved on time we can move them farther. There's 
> > >> lesser
> > >>      than a
> > >>      >> half-dozen blockers and none of them look too big, honestly. And 
> > >> we
> > >>      have a
> > >>      >> whole lot of active committers and contributors to wrap-up the
> > >>      release in a
> > >>      >> couple of weeks.
> > >>      >>
> > >>      >> Do we want to try upgrade to HBase 1.x for this release or it 
> > >> might
> > >>      be too big
> > >>      >> of a distortion? Andrew, what do you think and do you have 
> > >> cycles to
> > >>      do that?
> > >>      >>
> > >>      >> What else we need to get done for this release? Suggestions?
> > >>      >>
> > >>      >> Is there anyone who wants to step up as the RM this time around? 
> > >> RM
> > >>      doesn't
> > >>      >> mean that you have to do all the job, but rather be an efficient 
> > >> with
> > >>      a stick ;)
> > >>      >>
> > >>      >> Thoughts?
> > >>      >>A  Cos
> > >>
> > >>    --
> > >>    jay vyas

Attachment: signature.asc
Description: Digital signature

Reply via email to