Difference between revisions of "R Native API"
From R Consortium Wiki
Lukasstadler (Talk | contribs) |
Lukasstadler (Talk | contribs) |
||
| (3 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
= Working Group: Future-proof Native APIs for R = | = Working Group: Future-proof Native APIs for R = | ||
| + | This working groups will assess current native API usage, gather community input, and work towards an easy-to-understand, consistent and verifiable API that will drive R language adoption. | ||
| − | === 2016- | + | === 2016-06-30 Meeting UseR! === |
| − | + | see [[R Native API meeting 2016-06-30]] | |
| − | + | ||
| − | + | === 2016-06-20 Teleconference === | |
| − | + | see [[R Native API call 2016-06-20]] | |
| − | + | ||
| − | + | === 2016-06-20 Survey of API usage === | |
| − | + | see [[Initial Survey of API Usage]] | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
=== 2016-06-13 Initial WG members === | === 2016-06-13 Initial WG members === | ||
| Line 20: | Line 15: | ||
* Torsten Hothorn, University of Zurich | * Torsten Hothorn, University of Zurich | ||
* Mick Jordan, Oracle Labs | * Mick Jordan, Oracle Labs | ||
| + | * Stephen Kaluzny, TIBCO (ISC representative) | ||
* Michael Lawrence, Genentech | * Michael Lawrence, Genentech | ||
* Karl Millar, Google | * Karl Millar, Google | ||
| Line 33: | Line 29: | ||
* Gregory Warnes, Boehringer Ingelheim | * Gregory Warnes, Boehringer Ingelheim | ||
| − | === 2016- | + | === 2016-05-10 Initial phone meeting === |
| − | + | Attendence: | |
| + | * Stephen Kaluzny (WG sponsor in ISC) | ||
| + | * Lukas Stadler, Adam Welc, Mark Hornick (authors of the ISC project proposal) | ||
| + | Topics: | ||
| + | * Defining a WG leader (Lukas Stadler) | ||
| + | * Channels on which do distribute call for participation: | ||
| + | :* r-devel mailing list | ||
| + | :* Authors of important packages (top packages in download stats) with native components | ||
| + | :* Alterative and modified implementations: Tibco TERR, renjin, pqr, cxxr/rho, FastR | ||
| + | :* Program committee of the RIOT workshop [[http://riotworkshop.github.io]] | ||
| + | :* Lukas Stadler and Mick Jordan as initial members from Oracle Labs | ||
| + | * Discussion about stopping criteria for the WG / "What is the job of this WG?" | ||
| + | * Plan for meetings and discussions, general openness of all WG communication | ||
Latest revision as of 01:35, 3 July 2016
Contents
Working Group: Future-proof Native APIs for R
This working groups will assess current native API usage, gather community input, and work towards an easy-to-understand, consistent and verifiable API that will drive R language adoption.
2016-06-30 Meeting UseR!
see R Native API meeting 2016-06-30
2016-06-20 Teleconference
see R Native API call 2016-06-20
2016-06-20 Survey of API usage
see Initial Survey of API Usage
2016-06-13 Initial WG members
- Alexander Bertram, BeDataDriven
- Torsten Hothorn, University of Zurich
- Mick Jordan, Oracle Labs
- Stephen Kaluzny, TIBCO (ISC representative)
- Michael Lawrence, Genentech
- Karl Millar, Google
- Duncan Murdoch, University of Western Ontario
- Radford Neal, University of Toronto
- Edzer Pebesma, University of Münster
- Indrajit Roy, HP Labs
- Michael Sannella, TIBCO
- Lukas Stadler, Oracle Labs
- Luke Tierney, University of Iowa
- Simon Urbanek, AT&T Research Labs
- Jan Vitek, Northeastern University
- Gregory Warnes, Boehringer Ingelheim
2016-05-10 Initial phone meeting
Attendence:
- Stephen Kaluzny (WG sponsor in ISC)
- Lukas Stadler, Adam Welc, Mark Hornick (authors of the ISC project proposal)
Topics:
- Defining a WG leader (Lukas Stadler)
- Channels on which do distribute call for participation:
- r-devel mailing list
- Authors of important packages (top packages in download stats) with native components
- Alterative and modified implementations: Tibco TERR, renjin, pqr, cxxr/rho, FastR
- Program committee of the RIOT workshop [[1]]
- Lukas Stadler and Mick Jordan as initial members from Oracle Labs
- Discussion about stopping criteria for the WG / "What is the job of this WG?"
- Plan for meetings and discussions, general openness of all WG communication
