Getting Noticed in the dsh Ecosystem — English Summary

Full Chinese version: zh-04-contributing.md

Current official stance

External PRs are not accepted yet (developer preview). The official CONTRIBUTING.md lists other ways to contribute, and the team explicitly monitors GitHub Discussions and allocates resources based on feedback.

Four official contribution paths

1. Discussions: report reproducible bugs, upvote what matters. Reproducibility is mandatory: environment, version, steps, expected vs actual.
2. Plugin ecosystem (highest leverage): build a plugin you are excited about, add the dsh-plugin topic. The official repo states community packages are no less important than official ones.
3. Tutorials and guides: bilingual content is scarce and valuable; every command must be actually tested.
4. Answering questions: the fastest way to build a reputation.

Community channels

• GitHub Discussions: https://github.com/deepseek-ai/deepseek-harness/discussions
• Discord: https://discord.gg/Ycq5dCaS4
• WeCom (Chinese): QR codes in the official README (add the assistant, fill the survey)
• dsh-plugin topic: https://github.com/topics/dsh-plugin

14-day roadmap

1. Day 1-2: run npx @deepseek-ai/dsh web; read AGENTS.md and dev docs; join communities.
2. Day 3-4: build one small, real plugin (see the plugin tutorial); bilingual README; add dsh-plugin.
3. Day 5-6: publish getting-started + plugin tutorials.
4. Day 7-8: file verified bugs/doc gaps on Discussions (search first to avoid duplicates).
5. Day 9-14: keep answering questions, iterate the plugin to v0.2, write a retrospective, share links in Discord/WeCom.

Rules

No spamming, no duplicate posts, no clickbait. Every claim needs source code or a test as evidence. Expect breaking changes — state the version you tested.