Thanks for heads up! I meant maybe to re-implement Mahout java Hadoop code to use scalding, and algebird. For me it would be great way to learn all of these technologies (scala, mahout, hadoop, cascading, scalding, algebird). Expected/desired improvement for Mahout committers and users would be hopefully less code in Mahout projec itselft, easier to maintain and learn, existing and implement new algorithms.
Kind regards, Stevo Slavic. On Mon, Mar 25, 2013 at 1:08 PM, Isabel Drost <isa...@apache.org> wrote: > Hi, > > On Mon, Mar 25, 2013 at 11:15 AM, Stevo Slavić <ssla...@gmail.com> wrote: > > > Please consider shipping Mahout 0.8 organized as it is now, and come back > > to ideas for the future after release. > > > > Personally I see the current discussion as a means to find out what people > want Mahout to be in the long time and on how to come back to increased > activity. > > > > > > > I agree, having more freely accessible data sets would help, not only > > Mahout. Maybe create a subproject or separate Apache project for that. > > > > There is one already: <http://lucene.apache.org/openrelevance/> - though > currently there's not too much activity. > > > > > > > As non-committer I'd contribute more to Mahout, had github be primary > > source. Now, when I contribute a pull request, it gets merged to Apache > git > > server by committer, and I don't get recorded as contributor on github. > > Maybe just workflow can be changed to improve this. > > > > Valuable input indeed. Though given that we are still using svn as > canonical version control system that sounds like a bigger project to me. > > > > > > Discussing about ideas for the future, have Mahout committers considered > > using scalding and/or algebird instead of or along with Java Hadoop API? > > > > > Just to clarify: Do you mean re-implenting what is available in these > languages or making what is implemented available to these languages? > > > Isabel >
