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

D4.2 Freeze weekend: DTC events cutover

Open
  • Is something wrong?
#413 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
python
Domain
backend, release

Research direction

Read docs/plan/phase-4.md section D4.2, docs/plan/STATUS.md, AGENTS.md, _docs/PROCESS.md, and the relevant _docs/specs/ authority. Wait until D4.1 is done and a P13 freeze window is scheduled, then verify /events, free-event registration, Relay delivery, confirmation, and the spec 05 ownership-list update.

Written by the indexing model from the issue text.

Description

Plan issue D4.2, phase 4 of the community-base unification plan.

Spec: docs/plan/phase-4.md, section D4.2, in DataTalksClub/community-base. Status is tracked in docs/plan/STATUS.md there, which stays the source of truth.

Depends on: D4.1. Do not start until every one of them is done in STATUS.md.

Freeze issue. Playbook P13 applies: this moves data during a scheduled weekend freeze of the site. Do not start it outside a planned freeze window.

Process

This repository's AGENTS.md and _docs/PROCESS.md govern this work, with _docs/specs/ as the product authority. The plan says what to build and how to verify it; the site process says how work is done here.

Spec

Repository: DataTalksClub/website. Depends on: D4.1. Freeze required: yes. Playbook P13 on the development environment
(and production if DTC is live by then).

Checks

  • /events list and one detail by public_id render;
  • anonymous registration on a free event -> verification email delivered through Relay ->
    confirm link -> confirmed.

Done when

  • spec 05 "Accountless event registration" marked implemented by the package; events removed
    from _docs/specs/03-github-content-and-people.md data ownership list
Dominant language
Python
Stars
0
Forks
0
No merged PRs in 30d

Getting set up

  • Ships a Dockerfile or Docker Compose file
  • No pull request template
  • No contributing guide

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 DataTalksClub/website

All issues in DataTalksClub/website

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.