docs(plans): Add the course management by role plan#95
Merged
Conversation
What needs to be done, per role, on top of the shipped course domain: students browse, register for, read, and quit courses; instructors author courses and lessons, archive them, and handle their students; admins create instructor accounts, archive accounts, and archive any course or lesson. The plan verifies that the data model needs no change: archiving and dropping are already lifecycle states (PublicationStatus.ARCHIVED, EnrollmentStatus.DROPPED, users.is_active), and the INSTRUCTOR and ADMIN roles are already seeded. It prescribes four stacked feature branches (security foundation, student, instructor, admin) with one atomic commit per task.
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## dev #95 +/- ##
=========================================
Coverage 81.30% 81.30%
Complexity 62 62
=========================================
Files 23 23
Lines 246 246
Branches 13 13
=========================================
Hits 200 200
Misses 32 32
Partials 14 14 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What needs to be done, per role, on top of the shipped course domain:
students browse, register for, read, and quit courses; instructors
author courses and lessons, archive them, and handle their students;
admins create instructor accounts, archive accounts, and archive any
course or lesson.
The plan verifies that the data model needs no change: archiving and
dropping are already lifecycle states (PublicationStatus.ARCHIVED,
EnrollmentStatus.DROPPED, users.is_active), and the INSTRUCTOR and
ADMIN roles are already seeded. It prescribes four stacked feature
branches (security foundation, student, instructor, admin) with one
atomic commit per task.
This is part 1 of 2 in a stack made with GitButler: