You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[outreach] CONTRIBUTING.md never points new contributors at good-first-issue/help-wanted or the community channels #372
CONTRIBUTING.md tells a contributor how to set up, test and open a PR, but not what to pick up or where to ask. It never mentions the repo's good first issue / help wanted labels (both exist: gh label list --repo hivecommons/hotshot), the terminal or AI CLI support request form, the Hive Commons Discord, or the community meeting. Those community links are on the README (## Contributing & community) and in .github/ISSUE_TEMPLATE/config.yml, but a contributor who lands on CONTRIBUTING.md — GitHub links it from the PR and issue pages — reaches a dead end.
Why Now
hotshot just added Gemini CLI (v0.2.0) and its ROADMAP's near-term item 3 asks for "more terminal and agent targets", which is exactly the kind of small, well-scoped work an outside contributor can take on. The community meeting / Twitch / Discord links were rolled out last week (#351, #366); CONTRIBUTING is the one entry point that was not updated.
Proposed Action
Add a short "Finding something to work on" section to CONTRIBUTING.md linking the good first issue and help wanted label queries, the target-request form, the ROADMAP, the Discord and the community meeting.
Pin those links in Tests/HotshotCoreTests/RepoMetadataDriftTests.swift (same pattern as testReadmeAndIssueChooserLinkEveryCommunityChannel) so they cannot drift.
Decision taken by hive: docs + test only; no labels are applied to existing issues (that is a maintainer triage call).
Activity
docs(contributing): point new contributors at starter issues and comm…
docs(contributing): point new contributors at starter issues and comm…