2025-03-13 Meeting notes

By Kyle McCormick
2 min

All public Working Group meetings follow the Recording Policy for Open edX Meetings

 Date

Mar 13, 2025

 Participants

  • @Feanil Patel

Previous TODOs

 Discussion topics

Item

Presenter

Notes

Item

Presenter

Notes

Previous TODOs

 

  •  

Meeting Times?

 

  • We’ll move the meeting 1 hour earlier starting next week but leave all the timings in UTC to continue to check in on whether or not that makes sense as the makeup of the group changes.

Metrics of Maintenance Health we should start thinking about

 

  • What are other metrics we should be thinking about to assess maintenance health?

    • Times since last comment for a PR or Issue

    • Age of PRs and Issues

    • Some of this data is in bitergia today.

    • We want to be able to provide this to maintainers.

    • The WG group will also probably want to look at it periodically.

  • Focus on responsiveness from the maintainers first, if the can look at issues and PRs then we can provide more goals and action items for them after that.

  • Recommendation to make just one specific maintainer oriented dashboard. We can slowly add to it as we want the maintainers to focus on more things so we won’t overwhelm people.

FYI on an update to OEP-55

@Kyle McCormick (I’m on PTO, but @Feanil Patel can answer questions)

  • https://github.com/openedx/open-edx-proposals/pull/691#issuecomment-2715080941

  • tl;dr:

    • Before: Any maintainer (individual or group) needed to have CC write access to the repo.

    • After: Individual maintainers still need t CC write access. But when a group is acting as the maintainer, we only require that 1 member be a CC with writ access.

  • This will help facilitate cases where a team wants to jointly maintain a repository. As long as 1+ team members have the expertise and ability to merge PRs, then that is A-OK.

Distributing Small Maintenance Tasks

 

  • Have maintainers do this work where possible.

  • Have maintainers-at-large do this for all repos that don’t have a maintainer.

Code styles and linting

@Robert Raposa

Mostly edx-paltform, but partly across entire platform.

I picked up review for https://github.com/openedx/edx-platform/pull/36177 and had some questions.

 

@Awais Qureshi

I have a questions one about this issue https://github.com/openedx/edx-platform/issues/36184 . Need some clarity from Axim about which apps qualify for this task .

  • Feanil will take this back to Dave and Kyle for further discussion and clarification.

 

 

 

 Action items

@Feanil Patel @Sarina Canelake Sync up to figure out how we would use Bitergia to provide the right dashboards for maintainers.
Recommendation to make just one specific maintainer oriented dashboard. We can slowly add to it as we want the maintainers to focus on more things so we won’t overwhelm people.
@Feanil Patel Add a maintainers-at-large slack group to coordinate maintenance work.
@Feanil Patel Ticket adding catalog-info.yaml files to all un-maintained repos with openedx-unmaintained as the owner. This ticket can be worked on by the maintainers-at-large.

 Decisions

Related content