There weren’t any to check up on, this time. (See next item, though.)
I’ve been doing frontend community project management using the Frontend Dev board. I pinged a bunch of people yesterday, merged and reviewed a bunch of issues. I’ll be doing this every two weeks.
After talking to @Kelly Buchanan and the rest of the tCRIL team, I’m proposing we try to use #wg-frontend as much as we can for this group’s business, so that eventually (but not immediately) we can reduce the frequency of meetings and make them more interesting. We could have meetings once a month or two, where we do show-and-tell or discuss technology, rather than only talking about specific issues.
I (Adolfo) will also be the go-between the rest of the frontend community and 2U, by bringing attention to important forum or github topics in the Slack channel. Hopefully it’ll make for a reasonably active channel that make joining Frontend WG meetings totally optional.
Olive MFEs update
Going down the Matrix:
All those MFEs except Learner Record are looking good for inclusion in Tutor/Olive
Learner Record: depends on Credentials, so we can’t include it
Ora Grading: depending on fix that has yet to be reviewed
Discussions: depends on backports to edx-platform, also needs review
Course Authoring: pretty much in already
Authn: Missing reply in this thread: should we wait for the refactor?
MFE Modular Domains OEP
Being worked on by @Adolfo Brandes and @Adam Stankiewicz
Discovery work to be funded by tCRIL; bidder selection is ending, so it should start soon
Modular Web Analytics
We need a solution for Google Analytics by July 1, 2023
The linked issue lists some options, but we’ll probably want to go with Option 2: using the analytics interface already implemented in frontend-platform to create a GA plugin
Sharoz says Segment’s API, which is already implemented in frontend-platform, is very similar to Google Analytics', so this shouldn’t be difficult to do
React 16 will be out of support soon, we need to start thinking about upgrading to 17, then 18
Jeremy will create a template for how to deal with these upgrades, which will include ways to make it easier to coordinate the work across the several maintaining teams at 2U and elsewhere
Adolfo will be able to help via the Frontend Dev board sprint updates, every two weeks
The Support Windows spreadsheet is still a thing! We’ll want something like it focused on the frontend.
Dealing with Information Overload
Adolfo explains how he deals with notification overload:
edX platform-core roadmap
Jeremy shows us where to track FED-BOM’s current and future work.
Adolfo notes this is close to what the Frontend Dev board tracks, and most tickets are gladly already on it. The platform-core board will be a great source to pull issues from (and into the Frontend Dev board), in any case.