Core Contributor Check-in: May 11th - 24th, 2024
34 days and counting until the Open edX 2024 Conference 
Core Contributor Hours
There was a total of 229 hours of contributions reported this past sprint. This is 26 hours more than the previous sprint of 203 hours.
The overall checklist response rate was 38 for this sprint, which is an 4% decrease from last sprint.
Summary of Responses
1. Do you need any help? Or is there anything you’d like to collaborate on?
- Yes! Join the Redwood Testing Team if you haven’t already. If you are more interested in solving bugs, you can help us by reviewing the test failures reported in the BTR board. Click on the issue you’re interested in, and help us solve it! If you have further questions, you can contact us on Slack. Thank you!
- I’ve marked some open-edx-proposals issues as “help wanted”, meaning they’re ready to be picked up by anyone who wants to help move the issue forward. Some, like #531, include a checklist of many tasks to add ADRs explaining some technology choices. Please ping @sarina for help/questions/review.
- Let’s remove all Devstack related documentation, it’s causing confusion for newcomers.
- Maintainers: please make sure your READMEs and other docs don’t mention Devstack
- Everyone: If you encounter docs pages with Devstack mentioned (or want to fix places others have flagged), please join this issue.
- If you have cute pets please join #pets and share them with us!
2. What should we improve? Are there any blockers?
- I’m gathering data using a form to improve developers’ experience with the Hooks extension framework, but I’m having trouble getting people to fill it out. If you, or any of your team members used the framework, please share it, or fill out the form and help us improve!
- After the Redwood Release, we need to review and reorganize the testing plan before the next release.
3. What did you accomplish this sprint?
- Openedd and merged a PR in tutor-contrib-codejail with a fix.
- Helped with the Open edX Conference Webinar.
- Added more types to Paragon.
- Got up to date with the release testing process and reported one issue.
- Participated in the large instances meeting.
- Reviewed two light PRs in OEP and edx-platform.
- Reviewed frontend-app-course-authoring PRs and a got up to date with new OEPs related to frontend-shell and OEP-65.
- Trained two team members on Sphinx documentation Edit Educator docs to a) remove edx.org-specific references b) validate/fix links c) add taxonomy terms Deliver “5 Lessons Learned building AI Assessment”
- Approved a bunch of new CC nominations – kudos to all the nominators and nominees!
- Reviewed the “Needs Revision” OEP status proposal.
- Repo maintenance for edx-submissions, completion.
- Redwood testing.
- Cleaned out open issues & pull requests from OEP repo Documentation changes/fixes/additions & reviews/testing for Redwood.
- Core sprints - Followed up & answered retro threads, groom board/backlog WG (and meeting)
- Announced OEP for escalation process to TOC
- Started working on new items and made a list of un-maintained repos.
- Redwood testing
4. What do you plan to work on in the upcoming sprint?
- More testing. We plan to upgrade the MIT residential Open edX instance to Redwood in June.
- Documentation - when to merge a PR raised by bots.
- Some maintenance in fairly unmaintained repos.
- The Redwood release!
- Testing…
- Conference talk.
- Aspects bugs and documentation.
5. What went well this sprint?
- Lots of eager testers. Good coordination with Product Working Group.
- Testing started
- Kudos to wg-maintenance for their support and advice on how best to handle dependabot PRs! Helped me merge with confidence.
- Community support
Questions or comments?
Please add any questions or comments you might have below. We’d love to hear from you!
And if you’d like to take a peek at the full report, see it on Listaflow