DataTalksClub / DataTalksClub/community-base

C5.3 Release 0.6.0

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

Nobody has claimed this yet.

Dominant language
Python
Stars
0
Forks
0
Avg merge
9m
Merged PRs (30d)
210

Description

Plan issue C5.3, phase 5 of the community-base unification plan.

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

Depends on: C3.7, C4.3, C5.2e, C5.1e. Do not start until every one of them is done in STATUS.md.

Spec

Repository: community-base. Depends on: C3.7, C4.3, C5.2e, C5.1e. Playbook P15.

This is the single adoption-ready domain release. Do not publish provisional v0.4.0 or
v0.5.0 releases containing kept-label migrations.

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 C5.3, and verify C3.7, C4.3, C5.2e, and C5.1e are marked done in docs/plan/STATUS.md before starting. Follow Playbook P15; done means publishing the single adoption-ready v0.6.0 release without provisional v0.4.0 or v0.5.0 releases.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.