DataTalksClub / DataTalksClub/website

D5.2 Freeze weekend: DTC courses cutover and self-paced mode

Open
#415 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
0
Forks
0
PR merge metrics
No merged PRs in 30d

Description

Plan issue D5.2, phase 5 of the community-base unification plan.

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

Depends on: D5.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: D5.1. Freeze required: yes. Playbook P13 on the development environment. Checks: cohort page, homework submission, leaderboard,
project peer review, certificate download, one self-paced course created in Studio with a unit
visible to a registered member.

Done when

  • spec 04 updated: the package owns curriculum and coursework; DTC keeps LearnerProfile
    and route compatibility

Contributor guide

No contributing guide indexed for this repository

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.

Research direction

Read docs/plan/phase-5.md section D5.2, docs/plan/STATUS.md, AGENTS.md, and _docs/PROCESS.md; confirm D5.1 is done before scheduling the P13 freeze. Use the listed cohort, homework, leaderboard, peer review, certificate, and self-paced checks, then update spec 04 so the stated ownership and compatibility criteria are met.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.