Do you need any help? Or is there anything you’d like to collaborate on?
User
Not just yet, but I will be asking for reviews of the WIP UX work for Content Tagging over the coming months.
Ali Hugo
Working on Intro to Dev course. Currently could use help building and reviewing dev env section (both Tutor and Devstack). Reach out to me if interested.
- We need to stop linking PR descriptions to tickets that aren’t public. - Many, if not all, MFE settings do not have annotations.
Peter Pinch
What went well this sprint?
User
Good sprint, with good problem-solving!
Xavier Antoviaque
We seem to have come up with an effective format for the UX/UI Working Group meetings.
Ali Hugo
Although I had left a lot of the release notes writing for the last minute, it went pretty quickly.
Peter Pinch
Getting into the nitty detials of tutor hooks, I have had some ups and downs, but ultimately I was able to better understand it’s eco-system while building a spesfic service.
Ghassan Maslamani
lots of coordination with other community members ahead of the emoocs participation.
Engaged in the meetings of the MWG and CWG, Coordinated alongside Abstract and Raccoongang the participation en the emoocs 2023 conference, Prepared part of the workshop about Open edX to be given at emoocs, Prepared a short talk about open edX for the emoocs business track
Juan Montoya
Attended working group meetup for Build-Test-Release Working Group (May 29), Attended working group meetup for Developer Experience Working Group (June 5), Translated and revised some strings for fr_CA in Transifex, Tested Google Analytics 4 in Tutor Olive.4, Tested without much success migrating from Tutor Olive to Tutor Palm., Browsed through Slack and Discourse.
Pierre Mailhot
Ran the rest of the UX/UI Working Group through the wireframes for the Content Tagging project. Got a lot of helpful feedback and suggestions, Attended the “Scrum of Scrums” meetup and got a better idea of the product-related projects that are going on in the community
I was still working on cloudflared tutor plugins realted again to this roadmap Open edX Light/Express (minimalist version of Open edX) · Issue #169 · openedx/platform-roadmap · GitHub please see last comment for releative info. (I definilty spent more hours on this in this sprint, but I don’t think it’s important to be precivse given I working a featuer that might not be widely used, or has the intreset of commutiy). Keep following PRs issues from the previous sprint.
Ghassan Maslamani
Getting the Communications, ORA Grading, and Learner Dashboard MFEs working with Palm, Frontend working group coordination
Adolfo R. Brandes
Reviewed several OARS PRs, Read and discussed implications of merging OARS with Cairn
Jill Vogel
Participated in the workgroup meeting, helped around the OpenSearch setup config.
Gábor
What do you plan to work on in the upcoming sprint?
Keep working on cloudflared tutor plugin, Attend/prepare for next TGW, I thin it fails in next sprint.
Ghassan Maslamani
OEP for escalation process to TOC - Follow-up, TOC Meeting - Follow-up summaries & topics, Upstreaming course - Test recording & write instructions
Xavier Antoviaque
Finishing the updates to the Content Tagging wireframes based on the feedback I received in the UX/UI meeting, Planning and attending the next UX/UI meeting
Ali Hugo
On vacation from June 16th to July 3rd. I might not have much to report in the next two sprints as my vacation overlap a week of each sprint.
Pierre Mailhot
Merge the release notes, any additional testing of the Palm release
@pdpinch This came up in the past, though more for commit descriptions – the outcome of the discussion back then was this change: E0d/proposed footer changes by e0d · Pull Request #348 · openedx/open-edx-proposals · GitHub – the linking is allowed in commits (and by extension in PR descriptions?), but it shouldn’t be an optional footnote, not something part of the title or necessary to understand the ticket.
Do you have some examples that don’t follow this guideline? We could reach out to their authors to remind them of the rule on their PRs? Happy to help with this.
@pdpinch Do we have a rule/decision somewhere about this? I remember discussions about this in the past, though not sure if we ended up taking a proper decision on it? If so, we could do something similar – if not, we could establish a rule?
Looks like these have been reviewed and merged in the meantime
And an additional topic that came up during the contributor meetup yesterday – there is now a disconnect between the dates of the core contributor sprints, which come up every two weeks, and the contributor meetup which happens twice a month. It is ok most of the time, but since a month is slightly more than 4 weeks, it ended up drifting. So we discussed adjusting the dates for the contributors meetups to follow the same dates as the core contributors sprint, ie every two weeks. I have made the change on the calendar – if you spot any issue with it let me know. CC @jalondonot
This would be good. I’d especially like help building the Tutor section in Module 2. The Devstack section is written and under review. I’ve asked Farhaan to review Module 1 (Arch Overview) but new eyes on that would also be welcome. (by the way it might make sense for you to give all names to Legal under the entity agreement so anyone can jump in to review/produce content)
“We could use some help from the translations WG to assess the state of translations in Superset (which we use for OARS data visualization). I suspect it’s not great and we may want to contribute translations upstream to them if we can.”
They are continuing to host monthly educator-centered knowledge-sharing sessions. On Monday, ASU will be presenting on “Non-Linear Learning using Open EdX: Resource Hubs”. Next month will be a panel discussion on the implications of AI and LLMs on MOOCs.We are also gearing up a team to work on documentation on http://docs.openedx.org/
Working on the best system to have non-technical folks contribute to documentation using Google Sheets that can then be migrated to RST and Github.
They are continuing to develop the Harmony Helm charts and get closer to a releasable version. “Thanks to everyone who has been working on PRs!”
Releasing the chart - Jhony Avella created a new PR that’s from the same repo rather than a fork, and now it seems to be working. You can now use Helm to install it directly for testing.
OpenSearch cluster - Maksim Sokolskiy has resolved all the comments. Mostly been testing on minikube so would appreciate if someone can test on EKS. Found a new issue with the “reindex_course” command that affects both OpenSearch and ElasticSearch. PR is ready for second round of review.
Writing community guidelines for building features:
Some guidelines are now proposed for how to handle pull requests and how to propose making a feature (making a roadmap ticket, etc). This needs to be documented somewhere. Who can take this task?
Wiki documentation of PR review process [Ryan/Jenna/Shelly]
Documentation of doing product discovery/feature definition in the open and how to submit [Santiago]
Once it’s in wiki, translate to docs.openedx.oeg [Sarina]
Thank you @Natalia_Choconta for compiling these updates and keeping us all informed of what’s going on with all the working groups
I noticed we had a lot of new people joining the cc program this month… so great! Would this meet-up and update be a good place to highlight and welcome new members?
Thank u @antoviaque. It works perfect for the next update! With @jalondonot we adjusted the update dates and they are synchronized with the Sprint retro.
CC 
