DataTalksClub / DataTalksClub/community-base
C4.3 Events donor compatibility checkpoint
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 0
- Forks
- 0
- Avg merge
- 9m
- Merged PRs (30d)
- 210
Description
Plan issue C4.3, phase 4 of the community-base unification plan.
Spec: docs/plan/phase-4.md, section C4.3, in DataTalksClub/community-base. Status is tracked in docs/plan/STATUS.md there, which stays the source of truth.
Depends on: C4.2, A4.1. Do not start until every one of them is done in STATUS.md.
Spec
Repository: community-base. Depends on: C4.2, A4.1.
Goal: finalize the provisional events squash against the prepared AISL donor state.
Steps
- Record the exact donor commit SHA, model state, migration names and test count.
- Finalize the squash, leaving new shared schema in appended migrations.
- Run equivalence, reversibility, synthetic PostgreSQL and development-copy rehearsals.
Done when
- the events migrations are adoption compatible and no longer provisional
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by checking docs/plan/STATUS.md and docs/plan/phase-4.md, section C4.3, and confirm C4.2 and A4.1 are marked done. Record the donor SHA, model state, migration names, and test count, then review the specified equivalence, reversibility, synthetic PostgreSQL, and development-copy rehearsals. Done means the events migrations are adoption compatible and no longer provisional.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- django, postgresql, python
- Domain
- backend, database
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100