2026-08-18 Developers Deep Dive Call - Projects
Overview
Date: 2026-08-18
Time: 15:00 am (UTC)
Room: 
Jitsi Meet - 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 Zaki Syaiful Hunafa
m4h , Y-Note , Tinker Technologies
Agenda:
When | Duration | Who | Topic |
|---|---|---|---|
15:00 | 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
module landing pages were moved to main wiki: openIMIS Modules
Solution Building
https://openimis.atlassian.net/wiki/spaces/SB/pages/5220368387
check module to solution bundle: https://docs.google.com/spreadsheets/d/1oJ-SKI6F2LuEd6WCMVTMcqYy6Eo7k2CpJ4sauqWyBUY/edit?gid=1647117087#gid=1647117087
sample for listing modules in a solution bundle: Solution Bundle: CORE-MIS (Cash Transfer)
test script generated to create filters for the module selection per solution bundle page
Interoperability Sandbox
need to update all of the involved instances (sync with external 3rd part tools)
need all the repos - also external & private repos
most instance-pages were created - Sunil will do the AeHIN webinar
Bug-Fixing
https://openimis.atlassian.net/browse/OP-2851
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: 0 (was 9) |
II | (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: 89 (was 147) |
III | (T1 + devs) verify 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: 0 (was 42+)) |
IV | (T1) only PRs with a high reasonable quality to not de-stabilize the dev-branch (includes ‘regression’ PRs) | 2026-08-30:
| tag: “next-release” (current count: 42) |
V | (T1) PRs for Release 2026-10 need to be identified and listed in the Jira epic for 26-10 for prioritization.
| 2026-09-11: package will be the basis for the UAT | JIRA-epic: “OP-2851” (count: 106 (was 102)) |
!!! Anything that is not in V by 2026-08-30 will not be in the next release !!! | |||
Action Items
Please help with reviewing PRs based on which repositories you are interested in (e.g. everything that’s in the CORE-MIS solution bundle). You can monitor pull requests which are very likely to be accepted soon by filtering to the label next-release. However, this will give you a list of all the repositories you can add an additional filter with only the repositories that you are interested in by adding a clause on the repos and save it as a view: (repo:openimis/openimis-fe-claim_js OR repo:openimis/openimis-be-claim_py). Check out the example filter string for the previous claim example: https://github.com/pulls/search?q=is%3Apr+is%3Aopen+org%3Aopenimis+NOT+%22Bump%22+in%3Atitle+label%3Anext-release+sort%3Aupdated-desc+%28repo%3Aopenimis%2Fopenimis-fe-claim_js+OR+repo%3Aopenimis%2Fopenimis-be-claim_py%29
payroll requests PRs will be included - need to be tested by worldbank
polygamous PRs is migrated to vite, can be intgrated, but willl be difficult to test during UAT because it needs to be configured
include as silent feature - this will still make it easier for new implementations
user business acces -
Presentations
Questions
Attachments
Additional Resources