I agree with you. If we have a roadmap we can tell new contributes easily. BTW Lewis mentioned about our vision. Mapreduce is outdated technology, we should support new execution engines( Spark, Tez ) in next releases. Wdyt ?
2015-01-12 11:10 GMT+02:00 Alparslan Avcı <[email protected]>: > That will be good. > > +1 > > > On Sun, Jan 11, 2015 at 10:53 PM, Alfonso Nishikawa < > [email protected]> wrote: > >> +1 >> >> 2015-01-11 16:03 GMT-01:00 Renato Marroquín Mogrovejo < >> [email protected]>: >> >> > +1 for roadmap as well. >> > I think a really important issue is the shim layers. We have to fully >> test >> > them and document them so people can actually use this code. And we >> should >> > try to standardize the functionality across the data stores so we can >> keep >> > on accepting new ones, or integrate with other systems. >> > >> > >> > Renato M. >> > >> > 2015-01-09 17:48 GMT+01:00 Henry Saputra <[email protected]>: >> > >> > > +1 for roadmap page for Apache Gora in the website >> > > >> > > On Fri, Jan 9, 2015 at 8:24 AM, Lewis John Mcgibbney >> > > <[email protected]> wrote: >> > > > Hi Folks, >> > > > I wanted to poll you guys on the possible creation of a well >> structured >> > > > Roadmap page for Gora. >> > > > It doesn't need to be anything fancy, but just one that lets one, at >> a >> > > > glance, comprehend what one should expect from the next Gora release. >> > > > Right now we have the Jira Roadmap [0] however (i don't know about >> you >> > > > folks) but I tend to view this as a wildcard tracker as oppose to a >> > > > strategic vision. >> > > > Any thoughts folks? >> > > > Thanks >> > > > Lewis >> > > > >> > > > [0] >> > > > >> > > >> > >> https://issues.apache.org/jira/browse/GORA/?selectedTab=com.atlassian.jira.jira-projects-plugin:roadmap-panel >> > > > >> > > > -- >> > > > *Lewis* >> > > >> > >> > > > > -- > Alparslan Avcı -- Talat UYARER Websitesi: http://talat.uyarer.com Twitter: http://twitter.com/talatuyarer Linkedin: http://tr.linkedin.com/pub/talat-uyarer/10/142/304
