\uD83D\uDDD3 Date
\uD83D\uDC65 Participants
📹 Recordings
🔄 Github Issue
\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. |
7 minutes | Olive MFEs update | Adolfo | Going down the Matrix:
|
3 minutes | Adolfo |
| |
7 minutes | Adolfo |
| |
10 minutes | React upgrade | Jeremy |
|
10 minutes | Dealing with Information Overload | Adolfo | Adolfo explains how he deals with notification overload:
|
5 minutes | Jeremy | Jeremy shows us where to track FED-BOM’s current and future work.
|
✅ 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.