Overview
What this challenge is about.
Pick a published roadmap area on the chosen project (instructor will sanity-check the choice). Read the project's CONTRIBUTING.md, RFC template, governance model, and the 3 most-recent merged PRs in the area. Draft an RFC scoping the change conservatively — explicit non-goals matter as much as goals. Implement the change with full test coverage in the project's idioms, and post the PR with the reviewer-respectful tone the project's maintainers have publicly asked for. Iterate on review feedback within the project's response-time norms. Deliver: RFC document, PR (link + branch), 6-page retrospective covering RFC framing, review etiquette, and upstream-vs-fork ROI.
The Brief
What you'll do, and what you'll demonstrate.
Plan, scope, and land a non-trivial upstream patch in a major CNCF project, retiring the internal fork that depends on it.
Earning criteria — what you'll demonstrate
- Scope an upstream RFC respectfully and conservatively
- Navigate review etiquette under a public OSS governance model
- Implement and test changes in an unfamiliar codebase's idioms
- Translate upstream contribution into internal cost avoidance
Program Fit
Where this fits in your program.
Sharpens the same skills your degree expects you to demonstrate.
Skills
Skills you'll demonstrate.
Each one shows up on your verified credential.
Careers
Roles this prepares you for.
Real titles. Real skill bridges. Pick the one closest to your trajectory.
Career mappings coming soon.