Contents

openIMIS Wiki Spaces

openIMIS Product

• Demo server / Sandbox Landscape

• Releases

  • Release 2022-04

    • Sources Release 2022-04

  • Release 2021-10

    • (Sources Page for Release 2021-10 is missing)

    Release 2021-04

    • Sources Release 2021-04

• Installation guide

  • Requirements

    • Connectivity & theoretical infrastructure required

    • Resource requirements

    • Infrastructure security

  • Generic Implementation Starter Kit

  • Installation Guide

  • Configuration (choosing Modules)

  • Localisation / Translation Management platform

  • Customization (configuring/extending Modules)

  • Import tools

  • “How to migrate from Legacy to Modular” ↔︎ (see Modular Migration: Open Issues )

  • Training / YouTube

• Architecture

  • Use cases served by openIMIS - overview

  • Target Technology Stack / (new) openIMIS installations

  • Modular Transformation / openIMIS Modules/ Target (modular) Architecture / https://docs.google.com/presentation/d/1eUqlOkK6MyTPZsQG3A8mZDzoIvFxzUtxi5r6UCVYYjc/edit#slide=id.g1192d288ca2_0_65 (slide 12)

    • The JLN Process Matrix

    • JLN Process - OpenIMIS Mapping

    • Dependency Graph for Modules / repos

  • openIMIS Database Design

  • openIMIS Integrations

  • /wiki/spaces/SB/pages/3244916739

• Software Development

  • code and publishing management

    • Version management

    • Contribution guidelines

    • UI/UX Style Guide

    • Extended Github workflow

    • Updating all python modules CI github workflow

    • “Automated CI testing" of code and publishing management

    • Repository management (http://github.com / http://npmjs.com / http://pypi.org

  • Developer Starter Kit

  • Quality assurance

    • Testing

    • Security assessment template

  • Training / YouTube

• Service Desk

  • Issue tracking

  • JIRA reports

• Licenses

openIMIS User

• FAQ List

• http://docs.openimis.org/en/latest/ / http://docs.openimis.org/fr/latest/

• Training / YouTube

openIMIS Implementers

openIMIS Development

• Product Roadmap

• Product Incubator

• Opportunities

• Project Portfolio

• Shared resources

openIMIS Community

• Meet our partners

• Governance

• Implementations

• Communication

Background

Todo

• Empathize - Research Your Users' Needs to build a product that is relevant for people
• Goal: Enable users to use the product “openIMIS” by providing easy access to information (and contribution?)
• List users of openIMIS as a product
• Examples (End-User, oI Coordination-Desk / Product Owner, oI Maintainer, Funder, Software Developer, Scheme-Operator (CEO), Scheme-Implementer (CIO/CTO), )
• List Target Groups (Personas - https://www.interaction-design.org/literature/topics/personas )
• Name, Age, Foto, Occuptation, Location (totally fictional of course)
• Why are we interested in them / Why are they interested in us
• Goals (What does the person want to archieve by using our service?)
• Behaviours (What else does the person do?)
• Priority (Primary and (supporting) Secondary)
• Quality Check Personas
• Whos responsibility are they?
• What overlaps do exist?
• Do we consider special needs (accessibility, disabilities, demographic differences) ?
• Assign 1-2 primary personas and some secondary personas to each entitity of the following structure - Describe every entitiy with one or two sentences that could appear on their start page
• Webpage
• Wiki
• openIMIS Product
• openIMIS Development
• openIMIS Community
• “openIMIS User”
• Consider testing of the structure e.g. by getting user feedback

Questions

• Should we have Target-Group-specific Top-nodes?

  • Aren’t there any overlaps?

  • Every top-node would need to explain it’s specific purpose on its main page