Date: Thu, 28 Mar 2024 09:21:35 +0000 (UTC) Message-ID: <1280022973.91.1711617695447@0e604bd9f8c9> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_90_897535097.1711617695447" ------=_Part_90_897535097.1711617695447 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Leads: Rich, Ashraf
Rapporteur/Notetaker: Darius
Notes from Session: (audio recording failed)
Karl: I'd like to see over the next 6 months, that "2.0" becomes the mas= ter upstream branch for development. And having the "eLMIS" in bitbucket ma= kes things a lot harder.
Rich: Right now, 2.0 is not really "upstream", and we all want it to be.=
Ashram: Once VIMS is released (later this year, or next year) then we ca= n put resources into shifting from bitbucket to github.
Rich: Current state: 2.0 is not releasable (e.g includes incomplete feat= ures)
Karl: Have a separate repository with Moz-specific configuration. Going = forwards, we should have a default/demo configuration and feature toggles t= hat disable features not yet complete.
---------------
* Different configurations for R&R, with different calculations ("R&= amp;R Templates")
* Different groupings within an R&R
* Reports
* Checks status of equipment before certain orders (and requires explana= tions for broken equipment)
* Dashboard on home screen (role-specific)
* uploading of photos from an android application (ODK)
* integration with RapidSMS gateway
* GIS map
* ILS gateway
-------
= (Ashram: some database tables are there as proof of concept and are great = examples of things to "clean up")
Have a default/demo config (following github.co= m/clintonhealthaccess/lmis-moz pattern)
Evaluate TW customization module