...
openIMIS Product
Sources Release 2022-04
Sources Release 2021-10
Requirements
Configuration (choosing Modules)
Localisation / Translation Management platform
Customization (configuring/extending Modules)
“How to migrate from Legacy to Modular” ↔︎ (see Modular Migration: Open Issues )
Training / YouTube
Architecture
Modular Transformation / openIMIS Modules/ Target (modular) Architecture / https://docs.google.com/presentation/d/1eUqlOkK6MyTPZsQG3A8mZDzoIvFxzUtxi5r6UCVYYjc/edit#slide=id.g1192d288ca2_0_65 (slide 12)
Dependency Graph for Modules / repos
Software Development
code and publishing management
“
Automated CI testing
" of code and publishing managementRepository management (http://github.com / http://npmjs.com / http://pypi.org
Testing
Training / YouTube
Service Desk
openIMIS User
http://docs.openimis.org/en/latest/ / http://docs.openimis.org/fr/latest/
Training / YouTube
openIMIS Development
openIMIS Community
...
Update and Integrate Installation and Country Localisation into Documentation
Update Installation and Country Localisation to allow newbies to quickly setup the current version
Clean up naming: “modular” is default case and doesn’t need to be especially designated as such for the purpose of Documentation , “legacy” is special case, its content need to be updated/removed/archived to reflect the new reality - E.g. in Installation and Country Localisation - This also needs to be reflected in documentation within the (GitHub) repositories
Update and Integrate Generic Implementation Starter Kit into Documentation
Update Resource requirements
Integrate further mature/non-development content into Documentation
Describe Configuration/Customization (per module) in Documentation ↔︎ Dev Committee #288
Update Demo server to latest version (currently 1.1.3)
Jira Legacy server System JIRA serverId 97d38f4a-4cd9-3563-900d-60c9290b47f4 key OSD-179 Document versioning - How to maintain a visible “main version number” and organize versions for modules while inter-module-compability can be understood
Create “How to migrate from Legacy to Modular” in Knowledge Base https://openimis.atlassian.net/wiki/spaces/OP/pages/3286204427 (see Modular Migration: Open Issues )
Cleanup Quality assurance and Document Testing Scenarios ↔︎ Dev Committee #223
Update and Integrate openIMIS Integrations into Documentation
Update and Integrate Sandbox Landscape into openIMIS Product
Update and Integrate Translation Management platform into Documentation
Cleanup and Integrate JIRA reports into openIMIS Product
Cleanup and Integrate Issue tracking into openIMIS Product
Update and Integrate Use cases served by openIMIS - overview into Documentation
...
Update Developer Starter Kit for Release 2022-04
Update Installation guide for Release 2022-04
Create “Technical Requirements” page and fill with content e.g. Connectivity & theoretical infrastructure required
Cleanup and Integrate code and publishing management into Documentation
Update Version management
Update Contribution guidelines
Update Extended Github workflow
Integrate Updating all python modules CI github workflow into Knowledge Base https://openimis.atlassian.net/wiki/spaces/OP/pages/3286204427
Integrate “
Automated CI testing
" of code and publishing management into Knowledge Base https://openimis.atlassian.net/wiki/spaces/OP/pages/3286204427
Update YouTube content for Release 2022-04 / current development ↔︎ Dev Committee #176
...
How to document architecture: Graphics: repository for architecture etc done with draw.io
Re-organize first level children of Documentation e.g. create and move content into Knowledge Base https://openimis.atlassian.net/wiki/spaces/OP/pages/3286204427 as “How-to”
Cleanup and Integrate further mature/not-in-development content into Documentation
Standardize naming in Knowledge Base https://openimis.atlassian.net/wiki/spaces/OP/pages/3286204427 “How to” etc. …
Standardize naming in openIMIS Product substructure explicitely “openIMIS” everywhere or nowhere
...