25
Inside the R Consortium Joseph Rickert Microsoft & R Consortium ISC

Inside the R Consortium

Embed Size (px)

Citation preview

Page 1: Inside the R Consortium

Inside the R ConsortiumJoseph RickertMicrosoft & R Consortium ISC

Page 2: Inside the R Consortium

Working with the R FoundationSupporting the R user communityContinuing the growth of the R ProjectLinux Foundation collaborative projectNon-profit trade organization

Page 3: Inside the R Consortium

• Create infrastructure and standards to benefit all R users

• Promote R as a vital component of a production Data Science platform

• Create and promote best practices for:• the development and maintenance of R code and applications• evaluating, adopting, validating, and managing R code and applications

• Provide information and metrics about growth and adoption of R

• Support the annual useR! conference as the primary conference for the R community.

Goals of the Consortium

Page 4: Inside the R Consortium

Board of Directors• Louis Bajuk-Yorgan (chair) – TIBCO• JJ Allaire - RStudio• John Chambers – R Foundation• Richard Pugh – Mango Solutions• David Smith – Microsoft• Hadley Wickham – ISC Representative

R Consortium Goverance

Page 5: Inside the R Consortium

• Mission: create, organize, establish and maintain• Infrastructure projects• Infrastructure collaboration Initiatives

• Current members• Hadley Wickham (chair) – RStudio• Stephen Kaluzny – TIBCO• Joseph Rickert – Microsoft• Luke Tierney – University of Iowa

Infrastructure Steering Committee (ISC)

Page 6: Inside the R Consortium

Projects Funded

Page 7: Inside the R Consortium

• Gábor Csárdi• A service for developing, building, testing

and validating R packages• Complementary to CRAN and R-Forge• https://github.com/r-hub/proposal

R-HUB: $85K

Page 8: Inside the R Consortium

• Simplify the R package development process:• Package creation• building binaries• continuous integration• publishing, distributing and maintaining packages

• Provide services free for all members of the community

• Encourage community contributions• Pre-test CRAN package submissions to ease

burden on CRAN maintainers.

Goals for R-Hub Include:

Page 9: Inside the R Consortium
Page 10: Inside the R Consortium

• Kirill Müller (ETH Zürich)• Improve database access in R so that

porting code is simplified and less prone to error

• Plan:• Create a DBI specification, centralized test and boiler plate for DBI

backends• Improve existing DBI backends to adhere to the standard• Focus on RMySQL, RPostgres and RSQLite

Improving Database Interface (DBI): $25K

Page 11: Inside the R Consortium

• Mark Hornick, Lukas Stadler and Adam Welc (Oracle)

• RIOT: R Implementation, Optimization and Tooling

• A one-day workshop to:• Unite R language developers• Identify R language development and tooling opportunities• Increase involvement of the R user community

RIOT Workshop 2016: $10K

Page 12: Inside the R Consortium

• Richie Cotton (Weill Cornell Medicine in Quatar) and Thomas Leeper (The London School of Economics)

• Majority of R packages in English only• RL10N project will make it easier for R

developers to include translations in their own packages

• Plan:• Improve msgtools package• New package to adapt MTurkR for managing translation• New package to adapt translateR for automated translations

R Localization Proposal (RL10N): $10K

Page 13: Inside the R Consortium

• Gergely Daroczi (Hungarian R user group) and Steph Locke (Mango Solutions)

• “SatRdays” are community-led, regional conferences

• Intended to encourage collaboration, networking and innovation within the R community.

• Initially three events will be hosted, with plans for additional meet-ups as the R user base grows.

SatRdays: $15K

Page 14: Inside the R Consortium

• John Blishak, Jonah Duckles, Laurent Gatto, David LeBauer, and Greg Wilson (Software Carpentry)

• Two-day in-person instructor training course• Focused on teaching R programming• Introduces the basics of educational psychology and instructional

design• Targeted towards teaching adult learners

• Participants will be required to demonstrate good knowledge of R

Software Carpentry R Instructor Training: $10K

Page 15: Inside the R Consortium

• Edzer Pebesma (Institute for Geoinformatics, University of Muenster)

• Simplify analysis of geospatial data• Write an R package that complies with the “

Simple Features” standard for access and manipulation of spatial vector data• Open Geospatial Consortium• International Organization for Standardization

• Write a C++ interface to GDAL 2.0

Simple Features Access for R: $10K

Page 16: Inside the R Consortium

Working GroupsCollabotaio

n

Consensus

Confidence

Page 17: Inside the R Consortium

The benefits of forming a ISC working group are to have your project:• Vetted by the relevant experts• Sanctioned by the R Consortium• Receive the attention of the R Foundation• Become visible to the greater R Community• Administrative support from the R

Consortium 

Working Groups

Page 18: Inside the R Consortium

• Michael Lawrence (R core, Genetech), Edward Ma (HP), and  Indrajit Roy (HP)

• Develop a common framework to simplify and standardize how users program distributed applications in R

• Current status: • ddR is a CRAN package• 3 ML algorithms with R’s parallel package and HP Distributed R

“backends”• Current focus: More algorithms and Spark

driver

A Unified Framework for Distributed Computing in R: $10K

Page 19: Inside the R Consortium

• Adam Welc, Lucas Stadler, Mark Hornick• The proposal asserts that R’s native API is:• Broader than necessary, inconsistent, redundant, tied to the internals

of GNUR • A restructured API is crucial to R’s evolution

• The working group will:• Assess R’s current native API usage (potentially automatically)• Gather community & R core input• Seek consensus to design an easy-to-understand, consistent and

verifiable API that will drive R language adoption

Future-proof native APIs for R

Page 20: Inside the R Consortium

• Shivank Agrawal, Santosh K Chaudhari, Chen Liang, Qin Wang, Vlad Sharanhovich, Mark Hornick (Oracle)

• Develop tool for R that determines code coverage upon execution of a test suite

• Improve software quality• Promoting the use of code coverage more

systematically within the R ecosystem.

Code Coverage Tool for R

Page 21: Inside the R Consortium

Not Funded

Page 22: Inside the R Consortium

In this first round of funding, projects rejected were• Too specific• Too small• Too ambitious for resources requested• Too open ended• Already exists or partially implemented

somewhere else

Characteristics of Projects Not Funded

Page 23: Inside the R Consortium

• Think big: something that will benefit a sizeable portion of the R Community for years to come

• Collaborate: seek expert opinion about your ideas and find potential collaborators

• Do your homework: make sure you understand what relevant work already exists

• Write a detailed proposal and carefully estimate work, resources and money required

• Be careful what you ask for!

Suggestions for Submitting a Proposal

Page 24: Inside the R Consortium

• The R Consortium and the ISC are looking for new projects to support

• Projects that broadly help the R Community• Call for proposals now open, closing June

10th 2016• More information on the submission

process at https://www.r-consortium.org/about/isc

Call for Proposals