Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

\uD83D\uDDD3 Date

...

\uD83D\uDC65 Participants

Recording

...

Video:

...

Chat:

...

, time, location

\uD83D\uDDE3 Discussion

...

Time

...

Item

...

Presenter

...

Notes

...

20 mins

...

Deprecated code removal from edx-platform

...

Muhammad Abdullah Waheed Khan

...

  • Account, profile, and some ecommerce pages

  • Breakages at 2U:

    • An internal template override (for a reverse() url) broke edx-platform

  • Should we announce before removal? Or should we add it to a planned release?

    • Could it have been caught by CI?

      • No, because it is an internal override

    • Should we support this kind of override in the first place?

      • Probably not.

    • We should just follow OEP-21, but since it’s taken so long for this particular DEPR ticket, an announcement in the forum would be corteous

    • Also, since edx-platform doesn’t have a proper CHANGELOG, make sure to flag commits with BREAKING CHANGE or !, and that will help the release notes author noticing it.

...

20 mins

...

React router upgrade issues and future plans

...

Muhammad Abdullah Waheed Khan

...

  • Should we announce these changes? How?

    • Yes if it’s a deprecation: see previous entry.

  • We should be test any frontend changes against Tutor, where applicable. The upcoming sandboxes project will help with this.

...

20 mins

...

Pluggability catch-up

...

Adolfo Brandes

...

Catching folks up on the Pluggability discussions.

...

(For next meeting)

...

Renovate auto-rebase?

...

Adolfo Brandes

...

Do we need Renovate to auto-rebase stale PRs? (See frontend-platform.) It’s generating a lot of noise (because maintainers aren’t doing anything about them). (Slack thread.)

✅ Action items

  •  Adolfo Brandes will bring the Tutor sandbox testing discussion to Axim Engineering: will we be able to use sandboxes to avoid Tutor-compatibility issues?

topic(s)

One, maybe two topics to be presented or discussed in depth in the upcoming meeting.

🎥Recording

Info

Please be advised: Frontend Working Group meetings are recorded and transcribed.

  • Video:

  • Chat:

  • Transcript:

\uD83D\uDC65 Participants

The list of participants, tagged if they’re registered in Confluence.

🤖 Summary

A summary of the meeting, usually generated from the transcript by an LLM.

✅ Action items

  •  

⤴ Decisions