Date: 2026-08-25

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)

• GIZ

  • Kelvin Twum Abrokwah Uwe Wahser Zaki Syaiful Hunafa Zikani Nyirenda

• Speedykom Group

  •  

• m4h , Y-Note , Tinker Technologies

  • Sunil Parajuli

• Swiss TPH

  • Dragos Dobre Patrick Delcroix

• World Bank

  • Wei Lu

• SolDevelo

  •  

• https://openimis.atlassian.net/wiki/spaces/SB/pages/697139258

• module landing pages were moved to main wiki: openIMIS Modules

• 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)

  • looking into options to add hierarchies / sub-menues into the openIMIS menues

  • solution builder & releases

    • Solution Builder is an application that takes parameters for building solution

    • Solution building team will build solutions based on last release as a test for the solution builder, this will result in Docker images like release/26.04-solution-name

  • Full process for solution building:

    • need list of module (where is the reference ? )

    • menu (optional, else derive from module list)

    • seed-data: roles, …

• need to update all of the involved instances (sync with external 3rd part tools)

  • Interoperability Sandbox

• need all the repos - also external & private repos

•  

https://openimis.atlassian.net/browse/OP-2851

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

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

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

• Patrick Delcroix to clearly document how to use solution builder:

  • source of truth for configuration - what should & should not be manually updated (e.g. openimis.json, module configuration in admin interface etc), and

  • data flow - how does config flow from which github repo to frontned/backend, wiki generation etc, and

  • provide the how-to URL link in the wiki landing page for each solution

• Patrick Delcroix to fix aggregated doc:

  • heading: rename “Aggregated doc” to be something more readable

  • fix user manual hierarchy

• Patrick Delcroix to fix the CoreMIS solution demo server deployment

• Wei Lu to have UX designer review & finalize CoreMIS solution menu

• Wei Lu to create a PR for https://openimis.atlassian.net/browse/OP-3077

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 - Anthony Belem to provide testing data for performance/load testing

• 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 -

• https://github.com/openimis/openimis-fe-insuree_js/pull/180