2022-12-01 Frontend Working Group Meeting Minutes

\uD83D\uDDD3 Date

01 Dec 2022

\uD83D\uDC65 Participants

📹 Recordings

\uD83D\uDDE3 Discussion topics

Time	Item	Presenter	Notes
	Action items		There weren’t any to check up on, this time. (See next item, though.)
5 minutes	Sprint reviews	Adolfo	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.
8 minutes	Going Async	Adolfo	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.
7 minutes	Olive MFEs update	Adolfo	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?
3 minutes	MFE Modular Domains OEP	Adolfo	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
7 minutes	Modular Web Analytics	Adolfo	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
10 minutes	React upgrade	Jeremy	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
10 minutes	Dealing with Information Overload	Adolfo	Adolfo explains how he deals with notification overload: Hiding channels with no unread messages on Slack Using Github Notifications page instead of email and the refined-github browser extension
5 minutes	edX platform-core roadmap	Jeremy	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.

✅ Action items

Adolfo will start creating meeting notes in the Wiki for better discoverability
Adolfo will add issues from the platform-core FED-BOM view to the Frontend Dev board
Adolfo will start using #wg-frontend as a nexus of frontend-related communication, bringing attention to issues, PRs, forum posts, etc, and pinging the right people where necessary.

⤴ Decisions

The Frontend Working Group will start using asynchronous channels of communication more, in particular the #wg-frontend Slack channel, with the dual goal of making meeting attendance optional, but also making meetings more like meetups: less frequent and more interesting.