Topic | Presenter | Meeting notes | ✅ Action Items |
|---|
| Peter Pinch | | |
Follow-up - Open edX Survey Report | Jorge Londoño | Ed proposed the idea of a campaign to encourage community engagement when the new feature is ready for rollout Xavier mentioned the need for more channels to reach out to the broader community, such as an opt-in banner or news section on all Open edX instances. Ali mentioned an upcoming beta testing program project to involve users in the development process and decision-making. Ali asked about the incentives for users to participate in beta testing, to which Ed responded that users get to be part of the steering committee and have their voices heard. Xavier emphasized the importance for betatesters of getting privileged access to decision-makers, and becoming a reference among colleagues.
| |
Follow-up - How do we make sure strings in frontend-app-communications are sent to Transifex? (and frontend-app-course-authoring, and frontend-lib-content-components that is using it) These are included as official in Olive. The message are properly handled in the code, but they are not being pushed to Transifex. FE App Component is another issue, it is not tagged as it’s a library. There’s also a bug for this library that needs to be address. Adolfo Brandes has context on this issue and will investigate. Related bugs and Slack threads:
| Pierre Mailhot | Not fully discussed during the meeting as Pierre Mailhot was not present, but the topic was brought up in Slack. There seemed to be a blocker on the availability of Atlas for Quince, but it now seem available: https://github.com/openedx/frontend-app-communications/pull/156 | |
Follow-up - MFEs for Quince | Adolfo Brandes | Additionally, Adolfo said that the MFE will be the first to use Atlas in a release, with the help of Brian, Omar, and himself. They are also planning to introduce a plugin architecture for the MFE, with details to be finalized in the coming months. The team is still working on these projects, so it's not guaranteed that they will be ready for the Quince release.
| ✅ Adolfo Brandes mentioned that he, Brian Smith and others, are working on fixing the learner dashboard MFE, which should be ready for Quince. |
Outdated MFEs | | | |
MFEs documentation & reviews | Adolfo Brandes Peter Pinch | Adolfo mentioned that there is a list of requirements for an MFE in the wiki, which is being used to check the Learner dashboard against. Xavier raised the point about new MFEs review for documentation, proposing that there should always be a reviewer caring about the documentation when a new MFE repository is introduced. Adolfo outlined the current process for introducing a new MFE: It includes a long-lived ticket with requirements (example) and an implicit review process. He suggested that the ownership of these issues could be better handled by someone more product-focused, as they could coordinate translation efforts and features. The ultimate test for a new MFE is through BTR, where a plugin is made for the MFE and added to the Test Plan.
Adolfo expressed concerns about the current process of preparing for releases, noting that the workload becomes too heavy in the last two weeks before release and that the PR comes only a couple of weeks before release. Adolfo suggested that this could be improved by having a single owner for each new MFE to help coordinate efforts. Xavier and Ali discussed the possibility of assigning a product review ticket for each MFE, and review/assign it as part of the product working group meeting triage. Ed suggested that it probably wouldn’t fit well with the product working group, as it’s often not product decisions. Instead, Ed suggested it would be beneficial to have of a group of front-end architects (including Adolfo, but not just Adolfo), who would be focused on questions about MFEs. Adolfo mentioned the need to decide on whether a given MFE would be included in a release, and the group agreed that this should be a product decision.
The difficulty can also be to know about new MFEs early enough, they are often worked on separately before being brought to the project. Xavier asked if there were ways to detect them automatically, which seem difficult. Ned revealed there are three repos in the Edx Github organization that start with 'front end app,' one of which is private, and agreed to investigate for Adolfo.
Adolfo suggested having an action item for owning and pushing for new MFEs and other features, and Ali agreed to bring this up in the group on Thursday. Angie proposed a standardized process for developing MFEs, including criteria for identifying the owner of each MFE and the skills needed for its development. Ed emphasized the need to separate product requirements from technical implementation and suggested that product changes should be decided based on their efficacy.
| ✅ Ali Hugo will bring up the topic of ownership for pushing new MFEs (or features in general) with the product working group ✅Ned Batchelder (Deactivated) will be investigating the 3 repos in the edX Github organization that start with 'front end app,' one of which is private, and let Adolfo Brandes know the outcome.
|
Frontend summit | | Given the summit’s outcome, Xavier asked how we would prevent multiple implementations from persisting. Adolfo clarified that no decisions were made at the summit and that attendees were assigned tasks to propose unified solutions for all discussed use cases. Braden and Kelly's teams have proposed course authoring and learner dashboard solutions respectively. Adolfo stressed the need for further exploration and development of these proposals, aiming to unify the Learner dashboard to address most of the discussed use cases. There will be an iterative approach developing the general direction of the learner dashboard. Ed emphasized the significance of having operational code and testing it in production, which everyone agreed upon regarding requirements. Adolfo made it clear that they were not working towards Quince but for the following release, Redwood, intending to achieve version 1.0 of the architecture or Plugin API within six months. The team also emphasized the need for caution to prevent multiple implementations of the project.
| ✅ Braden MacDonald and Kelly Buchanan's team have proposed course authoring and learner dashboard solutions respectively, and will be aiming to unify their approaches. |
Product & UX meetingLast core contributors update: “The Paragon Working Group would like to get members of the Product Working Group (and others in the community) more involved in UX discussions. This will allow individuals outside of 2U, not only to keep tabs on design updates, but also to help guide the design of Open edX. The idea is to start a cross-functional meeting for context/knowledge sharing around design. Anyone interested in getting involved?” Previous core contributors update: Discussions about setting up a betatester program
| Ali Hugo | Discussion postponed to next meeting (out of time) | |
Product reviews & discussionsPrevious core contributors update: “It is still hard to get more contributors involved in the product conversations in a timely manner.” | Jorge Londoño | Discussion postponed to next meeting (out of time) | |
New named release manager rolePlease take a look at a proposed new CC role (comments end 10 Nov): https://discuss.openedx.org/t/potential-new-cc-role-access-named-release-manager/8588 | Sarina Canelake | Discussion postponed to next meeting (out of time) | |
Maintainer phase 3 - Looking for maintainers | Xavier Antoviaque | Discussion postponed to next meeting (out of time) | |
Async working group updates - News sectionAdding a news section to all working groups wiki pages to facilitate building the summary: https://openedx.atlassian.net/wiki/spaces/COMM/pages/3768188929/Contributor+Coordination+Working+Group?focusedCommentId=3894607915 | Xavier Antoviaque | Discussion postponed to next meeting (out of time) | |