Bitergia will go for Kibana (which is just the visualization layer, there is a simplified software stack behind compared to the current stack behind korma.wmflabs.org), and the software stack currently behind korma.wmflabs.org will go into maintenance mode.
To see Kibana, there is a test instance at http://s.bitergia.com/db-mediawiki-gerrit and http://s.bitergia.com/db-mediawiki-git which is for general purpose testing and does not have the specific stuff we have. https://kibana.bitergia.com/xen/app/kibana#/dashboard/Time_Focused_Dashboard is an actual example of a dashboard with a bunch of panels.
Kibana is based on indexes, coming from Differential, Gerrit, Git, Differential (once a backend has been created, see {T118753}) etc.
If Wikimedia went for Kibana, panels, indexes and widgets need to be created based on Wikimedia's needs and what Wikimedia has in korma. (TODO: Creation should be way simpler and more standardized then for korma.)
We (@AKlapper, input from @QGil welcome) need to discuss in order to evaluate and to provide feedback to Bitergia:
** What are Wikimedia's most critical/important/used panels/pages in korma.wmflabs.org?
** Which parts are "nice to have"?
-----
First round by @AKlapper:
=== What those symbols mean: ===
✔ = Exists in Kibana (e.g. by applying filters)
✖ = Shrug / we don't care --- potentially discuss
✚ = Wanted in Kibana, or need to check whether exists in Kibana --- make sure they exist (check; file tasks; etc)
=== General remarks: ===
* ✖ I don't care about Countries data: incomplete and we don't care/use it currently
* ✔ Sources (e.g. list of repos, lists, etc) are always a panel in Kibana
=== Pages and panels on korma.wmflabs.org (to be updated): ===
* SCM
** Overview
*** ✔ Commits (per month)
*** ✖ Authors vs. New Authors (per month) | It is unclear what "new" authors are. We are more interested in SCR here and " [[ https://wikimedia.biterg.io/app/kibana#/dashboard/Git-Demographics | Demographics > Last Attracted Developers ]]" widget exists.
*** ✖ Files (changed per month)
*** ✖ Lines added vs. Lines removed
*** ✔ Authors (30d, 365d, TT)
** ✔ Contributors (also allows filtering per repo)
*** ✔ Authors (per month)
*** ✔ Authors (30d, 365d, TT)
** ✔ Organizations
*** ✔ Commits per org; authors per org
*** ✔ Commits / Authors per org per month
** ✖ Countries
** ✔ Repositories
*** ✔ Commits per repository / Authors per repository
*** ✔ Commits / Authors per repo per month
* SCR
** Overview
*** ✚ Pending reviews | TODO: We want the "Total open" and "CR0" only and "CR+1" only
*** ✔ Backlog of open changesets (monthly snapshots) per month (also ∃ under KPI: Overview) | [[ https://wikimedia.biterg.io/app/kibana#/dashboard/Gerrit | "Changesets per status" widget on "Gerrit" ]] exists but is per week.
*** ✚ Distribution of open changesets (by date of submission) per month | there was "Reviews by opening time" in Kibana but cannot find it in 09/2016 anymore; [[ https://wikimedia.biterg.io/app/kibana#/dashboard/Gerrit-Delays | Gerrit-Delays ]] offers two "Changesets Open..." panels but likely not "by date of submission"?
*** ✚ Age of open changesets (monthly snapshots) per month (also ∃ under KPI: Overview) | TODO: Not existing but [[ https://wikimedia.biterg.io/app/kibana#/dashboard/Gerrit-Backlog | Gerrit-Backlog ]] has "Backlog: NEW Changesets waiting to be Closed" (number of open changesets per week they were created) and "Backlog: Accumulated Days waiting to be Closed" (I don't fully understand the latter)
*** ✚ Age of open changesets by affiliation (monthly snapshot) per month | TODO: Are these two mergeable in one panel (via filters) in Kibana?
*** ✔ submitted vs. Merged changes vs. Abandoned per month (also ∃ under KPI: Overview) | [[ https://wikimedia.biterg.io/app/kibana#/dashboard/Gerrit | "Changesets per status" widget on "Gerrit" ]] exists but is per week.
*** ✚ Code review users vs. Code review committers per month | TODO: Missing, we want to see that ratio
*** ✖ Total reviews received by Patchsets vs. Total sent patchsets per month
*** ✚ People uploading patchsets vs. Reviewers per month | TODO: Missing, we want to see that ratio to know if we need more people with +2 rights
*** ✔ Openers (30d, 365d, TT) | Covered by stats on uploaders above.
*** ✔ Submitters (30d, 365d, TT) | Covered by stats on reviewers above.
** Contributors
*** ✔ Code review users; Code review committers (per month) (also ∃ under KPI: Overview)
*** ✔ Code review users; Code review committers (30d, 365d, TT)
*** ✔ Code review committers (TT, per past quarters)
** Organizations
*** ✔ submitted and Merged changes per org per month | [[ https://wikimedia.biterg.io/app/kibana#/dashboard/Gerrit | "Changesets per status" widget on "Gerrit" ]] exists and filter per org can be applied but is per week.
*** ✔ Reviews merged / Merged changes per org per month (WMF weight) | [[ https://wikimedia.biterg.io/app/kibana#/dashboard/Gerrit | "Changesets per status" widget on "Gerrit" ]] exists and filter per org can be applied but is per week.
*** ✖ Orgs per quarter / TT
** ✖ Countries
** ✔ Repositories
*** ✔ submitted vs. Merged changes per repo | [[ https://wikimedia.biterg.io/app/kibana#/dashboard/Gerrit | "Changesets per status" widget on "Gerrit" ]] exists and filter per repo can be applied but is per week.
** Backlog
*** ✚ Oldest open Gerrit changesets without code review | TODO: [[ https://wikimedia.biterg.io/app/kibana#/dashboard/Gerrit-Backlog | Kibana's "Backlog > Backlog" widget ]] lists //any// open patches regardless of CR status (e.g. https://gerrit.wikimedia.org/r/#/c/186610/ is included on 2016-11-21 which is CR-2); plus has [[ https://phabricator.wikimedia.org/T146893 | bugs ]]
*** ✚ Oldest open Gerrit changesets by organization without code review | TODO: See previous item; are these two mergeable in one panel (via filters) in Kibana?
*** ✖ Open Gerrit changesets with most activity | We don't use this data currently
* ✖ defunct Bugzilla | (drop all; maybe turn into static HTML for folks who care)
** ✖ Overview
** ✖ Contributors
** ✖ Organizations
** ✖ Countries
** ✖ Trackers
* Maniphest | TODO: All blocked on {T138002}; re-evaluate after T138002 is fixed
** Overview
*** ✚ Closed tickets vs. Opened tickets (per month)
*** ✚ Closers vs. Openers | TODO: Nice to have, half-covered by "closers" but do we also have "openers"?
*** ✖ "Efficiency closing tickets" | What is this?! Let's drop.
*** ✔ Closers: 30d, 365d, TT
** ✔ Closers
*** ✔ Closers: 30d, 365d, TT
** ✖ Trackers | drop, it's only one source
*** ✔ Closed tickets & Closers per Tracker
* ✖✔ Mailing lists
* ✖✔ IRC
* ✖✔ Wiki
** ✖✔ Those sections all follow "Created items"; "Most active people in certain time frame"; etc pattern. Low priority and mostly available in Kibana.
* Studies > [[ http://korma.wmflabs.org/browser/demographics.html | Demographics ]]
** ✚ TODO: No "direct" retained vs. attracted exist in [[ https://wikimedia.biterg.io/app/kibana#/dashboard/Git-Demographics | Git-Demographics ]]? - Would be nice but not a hard blocker.
* ✔ Data sources | see [[ https://wikimedia.biterg.io/app/kibana#/dashboard/Data-Status | Data-Status panel ]]
* ✖ Metrics definition | TODO: Explanation of terms; could be on-wiki docs in T132323
* More links:
** KPI: Overview
*** (✖✔) Age of open changesets (monthly snapshots): Time from last patchset in days | see above under SCR
*** (✖✔) Backlog of open changesets (monthly snapshots): Open changesets waiting for review | see above under SCR
*** (✖✔) New changesets submitted per month | see above under SCR
*** (✖✔) Active Gerrit code review users per month | see above under SCR
** (✖✔) KPI: Who contributes code? | covered above already under SCR>Contributors
** ✚ KPI: Gerrit review queue > Ranking of repositories; sorted by oldest median age of unreviewed changesets. | TODO: Worst offenders; hence we want this: {T151488}
** ✚ KPI: Code contributors new and gone > New + first patch(es) + Leaving + last patch: {T151161} (process how to use data within WM to be further discussed/handled in T137214)
*** ✖ People Intake: Number of people with 1 submission, 2-5 submissions, 6-10 submissions. | Interesting but not used; needs more thought and maybe better data representation format.
** ✖ KPI: Maniphest response time: 20 tickets for: Longest time without action; without comment; without resolution | Some of this could be queried in Maniphest; in any case Andre does not consider this data helpful. Median response time per project or such could be more interesting, to deal with underlying problems instead of single tasks listed here. (Plus patches always await a response. Tasks do not necessarily.)
** ✖ Top contributors > Ranking | We do not use this data currently. If anyone wants to keep it, good arguments and a better algorithm are needed. We can already filter for the past 12months who uploaded patches and filter out orgs like WMF and WMDE.