Skip to content

Align with template draft#471

Merged
hythloda merged 1 commit into
mainfrom
krlmlr-patch-1
Aug 20, 2025
Merged

Align with template draft#471
hythloda merged 1 commit into
mainfrom
krlmlr-patch-1

Conversation

@krlmlr
Copy link
Copy Markdown
Contributor

@krlmlr krlmlr commented Aug 18, 2025

AI generated.

See RConsortium/isc-proposal#17 for the continuous review branch.

3. **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](https://www.r-project.org/contributors.html).

4. **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 and assess the likelihood of success.
4. **The Proposal:** 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? Address what your proposal is at a high-level, go into detail about the specifics including minimum viable product, architecture, assumptions, and external dependencies.
Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I always hated the "likely failure modes", they are now in the template only as dependencies.

4. **The Proposal:** 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? Address what your proposal is at a high-level, go into detail about the specifics including minimum viable product, architecture, assumptions, and external dependencies.

5. **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 itemized budget and spending plan. We expect that most of the budget will be allocated for labor costs. We do not cover indirect costs. The ISC grants cannot cover such things as travel, lodging, food, journal publication fees, or personal hardware. Cloud services may be covered if they are specific to the project and the project period. The ISC reserves the right to vet how funds are used for each project separately. If in doubt, please reach out to us. 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 help promote your project.
5. **Project Plan:** Outline the milestones for development including start-up phase, technical delivery with target dates, dissemination strategy, and funding plan. Specify 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 expected outcomes. Include how you will ensure your work is available to the widest number of people, specify open-source licenses, hosting plans, and publicity strategy including quarterly R Consortium blog content.
Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should bring back the "won't fund" material here, or perhaps in a separate paragraph/box below.

@hythloda hythloda merged commit 1220dd2 into main Aug 20, 2025
@krlmlr krlmlr mentioned this pull request Aug 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants