5 mins | Arch coordination required (MFE extension options) | @Glib Glugovskiy | We want to extend new learner records MFE (credentials IDA) with new functionality for VC. I have found draft OEPs, but not sure about a generic approach for extending MFEs. OEPs: https://github.com/openedx/open-edx-proposals/pull/259 https://github.com/openedx/open-edx-proposals/pull/287/files Chris Deery: Our team owns it, so talk to me about the MFE! Feanil: Adolfo is also someone else to pull into the conversation–he took over those OEPs when David Joy went on leave. Brian links:
For event bus messaging between Studio and Credentials, start talking with Arch-BOM. Robert Raposa is the right person to reach out to. |
30 mins | Feedback on | | *Ned: Slack is for words in flight, not words at rest. Do people see these messages reliably? Feanil: Thought is that if you’re following a specific subject area, you’re probably paying attention to that part of the Slack ecosystem more than most people. For the small level of change impacting some parties, you might miss this, and that’s okay. Depends on what the impact is. Ned: Perennial question, “which of these channels work”? Robert: How to find out the specifics if the specifics are different? Whether that’s connected to a particular topic in backstage… How do I know what to listen to? Robert: What are the types of announcements that we’re talking about? Questions vs. Proposals communicated differently? Ned: Another level of detail that might clarify: this is about an announcement. But this could just be “hey, look at this thing over there for details”. Where should the details go (probably one place), while the announcements go to many places. Questions vs. Proposals Robert: Can we have examples of good announcements, to highlight the different types of announcements? So people know it’s not just proposals, things that are done, etc. Feanil: Added “Examples of Different Announcements” table at the bottom of the doc so we can start collecting these. Andy: My concern is about training if people expect things to be in once place and they are in another. Feanil: If it’s only impacting a specific repo, it probably doesn’t have wide arch impact that requires announcement. Andy: Jira might be appropriate for things that impact a single repo, e.g. when repos don’t use issues.
Alex: what if your wiki page had like...a summary. and you copypasta the summary into the announcement Everyone agrees this is a good idea Feanil: adding this as part of the guidelines, that your details page should have a summary that can be copy-pasted everywhere.
Ned: Potential rituals concern: Core Contributors Meetup is listed in 3/4 rows, but people often don’t go to them–it’s turned into a scrum of scrum of working groups. Robert: Discuss has a top level announcements category. Some notes on when/if/how the difference between the announcements category and the fact that we’re announcing makes sense. OEPs specifically get announced in a particular place. Consensus is that the doc is good enough to send out and iterate on.
|