Overview

Date: 2025-02-24 - 14:00 (UTC)

Room:

Objective: Project updates and indepth discussions

Participants: (kindly only add your own names, not those of other participants)

• GIZ

  • @Uwe Wahser

  •  

• World Bank

• m4h , Y-Note , Tinker Technologies

  •  

• Swiss TPH

  • @Patrick Delcroix

• Speedykom Group / Jembi

  •  

Agenda:

Minutes

Admin Stuff

m4h - Project: 2024.T4 Interoperability Sandbox

• no updates

Swiss TPH - Project: 2024.T3b Solution Building

• no updates

Questions / AOB

• Test server for vite & MUI migration is now available

  • tickets on Jira for end-to-end testing code chages set up in JIRA: https://openimis.atlassian.net/browse/OP-2811

• Tasklist / list of modules for Vite Migration & Material UI

  • https://openimis.atlassian.net/browse/OP-2809

  • Budget planning: https://docs.google.com/spreadsheets/d/1x3jLnMRJX_SdHUy2wFP9CydqLrt_78xbO9hoVXV74dg/edit?gid=0#gid=0

  • vite test-server: https://vite.s1.openimis.org/front/

• Test results WB-UX:

  • WB UI/UX looked at the vite migration branch and created a document here:  https://docs.google.com/document/d/12WK-wjyYy7I_VpzJizO7R8GZHUBeJfHz/edit  

    • Used a traffic light system to indicate criticality of issues

  • The following items were highlighted, though the community needs to read the full document to understand all the issues in detail.

    • Was finding difficult to add individuals to groups, it was noted within internal WB team that the error is happening in release server

      • The bug was found in current existing Material UI on release server and may exist on vite server too

    • When attempting to upload new benefit plans/programs got Error 500 on current version and blank screen on vite version

    • Template that needs to be uploaded in cash transfer module for the vite migration was not working, it works in release server

  • It was observed that failure to create Program will cause failures in other use-cases, and so the maintainers have to make sure it is possible to create Programs in both environments (release server, vite server) to ensure UI/UX person can test the rest of the use-cases that require program to exist.

  • Next steps:

    • Patrick to fix critical issues and deploy to vite server

    • Tabby to verify and re-try modules that were unable to be checked

    • What will be in the next release? Release 2026-04

      • Conditional cash transfer with timesheet-based payment

      • no migration related: vite&mui migration will be pushed to R.2026-10

      • end-to-end testing already

    • To minimize the merge conflicts caused by branch drift/diversion, let's merge vite branches to develop as soon as 26.04 release goes out

Presentations / Attachments

Additional Resources