openedx / openedx/sample-plugin
Separate init step for migrations shouldn't be necessary
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1
- Forks
- 4
- Avg merge
- 3d 1h
- Merged PRs (30d)
- 8
Description
The code here introduces separate tutor ... do init steps for running Django migrations for the sample plugin. This shouldn't be necessary since the plugin is installed with the rest of the Django dependencies which get picked up and migrated automatically.
Not critical, but maybe confusing, and definitely slows init down by 30+ seconds to spin up the container and run the whole no-op migration path.
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 with tutor-contrib-sample/tutorsample/plugin.py at lines 41–52 and inspect how the sample plugin is included in the normal Django migration flow. Remove the separate migration init steps if they are redundant, then verify that the sample plugin migrations are picked up during the standard initialization without the extra 30+ seconds.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 68/100