openedx / openedx/openedx-events
Address debugging improvement suggestions from community feedback
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 13
- Forks
- 33
- Avg merge
- 14h 37m
- Merged PRs (30d)
- 4
Description
Description
Feedback from a recent developer experience survey has highlighted several areas where the current debugging tools and processes can be improved to better support developers using the Open edX platform. This issue aims to address these concerns by enhancing debugging capabilities to make the process more efficient, effective, and user-friendly.
The overall objective of this issue is to address all community feedback to improve the library debugging capabilities.
### Tasks
- [ ] https://github.com/openedx/openedx-events/issues/371
- [ ] https://github.com/openedx/openedx-events/issues/372
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 reading the linked task issues #371 and #372, since this issue does not identify files or entry points. Use those issues to determine the requested debugging changes and scope; the work is done when both listed task items are addressed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- developer-experience
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100