Accept or Obsolete "Provisional" OEPs
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Stale
- Domain
- documentation
Research direction
Review the provisional OEPs and ADRs identified by the sub-issues, then compare each with its current implementation and community use. Determine whether each should be Accepted, Replaced, or Obsolete, and update the relevant proposal documentation and status. Done means every identified provisional document has an appropriate, evidence-based status.
Written by the indexing model from the issue text.
Description
Several OEPs were authored aspirationally, and then never implemented. Other were partially implemented, but have stalled or diverged from reality. Yet others should be followed by the community, but are erroneously marked as "Provisional".
In order to establish OEPs as a trustworthy source of documentation, we should mark OEPs that never came to be as "Replaced" or "Obsolete" (whichever or is more appropriate). We should revise and "Accept" OEPs that are still relevant but mismatched with reality. We should simply "Accept" OEPs that are for all practical purposes adopted by the community.
Sub-issues have been made for all the found Provisional OEPs & ADRs.
- Dominant language
- Python
- Stars
- 49
- Forks
- 47
- Avg merge
- 3d 16h
- Merged PRs (30d)
- 3
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
More from openedx/openedx-proposals
-
Should we continue to support YAML settings?May be free again @kdmccormick claimed this 630 days ago, and no pull request is open. Open
openedx/openedx-proposals#684 · 3 comments · 1 assignee ·
-
feb25 under discussion
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
openedx/openedx-proposals#668 ·
-
Update & Accept OEP-55 MaintainersMay be free again @feanil claimed this 651 days ago, and no pull request is open. Openfeb25 under discussion
openedx/openedx-proposals#667 · 1 comment · 1 assignee ·
-
ADR for Flaky TestsOpenfeb25 good first issue help wanted
Difficulty 3/5 1-2 days Newbie friendliness 45/100
openedx/openedx-proposals#599 ·
-
feb25 under discussion
Difficulty 5/5 Over a week Newbie friendliness 25/100
openedx/openedx-proposals#587 · 6 comments · 1 reaction ·
All issues in openedx/openedx-proposals
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
mozilla-ai/cq#601 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
intcomma returns exponential notation for large floatsPossibly taken @Omarinho12345 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
python-humanize/humanize#521 ·
Maintainers usually reply within 1 day
-
LUCJ pass manager raises NoEdgeBetweenNodes when an edge is bad for two two-qubit gatesPossibly taken @hat-im claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
opensubtitlescom: provider rejects pt-PT even though its own converter maps itPossibly taken @paulo-0308 claimed this today. Open
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Diaoul/subliminal#1405 ·