Strengthening the R community by improving infrastructure and building for long term stability is one of the primary focuses of the R Consortium. To achieve this, the R Consortium’s Infrastructure Steering Committee (ISC) has developed this grant program to fund development of projects that broadly help the R community.

Examples of previously funded projects include:

  • R-hub, a centralised tool for checking R packages.
  • SatRDays, bootstrapping a system for local R conferences.
  • Testing DBI and improving key open source database backends.
  • Improvements in packages such as mapview and sf.

In this round of proposals, the ISC is interested in projects that:

  • Are likely to have a broad impact on the R community.
  • Have a focused scope ( a good example is the Simple Features for R project ). If you have a larger project, consider breaking it up into smaller chunks ( a good example of this done is with the DBI/DBItest project submission, where multiple proposals came in over time to address the various needs )

While all projects are considered, the ISC generally does not accept projects that:

  • Impact only a small part of the R community (i.e. a limited geographic region, or a very specialised domain).
  • Request conference, workshop, or meetup sponsorship. For these you should look at our user group program or connect with the marketing committee for larger events.
  • Are very exploratory. These are better to be pursued through the working group program.

Submitting a Proposal

Please provide a 2 to 5 page proposal that describes the problem you want to solve. We expect submissions to include these components:

  • The Problem: What problem do you want to solve? Why is it a problem? Who does it affect? What will solving the problem enable? This section should include a brief summary of existing work, such as R packages that may be relevant. If you are proposing a change to R itself, you must include a letter of support from a member of R Core.
  • The Plan: How are you going to solve the problem? Include the concrete actions you will take and an estimated timeline. What are likely failure modes and how will you recover from them?
  • The Team: Who will work on the project. Briefly describe all participants, and the skills they will bring to the project.
  • Project Milestones: Outline the milestones for development and how much funding will be required for each stage ( as payments will be tied to project milestone completion ). Each milestone should specify the work to be done and the expected outcomes, providing enough detail for the ISC to understand the scope of the project work.
  • How Can The ISC Help: Please describe how you think the ISC can help. If you are looking for a cash grant include a detailed itemised budget and spending plan. We expect that most of the budget will be allocated for labor costs, but we will consider funding travel, equipment and services, such as cloud computing resources with good justification. If you are seeking to start an ISC working group, then please describe the goals of the group and provide the name of the individual who will be committed to leading and managing the group’s activities. Also describe how you think the ISC can we help promote your project.
  • Dissemination: How will you ensure that your work is available to the widest number of people? Please specify the open source or creative commons license(s) will you use, how you will host your code so that others can contribute, and how you will publicise your work. We encourage you to plan content to be shared quarterly on the  R Consortium blog.

If you would like a template to help you structure your proposal, we encourage you to use one contributed by Steph Locke at https://github.com/RConsortium/isc-proposal.

We encourage you to seek feedback from the community before formally submitting the your proposal. You are welcome to email individual committee members to get their informal opinion, and you may want to publicise it more widely to get feedback from the broader R community.

Once you have completed your proposal, create a self-contained pdf and complete the form. If you do not receive a confirmation within 24 hours please email proposal@r-consortium.org. (If you have already received a confirmation that your proposal was received you do not need to take further action.)

The deadline for submitting a proposal is midnight PST, Wednesday October 31, 2018.

The Process

All proposals will be read and reviewed by the Chair of the ISC, and assigned to a committee member for detailed review. Proposals will be reviewed as a group, and you will be notified of the decision by December 1, 2018.

All accepted projects will be published on the R Consortium blog. Later the ISC will publish a brief description of unsuccessful projects, including the rationale for the decision (which might just be insufficient funding at this time). The intention is to help build up a knowledge base that helps the community submit good proposals.

We review this process yearly to ensure that the process is as smooth as possible, and to incorporate the knowledge gained from putting it into practice. All decisions to accept or reject proposals will be made by R Consortium in its sole discretion and shall be final.

If you have any questions about the proposals or submission process write to proposal@r-consortium.org