Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Community growth: seed Discussions, add good-first-issues, purpose-tied sponsor goals, labs outreach, topics

Open
#132 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
github, github-actions, go

Research direction

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.

Written by the indexing model from the issue text.

Description

community marketing priority: low

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-tls and osint once 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.

Dominant language
Go
Stars
1
Forks
1
Avg merge
5d 2h
Merged PRs (30d)
3

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from TMHSDigital/subenum

All issues in TMHSDigital/subenum

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.