Complete transition from Confluence to GitHub issues
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 6
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
There are many issues noted in https://openedx.atlassian.net/wiki/spaces/AC/pages/2554331530/Toggles+and+Settings+Documentation. The higher priority issues have already been migrated to GitHub.
Additional Notes:
- Ideally the page could be archived once this is complete.
- As of 2023-06-24, the issues are not yet on a Project, so the priorities in the doc (for the already migrated tasks) are not yet in represented in GitHub. It would be great if that information could be handled somehow.
- The notes that haven't yet been migrated to GitHub may be lower priority, and should either be ice-boxed (deleted/archived?) or moved to GitHub. They will need to be reviewed bullet by bullet.
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 the linked Confluence page and compare its remaining bullets with the existing GitHub issues. Review each note, migrate or archive it as appropriate, preserve the stated priorities in GitHub, and archive the Confluence page when no actionable notes remain.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100