Content
Agenda
Review and delete finished Work Items
Review Findings in Checklist for Release 2022-10
Discuss Future Improvements and agree on next Work Items
Work Items
- STPH: Document list of steps aligned to phases on Release 2022-10 into Checklist for Release 2022-10 and restructure the checklist accordingly
- Necessary steps for “Preparation and Deployment” are documented and up-to-date (deliverables, pull-requests, version control & tagging, package manager, testing, staging, configuration, update release documentation, update architecture documentation, update sandbox landscape, etc)
- STPH: Lead discussion of version management → Developer Committee
- STPH: Installation Guide (Video) / One-Click-Install / Step-by-Step-Instructions
- Merge existing YT playlists openIMIS Installation and Country Localization Session 1 +2
- French version of Docker Installation
- Update Installation and Country Localisation to focus on “Modular” (put “Legacy” at the end)
- Rewire/reembedd youtube content for modular installation
- CD/Blqr: Review https://www.youtube.com/playlist?list=PLWKJKsJBiT3L2QHj1DwoXsl6CplZI2M2J Up2date?
- STPH: Fix findings for Release 2022-04
- Sources Release 2022-04 Double entry of repository https://github.com/openimis/openimis-fe-tools_js“FE French Translations” and “FE Tools”
- Sources Release 2022-04 Link to package manager of “FE French Translation” is broken
Coming up next
- Agree on Checklist in Checklist for Release 2022-10
- Integrate Checklist for Release 2022-10 in Release 2022-04 and prepare clean copy of the checklist for Release 2022-10
- Get an overview of Youtube-Content (up2date? helpful? misleading?)
Questions
- How do we keep the version (link) of every component in Sources Release 2022-04 in sync with every component’s “Release notes” page (e.g. openIMIS Database release notes) as well as with what is actually in the repository?
- How can we define “Epics” that represent better the added value (see mismatch between Release 2022-04 Epics and Highlights)?
Future Improvements
- Dedicated page for each module under openIMIS Modules (with Page Properties, descriptions/basic explanation, version history - Based on release notes pages?)
- Clarify wording module / component / repository - Define and document for example “Claim AI” from different perspectives - “Claim AI” Module contains the Components “Claim AI BE” and “Claim AI FE” “?
- openIMIS Feature: One-Click-Installation with selection of modules instead of installing components one by one / Define Standard-Installation
- Rethink grouping of components on Release 2022-04 according to Modules ->
- Include repository info instead of redundancy (and info gaps) between Release notes and repositories on GitHub (PlugIn?)
- Clarify usage of Pypi.org and npmjs.org with GitHub (calcrule links to GitHub, others to PyPi)
- Update Installation Guides (Docker and Non-Docker)
- Dependency Graph for modules / consistent dependency information in Sources Release 2022-04
- Reevaluate “Testing openIMIS” on Sources Release 2022-04
- Consider “Legacy” modules as “Deprecated” on Sources Release 2022-04
- Sort components by name on Sources Release 2022-04?
- Release 2022-04 Reevaluate redundant information in “Highlights” and “Release Notes”
- Combine Releases / Release 2022-04 , Release notes and Sources/Sources Release 2022-04 to reduce structural redundancy and confusion
- Clarify wording redundancy “openIMIS …” for components, modules, wiki pages, etc.