Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Date

06-02-2021

Attendees

Discussion items

Time

Item

Who

Notes

30 mini18n of back-end error messages (ad hoc conversation)
  • Julian Ladisch's institution has allotted him some time for UXPROD-371 (i18n of error messages received from APIs); even though it is not highly ranked overall it is crucial to a select audience. His initial foray led to STRIPES-750, which some front-end devs discussed, concluding that backend modules should be responsible for providing localized text in their responses given an Accept-Languages header in the requests they receive.
  • Depending on whom you ask, English-only responses from APIs constitute a bug (some UI devs see it this way) or an unimplemented feature. 
  • If this work is pushed to the back-end, there are implications for other teams, i.e. it's not as simple as saying "Julian can implement this in mod-foo" because mod-foo may forward a response from mod-bar, etc. (NB: the work won't be isolated to a single module on the front-end either).
  • Next steps:
    • present UXPROD-371 before the TC (goal: ask for the conclusions reached in STRIPES-750 to be accepted or rejected; Zak Burke )
    • present an initial proposal for handling l10n on the backend (goal: ask for endorsement of the proposal; Julian Ladisch )
    • make sure we invite Peter Murray , who is wise in the ways of Lokalise. md331 (Deactivated) notes that there were many bumps on the road to building a successful integration.
5 minfuture agenda items
  • i18n before a full audience, with an agenda and materials to review ahead of time

future agenda items
  • System and tenant level users are becoming an increasingly urgent problem. There was a recent discussion at Tech Leads. See also the spike FOLIO-2551 and Decision Log entry.