+1. On Thu, May 31, 2018 at 2:28 PM Joseph Bradley <jos...@databricks.com> wrote:
> Hossein might be slow to respond (OOO), but I just commented on the JIRA. > I'd recommend we follow the same process as the SparkR package. > > +1 on this from me (and I'll be happy to help shepherd it, though Felix > and Shivaram are the experts in this area). CRAN presents challenges, but > this is a good step towards making R a first-class citizen for ML use cases > of Spark. > > On Thu, May 31, 2018 at 9:10 AM, Shivaram Venkataraman < > shiva...@eecs.berkeley.edu> wrote: > >> Hossein -- Can you clarify what the resolution on the repository / >> release issue discussed on SPIP ? >> >> Shivaram >> >> On Thu, May 31, 2018 at 9:06 AM, Felix Cheung <felixcheun...@hotmail.com> >> wrote: >> > +1 >> > With my concerns in the SPIP discussion. >> > >> > ________________________________ >> > From: Hossein <fal...@gmail.com> >> > Sent: Wednesday, May 30, 2018 2:03:03 PM >> > To: dev@spark.apache.org >> > Subject: [VOTE] SPIP ML Pipelines in R >> > >> > Hi, >> > >> > I started discussion thread for a new R package to expose MLlib >> pipelines in >> > R. >> > >> > To summarize we will work on utilities to generate R wrappers for MLlib >> > pipeline API for a new R package. This will lower the burden for >> exposing >> > new API in future. >> > >> > Following the SPIP process, I am proposing the SPIP for a vote. >> > >> > +1: Let's go ahead and implement the SPIP. >> > +0: Don't really care. >> > -1: I do not think this is a good idea for the following reasons. >> > >> > Thanks, >> > --Hossein >> >> --------------------------------------------------------------------- >> To unsubscribe e-mail: dev-unsubscr...@spark.apache.org >> >> > > > -- > > Joseph Bradley > > Software Engineer - Machine Learning > > Databricks, Inc. > > [image: http://databricks.com] <http://databricks.com/> > -- Xiangrui Meng Software Engineer Databricks Inc. [image: http://databricks.com] <http://databricks.com/>
