# Project Goals notes

Rate-matching between prospective contributor(s) and project members

Project Goal should document proposed resources

Should typically present primarily the problem statement (and get consensus on *that*), and may mention draft solutions.

## Contributor Resources

- Specific People
- Amount of time (20%, 40%, 60%, 80%, 100%)
- Placeholder People
- Track record (so we don't have to track it down or rely on institutional memory

## Milestones

- Is there any early prototyping you could do to show the promise of this?
- Pre-RFC or design space exploration
- User study
- Blog post
- RFC drafts
- Experimental features
- Feature complete

## Menu

(From what teams?)

- Design meetings
- Bandwidth for brainstorming (optional)
- If there are subproblems you need ideas generated for, we have a surfeit of ideas. You may even want some of them.
- Review bandwidth for RFCs (specific team member(s))
- Review bandwidth for PRs (specific team member(s))

## Status updates

Try to help people automate project updates

Status updates on an automated regular schedule, if no update then it goes out with "no update, this may be stalled"