Contributors Meetup Async Update - March 16th - March 29th , 2024

Core Contributor Check-in: Mar 16th - 29th, 2024


:stopwatch: Core Contributor Hours

There was a total of 231 hours of contributions reported this past sprint, which is about 226 hours less than the previous sprint of 457 hours.

The overall checklist response rate was 34% for this sprint, which is an 11% decrease from last sprint.

Response Rates

:notebook_with_decorative_cover: Summary of Responses

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

@chintan

  • Can anyone confirm if learners are having issues unenrolling, or if this is a configuration mistake? See this issue.

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

@ayazquraishi

  • Suggests leveraging formal calendar invites, and a formal meeting note structure for all WG meetings.

3. What did you accomplish this sprint?

@chintan

  • Made progress on PRs. @feanil was able to help determine that the 3.12 python upgrade is not suitable for all python repos. Instead 3.11 will be used for many of them.
  • Joined more WG meetings, and gave input in some of them.
  • Moderated the forum - moved some topics and deleted some spam posts.

@jyliugithub

  • Developed content for the Open edX conference BizDev workshop.
  • Translation work for the on Open edX platform.

@jill

@ali_hugo

  • Product review on the UX update to the Resetting ORA submissions proposal.
  • Attended Core Product Meeting.
  • Worked on the talk @Cassie and I are presenting at the conference in July.

@farhaanbukhsh

  • Reviewed some PRs and left comments on a few.

@Felipe

  • Reviewed the Teams to Content Groups connection PR.
  • Participated in Large Instances and Maintainers WG meetings.
  • Reviewed the outstanding PR in the WooCommerce adaptor.
  • Started planning for the Paragon design tokens project.

@antoviaque

  • Was on leave last week, but worked on these topics:
    • Contributor Meetup and Coordination board update.
    • Meeting transcripts - getting Otter support to activate email warnings, testing Fireflies.
    • Review and moderating forum.

@Zia.Fazal

  • Reviewed a couple of edx-platform PRs (34358 & 34387) Reviewed couple of xblock PRs. (32& 68) Reviewed an ERB PR

@ayazquraishi

  • Began Core Contributor training.
  • Reviewed material for upcoming conference.

@Cassie

  • Product Review for Libraries Relaunch
  • Created Core Contributor Check-in Report
  • Worked on conference talk with @ali_hugo
  • Completed the Learning Technologies Stand Design
  • Designed the Open edX Conference Social media Adverts including Ambassador posts

@mafermazu

  • Planned webinar to be shown at the conference.

@pdpinch

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

@jill

  • Implementing and documenting Aspects scaling options.

@pdpinch

@farhaanbukhsh

  • A few tickets lined up for Harmony and frontend-app-gradebook repo.

@chintan

  • Complete the 3 PRs I raised, and make them 3.11 instead of 3.12.
  • If time permits will take up some new work.

@ali_hugo

  • I have very limited hours for CC work in April, so I will be focussing on any pressing items that may come up.

5. What went well this sprint?

@chintan

  • Community support was great, despite being new to these meetings and work, it’s always inclusive.

@pdpinch

  • I’m excited about the collaboration between BTR, Product WG and dev teams on the Redwood release. It seems like we will have a lot of interesting new features.

@jill

@farhaanbukhsh

  • I started following up on the Frontend WG, and was willing to work on Harmony.

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

2 Likes