Contributors Meetup Async Update - March 30th - April 12th , 2024

Working Groups Core Contributors
,
2

Core Contributor Check-in: Mar 30th - Apr 12th, 2024

:stopwatch: Core Contributor Hours

There was a total of 281.5 hours of contributions reported this past sprint, including 7.5 hours for Axim. This is 50.5 hours more than the previous sprint of 231 hours.

productivity
productivity1412×638 35.6 KB

The overall checklist response rate was 38% for this sprint, which is an 4% increase from last sprint.

response rate
response rate1308×478 29.5 KB

:notebook_with_decorative_cover: Summary of Responses

1. Do you need any help? Or is there anything you’d like to collaborate on?

@ali_hugo

  • Does anyone know the answer to this question about how MFE footer links will be customized in the updated Studio?

@Dean

  • Welcomes people to join testing the next release! You can post a message in the BTR Slack channel, or in the General Slack channel and tag @pdpinch, or myself.

2. What should we improve? Are there any blockers?

None

3. What did you accomplish this sprint?

@jyliugithub

  • Completed translation for Open edX platform
  • Developed content for BizDev Workshop at the Open edX conference
  • Participated in working group meetings
  • Completed survey for AWS partnership
  • Promoted Open edX Conference across social channels

@Felipe

  • Participated in Large Instances and the community release planning meeting
  • Reviewed the K8s dashboard PR in harmony (68)
  • Reviewed PRs in the context of py3.11, as well as the maintenance of packages I’m maintainer of
  • Investigated the blocker bug for the release about the MFE problem editor not rendering
  • Reviewed the last of the Wordpress PRs for package publication
  • Weighed in on the Frontend Extension Mechanisms conversation

@pdpinch

@Dean

  • Planned a meeting with BTR members to get started testing the next release

@chintan

  • Got three PRs merged

@Cassie

@jill

@ali_hugo

  • Gave UX feedback on the Resetting ORA submissions proposal
  • Tried to perform a product review on #324 (which turns out not to need one)
  • Emailed CC’s to remind them to complete the survey
  • Posted an update on the number of survey responders

@mafermazu

  • Fixed some WordPress plugin issues
  • Fixed a little issue with the tutor-contrib-codejail
  • Assisted and helped with the conference planning

@xitij2000

@farhaanbukhsh

  • Was able to review a few edx-platform PRs and test tutor harmony plugin

@juancamilom

  • Advanced the conversation / proposals in three of the proposed features for Unidigital / Campus Working Group that are to land upstream
  • Followed up with the Marketing Working Group, and prepared for the business development workshop for the conference
  • Worked as Product owner on multiple open source XBlocks being developed by the Unidigital initiative

4. What do you plan to work on in the upcoming sprint?

@Cassie

  • Now that the Graded Discussions Proposal is in the Wiki, I can start the next steps of the Product Review process

@jill

@Dean

  • Manual testing

@mafermazu

  • Make a few minor fixes in the WordPress plugin, participate a little more in discuss and planning a conference webinar

@pdpinch

@chintan

  • Will be on 4 weeks leave from 15th April

5. What went well this sprint?

@chintan

  • Support from maintenance group is great. I needed help with test runs. When I put it forward to the group, someone always helps

@farhaanbukhsh

  • Good amount of planned work

@pdpinch

@jill

@Felipe

  • We found the solution to one of the release blockers

:speech_balloon: 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 .

3 Likes