Transcript and summary (automated, via Otter)
As gathered from https://app.transifex.com/open-edx/edx-platform/dashboard/ , please refer the continuously updated table at https://openedx.atlassian.net/wiki/spaces/COMM/pages/3157524644/Translation+Working+Group#The-following-is-a-a-table-of-lanague-that-are-supporetd--last-updated
Time (in min) | Item | Presenter | Notes |
|---|---|---|---|
5 | Review language performances |
| |
20 | -Status of OEP-58 and transition to from edx-platform project to openedx-translations project - what is the timing? -If it takes another release then MFE’s need to be shifted to the edx-platform project -Leverage translation memory to ensure smooth transition (strings should be added as reviewed in the migration) -Aspen strings are embedded in the openedx-translations project only. -for Quince, work out of the Quince Release project, for Redwood, openedx-translations project -will run a sync today between edx-platform and openedx-translation project | Please provide update on when to transition to the openedx-translation project completely - the Communication MFE was not part of the edx-platform project for (MFE’s only part of the OEP-58 project are being impacted) example: Reference: https://github.com/openedx/wg-coordination/issues/107#issuecomment-1878633711 | |
20 | Simlink strategy - Please update entry for your dedicated languages - what about browser languages such as en.MX | Relevant doc: https://docs.google.com/spreadsheets/d/1u4pR98IB0ukyCW_fhNSm4kfosddmy_LKQtjXji_0_-M/edit#gid=0 | |
15 | Open Q&A |
|
|
Outlined here: https://github.com/orgs/openedx/projects/50/views/2