Align with template draft

all-projects/callforproposals.qmd

@@ -42,17 +42,17 @@ While all projects are considered, the ISC generally does not accept projects th
 
 Please provide a 2 to 5 page proposal that describes the problem you want to solve. We expect submissions to include these components:
 
-1. **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).
+1. **Executive Summary:** This section provides a condensed view of the entire proposal, one page long. It should be a comprehensive high-level overview that captures the essence of the proposal, including its goals, methods, expected outcomes, deliverables, and budget.
 
-2. **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?
+2. **Signatories:** This section provides the ISC with a view of the support received from the community for a proposal. Acceptance isn't predicated on popularity but community acceptance is important. Willingness to accept outside input is also a good marker for project delivery. Include the project team who will deliver the project, contributors who helped with the proposal, and those who were consulted for feedback.
 
-3. **The Team:** Who will work on the project? Briefly describe all participants, and the skills they will bring to the project.
+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.
 
-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.
 
-6. **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) you will use, how you will host your code so that others can contribute, and how you will publicize your work. We encourage you to plan content to be shared quarterly on the R Consortium blog.
+6. **Success:** Projects should have a definition of done that is measurable, and a thorough understanding going in of what the risks are to delivery. Define what success looks like, how you will measure it along the way, and describe potential future work that could extend or develop the project further.
 
 The ISC has a limited grant budget, and we want to ensure that funded projects deliver the maximum benefit to the community. Successful proposals show well-defined milestones, with initial work completed to minimize delivery risk, e.g., upfront research and well-defined action plans.