Repository navigation
Roadmap: Wesley near-term contributor onramp #646
Description
Activity
🔗 Related PRs
#43 - chore(oss): add PR template, CODEOWNERS, CHANGELOG (supersedes
#22) [merged]
#475 - Merge-worthy unmerged branches into omnibus reconciliation branch [merged]
#503 - Revise README.md for clarity and additional information [merged]
#506 - chore(release): v0.0.3 [merged]
#640 - chore(release): prepare v0.1.1 [merged]
📝 Issue Planner
Check the box below or use the
@coderabbitai plancommand to generate an implementation plan and prompts that you can use with your favorite coding assistant.- Create Plan
🧪 Issue enrichment is currently in open beta.
You can configure auto-planning by selecting labels in the issue_enrichment configuration.
To disable automatic issue enrichment, add the following to your
.coderabbit.yaml:issue_enrichment: auto_enrich: enabled: false
💬 Have feedback or questions? Drop into our discord!
Triage-label cleanup rationale before changing labels:
The retired
lane:*scheduling vocabulary conflicts withdocs/topics/contributing/triage.mdand the release-lane model. This issue is already correctly scheduled underv0.3.0; keeping an old retired-lane label would make its state ambiguous. I am removing only the stale retired-lane label; the issue remains open and scheduled forv0.3.0.Release-prep rationale before editing the body: this issue is a living contributor-onramp item scheduled for the next release, not unfinished work for the current release. Its body still names the current release by exact version, and
cargo xtask release-prep-guard --version <target>intentionally treats open exact-version title/body references as blockers. I am refreshing the wording so the issue stays useful without falsely owning the current release token.Release workflow hygiene before editing stale comments:
This issue is scheduled future-release work, not unfinished work for the current tag. The tag publish workflow performs a broad open-issue search that also matches old comments, so I am replacing stale current-release wording in prior comments only. Issue state, labels, milestone, and scope are unchanged.
Completed by the current contributor-onramp docs and roadmap routing now on main.
Evidence:
- docs: add first contributor fast paths #692 added the first-contributor fast paths in
docs/topics/contributing/first-pr.mdand wired them through the topic map and contributor guide. CONTRIBUTING.mdnow sends new contributors to scoped GitHub Issues, the good-first query, milestones, and the roadmap project instead of repo-local backlog state.docs/BEARING.mdanddocs/topics/contributing/triage.mdnow make GitHub Issues, Milestones, Projects, and labels the live roadmap authority.docs/topics/docs-orientation.mdgives the contributor/operator routing map for docs, roadmap, and issue triage.
No remaining concrete implementation task is left in this roadmap wrapper; future onboarding gaps should be filed as narrower issues.
- docs: add first contributor fast paths #692 added the first-contributor fast paths in
Summary
This roadmap issue gives new contributors one public place to orient on Wesley's near-term work without treating repository docs as a live backlog.
Current near-term goalposts
Contributor path
Start with issues labeled
good first issue. Those issues should be small, already scoped, and scheduled into a named release lane. Avoid unscheduled work unless a maintainer explicitly asks for triage help.Links