Skip to content

HACKTOBERFEST.md

Latest commit

 

History

History
48 lines (34 loc) · 2.91 KB

HACKTOBERFEST.md

File metadata and controls

48 lines (34 loc) · 2.91 KB
Raw

Hacktoberfest

Hacktoberfest is a good time to contribute to the Create Python App ecosystem, especially if you want a small, well-scoped task. The fastest way to get started is to pick a repo, scan for the right labels, and read the contributor guide before opening a PR.

Repositories newcomers can help with

Repository Good task types
create-python-app CLI bug fixes, docs polish, fixture/test improvements, release notes, contributor experience work
cpa-templates Template improvements, example updates, extension polish, catalog metadata fixes
website Landing page copy, docs navigation, examples, small UI polish
taps Packaging/documentation improvements, workflow tweaks, examples

Labels to look for

  • good first issue for small, low-risk tasks
  • help wanted when a maintainer is actively looking for contributions
  • Hacktoberfest for seasonal issues that are a good fit for the event

How to search for a task

  • Start with the repository's Issues tab and filter by one of the labels above.
  • Read the issue description, acceptance criteria, and linked discussion before you comment.
  • Prefer tasks that are clearly scoped, have an obvious next step, and do not depend on private access.
  • If you are not sure where to begin, ask in Discord or open a short note on the issue to say you are reviewing it.

Before you start

  • Read CONTRIBUTING.md first so you know the local workflow and expected PR style.
  • Join the community Discord for quick questions and coordination: Discord
  • If you are considering an assigned epic such as AI/ML catalog work, avoid duplicating it casually. Confirm the issue is still open and ask in Discord or on the issue thread before you start a parallel effort.

Suggested first tasks

  • Fix a typo or clarify a setup step in the docs
  • Add or improve a test for a CLI or scaffolding edge case
  • Help triage a small bug report or reproduce an issue locally
  • Improve template metadata or examples in a repo that already has a clear scope
  • Update release notes, changelog wording, or contributor-facing examples when they are clearly incomplete
  • Add a small regression test for a fixture or catalog path that is currently undocumented or brittle

What to avoid

  • Do not duplicate an assigned epic just because it looks similar to another issue.
  • Avoid large rewrites unless the issue explicitly asks for them or a maintainer has agreed to the scope.
  • Skip tasks that require private context, deployment access, or a broad architectural decision without guidance.

A good rule of thumb is to choose a task that is small enough to finish in one PR and clearly linked to an existing issue or discussion.