Core Contributor Sprint Retro - July 8th - July 22nd

[antoviaque (Xavier Antoviaque (OpenCraft) - opencraft.com/help)]

@Dean Thank you for the recap!

Follow-up from previous sprints

A follow-up on the topic of improving PR descriptions discussed at the Contributors meetup: this PR has been merged to move towards better descriptions on PRs:

E0d/proposed footer changes

Sprint’s checkins discussions

@Kyle McCormick

I’d like to understand why the various frontend packages seem to have a lot of conflicting dependency specifications and if there’s a reason why so many core packages don’t even support React 17. Context: fix: support running this frontend in “developer mode” on Tutor · openedx/frontend-app-library-authoring@76c1756 · GitHub

@kmccormick During the contributors meetup, @arbrandes indicated that this is caused by the current design, and that there are discussions on unifying dependencies, but there isn’t a clear answer yet. @ghassan has suggested and volunteered to do a discovery on this, and has a proof of concept that he will publish.

@Peter Pinch

What is a CourseOutline? What is a CourseOverview? When/where do they get created? Why do I seem to be missing them sometimes?

@pdpinch On this @dave offered to discuss with you. He has also provided a quick explanation of what CourseOutlines and CourseOverviews during the contributors meetup – it should be towards the end of yesterday’s recording (last 10-15 minutes) which will be published by @jalondonot at Open edX Contributors Meetup - #105 by jalondonot and Contributor's Meetup 2022-07-26 · Issue #69 · openedx/wg-coordination · GitHub in the coming days.

@Xavier Antoviaque

Reviews needed on the draft charter for the election of the TOC community board members – see TOC Community Members Elections - Brainstorm thread - #3 by antoviaque . We will need to discuss further some of the TOC elections aspects - like whether to include learners in the voting or not.

Definitely have a look at the TOC election draft! These are important discussions, which will impact the direction of the project.

Also worth looking at these two other collaboration & governance topics, which need feedback:

• Core contributor work scope definition: draft document up for review
• Kubernetes collaboration discussion: meeting scheduled for yesterday (Tuesday Jul 26th) - the recap and recordings of the meeting have been posted in that forum thread.

@Sarina Canelake

@maria - let’s work together on getting some of the course stuff defined that you were asking about

@mgmdi and @sarina will be discussing the plans for the onboarding courses.

@Kyle McCormick

The backporting process is pretty convoluted, especially when it involves adding a patch to Tutor.

@Peter Pinch

We seem to have run into a lot of issues with nutmeg and database configurations. Perhaps this is inevitable with the migration from mongodb to mysql, and the fact that our table character sets, etc. may not be in sync with edx.org. I am concerned however that tutor users have reported similar issues, e.g. Emoji in subsection title not supported since Nutmeg - #3 by pdpinch

@Andrés González

The migration process from older versions, especially from native to Tutor, is complex and problematic

For these three, there seem to be a common thread: the need to better support larger or more custom instances of Open edX, when they differ from the main Tutor use case. This is also something which we run into during the Kubernetes collaboration discussion. CC @kylesinlynn @pdpinch @Andres.Aulasneo @regis

@Jill Vogel

|My other client work is taking up all my brain space at the moment, so I’ve found it hard to make time for CC.

@jill As long as the average number of hours matches the commitments and there is no deficit build up, I think we have generally agreed that it’s fine to have variations of availability over time – ie you can do more one month, and then less the next month. Some of the work might be guided by more specific requirements, for example with dealing with production/master issues, or the maintenance/upgrade of specific code bases, as maintainers.