2026-07-07 Developers Deep Dive Call - Projects
Overview
Date: 2026-07-07
Time: 15:00 am (UTC)
Room: https://meet.jit.si/openIMISDevelopers - kindly indicate your name and organisation (jitsi claims to support Chrome, Chromium & MS Edge and Firefox browsers only. You might also want to try the jitsi app)
Participants: (kindly only add your own names, not those of other participants)
@Kelvin Twum Abrokwah @Uwe Wahser
@Zikani Nyirenda
m4h , Y-Note , Tinker Technologies
@Sunil Parajuli
@Patrick Delcroix @Dragos Dobre
Agenda:
When | Duration | Who | Topic |
|---|---|---|---|
15:00 am | 15 min | Agenda | |
15:15 | 10 min |
| |
15:25 | 10 min |
| |
15:35 | 10 min | @Zikani Nyirenda | next steps vite migration |
15:45 | 10 min | @Uwe Wahser | menu structure, io-sandbox documentation, module landing pages |
Meeting Note
Overarching
https://openimis.atlassian.net/wiki/spaces/SB/pages/697139258
openIMIS PSQL image use postgres 13 which is old and not supported by Django 5; database image are not compatible between version 13 and 14 (minimum for django 5) meaning it will require a data migration by the implementer; it means
we need to run test on psql 13 and 14 (or latest) to test against regression
Inform implementer (after we have some confidence it works) to update their postgres version to 14 (or latest that works)
Plan migration to Django 5 or 6 (latest possible, risk of missing modules with too recent version) in 27.04 or 27.10
Solution Building
https://github.com/openimis/openimis-be-core_py/pull/432 required to stop using roles upon creating Officer/ClaimAdmin
https://openimis.atlassian.net/wiki/spaces/SB/pages/5220368387
please verify the module pages
we’ll also create an overview list for QA with the excel sheet
Interoperability Sandbox
need to update all of the involved instances (sync with external 3rd part tools)
need all the repos - also external & private repos
Vite-Migration
Step | Description | Milestone | PRs |
|---|---|---|---|
I | (T1) PRs needed to complete the vite migration | 2026-07-16: vite migration is completly in dev-branch | tag: "vite-migration" (count: 9) |
II | (T1) PRs with high priority to stabilize the dev-branch | 2026-07-15: dev-branch is reasonably stable again | tag: “next-release” (count: 32) |
III | (T1 + devs) PRs with fixes & additions before / during vite-migration need to be rebased or recreated | 2026-08-30: identified PRs from cra to vite | tag: “cra-needs-rebasing” (count: 42+) |
IV | (T1 + devs) verify PR’s from current projects (solution building & sandboxing) that may still need be re-classified / prioritized | 2026-08-30: all needed project PRs are selected for the 26-10 | github by T3 & T4 project authors (count: 147) |
V | (T1) PRs for Release 2026-10 need to be identified and listecd in the Jira epic for 26-10 | 2026-09-11: All release relevant PRs are included in the release package | JIRA-epic: “OP-2851” (count: 102) |
!!! Anything that is not in V by 2026-08-30 will not be in the next release !!! | |||
Module Landing Pages
Action Items
Presentations
Questions
Attachments
Additional Resources