Draft: Resolve "Complete the information about KPI requirements"
Closes #3 (closed)
Merge request reports
Activity
assigned to @SpickerHZB
added 1 commit
- 7e3d1caf - Collection of already existing information as a draft and starting point for the discussion
KPI_general_requirements.md 0 → 10064423 * number of shares, 24 * storage 25 * Gitlab: 26 * active users 27 * active projects 28 * number of CI jobs 29 * number of Merge Requests 30 * Mattermost 31 * daily active user 32 * number of users per week in average 33 * number of teams 34 * number of chats 35 * Zammad 36 * number of new tickets 37 * b2share 38 * number of new publications - Comment on lines +9 to +38
Is this list a list of minimally required KPIs from your/CM side or is this merely a documentation of what's currently available (status of few months ago)?
If the latter, I'd prefer to remove this list from here and refrain to corresponding lists in the respective service kpi projects.
If the first is the case, it should be headlined as such, something like "Minmially required KPI per service" or similar
Actually, it is a draft that I wanted to work on further.
When we started in the summer, we didn't know what KPIs were available. When we contacted the providers, we made a list with some examples. These lists were the source for this draft.
The next step would be:
- What do the service actually send as KPIs?
- These KPIs shall replace the current list and will be the minimum for future services of the same kind.
- Together, they are also an indicator for new services.
- Are there universally valid KPIs that can be sent by all services? (e.g. number of users)
- These would be the general minimum KPIs
Also not solved is the question, how to link or connect this list with the existing read me
added 1 commit
- 30374f5d - move overall requirements to unified (README.md) file
added 1 commit
- 8fcd9dae - remove notification, as it is not necessary when regularly triggering ci pipeline