Community growth: seed Discussions, add good-first-issues, purpose-tied sponsor goals, labs outreach, topics
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 35/100
- Issue 类型
- 功能
- 描述清晰度
- 描述清楚
- 活跃度
- 活跃
- 技术栈
- github, github-actions, go
调研方向
Start with docs/labs.md, examples/labs/, and FUNDING.yml, then review the repository’s Discussions, issue labels, and GitHub topics. The work spans community posts, sponsor goals, outreach, documentation, and repository metadata; done means each checklist item in the issue is completed, including at least three open good first issue items.
由索引模型根据 Issue 内容生成。
描述
Value
The project has strong engineering and docs but almost no community surface yet: Discussions are enabled with 0 posts, and FUNDING.yml lists only github: [TMHSDigital] with no stated goals. A few cheap moves turn visitors into contributors and sponsors.
Suggested approach
- Discussions: a v0.9.0 Announcements post, a pinned "Show your pipeline" thread, and a Polls thread on the next transport or format.
- Good first issues: 3-5 scoped items, e.g. new takeover fingerprints, a new lab scenario ("Lab 6: contribute a scenario"), and completion fixes.
- Sponsors: set GitHub Sponsors goals tied to concrete work (package-manager matrix #62, benchmark infrastructure, MCP server).
- Labs outreach: the five labs in
examples/labs/with answer keys are rare. Add a Codespaces deep link that opens straight into lab 1, and pitch them to course authors (university security courses, TryHackMe/HTB-style content creators). CITATION.cff already supports academic use. - Topics: add
dns-bruteforce,attack-surface-management,subdomain-takeover,dns-over-https,dns-over-tlsandosintonce v0.9.0 ships.
Done when
Discussions has seed posts, at least 3 open good first issue items exist, Sponsors goals are visible, the Codespaces lab link is in docs/labs.md, and topics are updated.
- 主要语言
- Go
- 星标
- 1
- 派生
- 1
- 平均合并
- 5 天 2 小时
- 30 天内合并 PR
- 3
环境准备
在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。
- 提供 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
TMHSDigital/subenum 的其他 Issue
-
area: cli enhancement good first issue
难度 2/5 1-3 小时 新手友好度 88/100
TMHSDigital/subenum#136 ·
维护者通常 1 天内回复
-
community documentation good first issue
难度 2/5 1-3 小时 新手友好度 85/100
TMHSDigital/subenum#135 ·
维护者通常 1 天内回复
-
area: dns enhancement good first issue
难度 2/5 1 小时以内 新手友好度 90/100
TMHSDigital/subenum#134 ·
维护者通常 1 天内回复
-
feature priority: low
难度 5/5 一周以上 新手友好度 35/100
TMHSDigital/subenum#131 ·
维护者通常 1 天内回复
-
documentation marketing priority: medium
难度 5/5 一周以上 新手友好度 25/100
TMHSDigital/subenum#127 ·
维护者通常 1 天内回复
查看 TMHSDigital/subenum 的全部 Issue
相似的 Issue
-
Discriminator mapping keys are listed in a random order可能已有人在做 @reuvenharrison 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复
-
Idle compaction monitors LIST the replica every tick when the newest destination file spans more than one TXID可能已有人在做 @pishuv 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 72/100
benbjohnson/litestream#1563 ·
维护者通常 2 天内回复
-
难度 1/5 1 小时以内 新手友好度 88/100
维护者通常 1 天内回复
-
agent-research agent-review-finding chore
难度 2/5 1-3 小时 新手友好度 66/100
jordansmall/spindrift#4922 ·
维护者通常 1 天内回复
-
gcsartifact: deleting a missing version returns an error可能已有人在做 @ktsoator 今天认领。 未关闭bug
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 2 天内回复