Contents
Table of Contents | ||||||
---|---|---|---|---|---|---|
|
Todos
- Define purpose of this page: Is it “how to contribute” or is it general “documentation”
- Define target groups: User, Developer, Implementer, Academia?
- Define general structure for each target group
- Helpful media: YouTube
- Remove Target audience brackets
...
Would you like to use the software? [User]
Do you have problems using openIMIS? Please have a look in the http://docs.openimis.org/en/latest/ / http://docs.openimis.org/fr/latest/
Did you encounter a bug in the software? Please report it to our Service Desk
Training / YouTube
Would you like to implement the software? [Implementer]
Understand openIMIS
For general questions please check out our FAQ List
If you want to explore openIMIS or show it to someone else you can use our Demo server
Implementing openIMIS
You don’t know where to start? Check out the Generic Implementation Starter Kit
Are you missing a feature? Make a proposal at our Service Desk
Would you like to develop the software? [Developer]
Download the software source code
Latest release notes in the change log of the repository of each component in Sources
Reporting and Issue tracking
Contribute to the source code by following the Extended Github workflow
Would you like to know about the Initiative and join? [General]
Contribute to our Thematic Areas
Would you like to use the software for teaching purposes? [Academia]
...
Resources
Zielseite: Documentation
openIMIS Product
(Sources Page for Release 2021-10 is missing)
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 Implementers
openIMIS Development
openIMIS Community
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
...