openedx / openedx/openedx-platform
Consolidate grading/progress display logic
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 8.2k
- Forks
- 4.4k
- Avg merge
- 6d 18h
- Merged PRs (30d)
- 42
Description
The frontend-app-learning repo implemented some rounding/bucketing logic for course grades on the frontend. https://github.com/openedx/edx-platform/pull/37399 pulls some of this logic back to the LMS backend for integrity reasons, however this PR also ends up replicating some backend grading logic for things like dropping the lowest scores.
Any duplication of grading code introduces the potential for drift between the score the user sees in their progress page and the scores that are actually being calculated for the user for the purposes of passing a course, granting a certificate, etc.
@pdpinch: Is this something that you folks could take the lead on?
FYI: @pdpinch, @sarina, @jmakowski1123, @arbrandes, @Anas12091101
Contributor guide
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 reviewing the frontend-app-learning grading and progress display logic alongside openedx/edx-platform pull request 37399. Trace the rounding, bucketing, and lowest-score-dropping behavior in both frontend and LMS backend implementations. Done means the progress-page score and backend course outcomes use one consistent grading implementation without duplicated logic.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100