Skip to content

Commit c18f602

Browse files
nikomatsakislqd
andauthored
Update posts/inside-rust/2024-05-06-announcing-project-goals.md
Co-authored-by: Rémy Rakic <remy.rakic+github@gmail.com>
1 parent ed3f378 commit c18f602

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

posts/inside-rust/2024-05-06-announcing-project-goals.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -37,7 +37,7 @@ In exchange for committing energy towards the goal, owners are entrusted with de
3737

3838
> It’s difficult to make predictions, especially about the future.
3939
40-
Project goals will typically describe what the shiny future Rust will look like with the goal accomplished. However, humans are notoriously bad at planning and estimating, and in addition, resource committments may be time-bounded and may require re-evaluation on a regular cadence.
40+
Project goals will typically describe what the shiny future Rust will look like with the goal accomplished. However, humans are notoriously bad at planning and estimating, and in addition, resource commitments may be time-bounded and may require re-evaluation on a regular cadence.
4141

4242
Thus, project goals should focus primarily on a medium-term goal that can be accomplished within the year, and realistic milestones to be accomplished in that timeframe. Some project goals may be entirely completed within such a timeframe. Other project goals may set out incremental milestones (e.g. shipping an RFC), or even just experiments to determine feasibility.
4343

0 commit comments

Comments
 (0)