\uD83D\uDDD3 Date
\uD83D\uDC65 Participants
\uD83D\uDDE3 Discussion topics
Time | Item | Presenter | Notes |
---|---|---|---|
15 min | Working together async | Ideation around working together asynchronously
| |
5 min | Open edX Conference talks! | Special guest stars | Have you pulled together your conference proposal yet? Send it in! |
5 min | Upcoming RFP | We hope to announce a request for proposals to move forward the work on using redis streams as an alternative message bus to Kafka. Preliminary work is outlined in this issue, but the exact scope and milestones are not yet defined. This would likely be a fairly large chunk of funded work. I’ll update the WG when the RFP gets posted! 🤑 | |
10 min | Tracking Log, Caliper, xAPI Event Lifecycles | Some new events were added with the Discussions MFE, which is great! However it’s hard to know where to look for guidance on how to work with events. Naming, documenting, who to notify when changing, how to version, deprecating… these are all thorny issues that we should find a way to communicate to developers. Several OEPs cover pieces of the puzzle, but I think this group should work towards a central document that we can link to and share. I wrote this issue in the hopes of addressing this, but haven’t had time to work it. Is it sufficient? What would you like to see as an event author or consumer? |
✅ Action items
- Everyone should think about proposals to present at the Open edX Conference in March!
- Brian Mesick to ping the WG in Slack and Discuss when the Redis Streams RFP goes out
- Igor Degtiarov to post in Discuss about how we can better handle events when moving to MFEs as that has been a particular pain point
- Brian Mesick to post on the Mongo / Citus / Clickhouse data backend spikes, present at the next WG meeting
⤴ Decisions
- We are going to try to lean toward having more discussions on Discuss when possible