2023-06-05 DevEx Meetup Notes

Jun 5, 2023


Please be advised: DevExp Working Group meetings are recorded.

Link: https://axim-org.zoom.us/rec/share/d0hNaZd-9EBmhrQdoUIuCqMWVLko9uyn4GC0jXjhYbdHGiZkYWedKF_OIDaWNH8-.vrs3gqMy7aXwPn73


Meeting captain: @Rebecca Graber

Notetaker: @Kyle McCormick

  • @Diana Huang

  • @Pierre Mailhot

  • @Emad Ehsanrad

  • @Jeremy Bowman

  • @Maria Fernanda Magallanes Z

Discussion topics





Start the Zoom recording!


Demos, Scheduled Topics

@Kyle McCormick : Repo checks

  • Goal is to help developers and project leads/issue triagers

  • We have ~200 repos with lots of little differences

  • A repo check is something to ensure is true about a repository

  • repo_checks command line tools lets you execute checks as dry runs or as active fixes

  • Right now Axim runs it, but anyone can submit a PR and #ask-axim for review

  • Recent check: Ensure Labels

    • labels are inconsistent between repositories (“bug ” vs “bug” vs “ bug”)

    • goals is to have a consistent set of labels/colors, loaded from a labels.yaml file in the repo-tools repo

  • Q: How does this compare with Repo Health Checks (used by 2u)?

    • A: @Feanil Patel knows more. There is definitely more emphasis in repo_checks on fixing the inconsistencies rather than just reporting them. Repo health dashboard data is also currently not visible outside 2u. There’s also some crossover with backstage.

Cross Pollination

  • Tools/features/opportunities

  • Tips and tricks

  • Roadmap news

@Jeremy Bowman

@Diana Huang

  • Still nailing down issues with Apple Silicon and local development around MFEs.

  • 2U is still focused on devstack work and fixes vs. Tutor.

@Kyle McCormick

  • @Brian Smith is continuing to work on tutor-mfe support for running MFEs on the host (devstack style). Current challenge is around mismatched host names (localhost:xxxx vs apps.local.overhang.io:xxxx). He’s looking into a couple solutions/workarounds there.

  • xmodule_assets removal is ongoing, @Andrey Cañon Jimenez is reviewing. Latest series of PRs will remove all Python processing from xmodule SCSS. https://github.com/openedx/edx-platform/issues/32292

@Emad Ehsanrad


  • Each challenge should have a follow up action.

  • If you have an idea for follow up actions, add it.

  • Or if you aren’t sure, leave it blank.

  • We’ll discuss all actions either way.

  • @Rebecca Graber - devstack whackamole. Some issues are reproducible, some less so, some are only reproducible in certain contexts, and everyone seems to be using their own set of documentation

    • I am getting an M1 so hopefully that will help compare things between intel and silicon

    • much of it is edx-platform as much as devstack but it’s often hard to tell

  • @Kyle McCormick Devstack dissuades removal of containers (dev.remove-containers, formerly dev.down) which is usually a performance win, but container removal is an important part of isolating issues and is still much better than a full destroy.

    • Possible documentation update: reminding people to remove-containers before destroying as a step in troubleshooting


  • DevExp wins!

Suggested Action Items

Last Time:

@Rebecca Graber add dev data epic to DevEx board

This Time:

@Kyle McCormick review Jeremy’s doc, add details about Tutor changes in Palm
@Maria Fernanda Magallanes Z start with https://github.com/openedx/wg-developer-experience/issues/79

Look at the board

The board: https://github.com/orgs/openedx/projects/37/views/1

Top-level initiatives: https://github.com/openedx/wg-developer-experience/issues/1