Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

...

Coming up next

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

Anchor
future
future
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.

...