DataTalksClub / DataTalksClub/community-base

C3.7 Identity donor compatibility checkpoint

Open
#270 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 C3.7, phase 3 of the community-base unification plan.

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

Depends on: C3.6, A3.2, D3.1. Do not start until every one of them is done in STATUS.md.

Spec

Repository: community-base. Depends on: C3.6, A3.2, D3.1.

Goal: finalize provisional kept-label migrations against prepared donor schemas before release.

Steps

  1. Record exact AISL and DTC donor commit SHAs, model state, migration names and test counts.
  2. Finalize each kept-label squash and append genuinely new shared schema in later migrations.
  3. Run donor equivalence, reversibility, synthetic PostgreSQL and development-copy rehearsals.

Done when

  • every identity/community migration is adoption compatible and no longer provisional

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

First read docs/plan/phase-3.md, section C3.7, and check docs/plan/STATUS.md to confirm C3.6, A3.2, and D3.1 are done. Then inspect the provisional identity/community migrations and prepared donor schemas, recording the requested SHAs, model state, migration names, and test counts. Done means every migration is adoption compatible and no longer provisional, with the listed equivalence, reversibility, PostgreSQL, and development-copy rehearsals completed.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.