Task #1836
closeddashboard maintenance
100%
Description
For the dashboard we need to maintain it
Details TBD
Related issues
Updated by Florian Effenberger over 8 years ago
- Status changed from New to Feedback
Updated by Florian Effenberger over 8 years ago
Contract signed, which contains training for infra staff
Tentatively only as soon as the dashboard is delivered
Updated by Florian Effenberger over 8 years ago
- Assignee changed from Alexander Werner to Christian Lohmaier
- Target version changed from Q2/2016 to Q3/2016
Re-assigning to Cloph due to the infra changes
Updated by Florian Effenberger over 8 years ago
- Status changed from Feedback to In Progress
Updated by Florian Effenberger about 8 years ago
- Status changed from In Progress to Feedback
- Target version changed from Q3/2016 to Q4/2016
Currently arranging proposals on the date, so we can proceed
Updated by Florian Effenberger almost 8 years ago
- Subject changed from dashboard maintenance and feedback to dashboard maintenance
- Description updated (diff)
- Assignee changed from Christian Lohmaier to Guilhem Moulin
- Target version changed from Q4/2016 to Recurring
Updated by Florian Effenberger over 7 years ago
- Status changed from Feedback to In Progress
- Priority changed from Normal to High
Adding this to Guilhem's pile as part of his regular software maintenance
Guilhem, if there's anything missing, any information you need to get in order to regularly update the dashboard software, please let me know :-)
Updated by Florian Effenberger over 6 years ago
Out of curiosity, when was the last update installed? Are we up to date?
Updated by Guilhem Moulin over 6 years ago
Last upgrade (excluding ES & MariaDB) is from 1 year ago. There is an upgrade pending; at FOSDEM Italo said he'd put me in touch with the Bitergia folks so we could sync, but I forgot to poke him during the last calls.
Updated by Florian Effenberger over 6 years ago
Would be good then to sync with Italo, so we don't miss important
upgrades and bugfixes :)
Updated by Florian Effenberger over 6 years ago
Did you manage to get in touch with them through Italo?
Updated by Florian Effenberger about 6 years ago
Florian Effenberger wrote:
Did you manage to get in touch with them through Italo?
Ping?
Updated by Guilhem Moulin about 6 years ago
Italo put me in contact indeed (on May 15). We want to migrate the G-ELK stack from vm167 to vm213 (fresh Stretch VM that uses the new baseline) and “un-dockerize” the setup; tentative plan is to look at this with Brett during LibOCon, cf. infra call minutes.
Updated by Guilhem Moulin about 6 years ago
- Related to Task #2612: Replace all instances of pie charts in the Dashboard with more appropriate charts added
Updated by Guilhem Moulin about 6 years ago
- % Done changed from 0 to 90
We deployed from scratch a new dashboard, available at http://vm213.documentfoundation.org . It's based on native (non-docker) Elasticsearch/Kibana 6.1, the most recent GrimoireLab tools, and some custom (homemade) patches. I'll replace https://dashboard.documentfoundation.org tomorrow or so; and afterwards close this ticket, which has no raison d'être IMHO, especially not at "high" severity. Maintenance of the dashboard is now taken care of like any other manual deployment, and since Redmine, Jitsi, Etherpad, etc. have no assigned tickets, G-ELK shouldn't either.
The new dashboard shows extra metrics which might be useful:- "Git Demographics": attraction/retention of new developers
- "Git Areas of Code": which part of the project is the most often modified, what it is (filetype), where (directory), etc.
- "Community Structure" analysis: "onion model" analysis of core/regular/casual contributors, cf. Bitergia's blogpost https://blog.bitergia.com/2018/06/19/the-onion-model-analyzing-community-structure/
- Mediawiki (pages in the default namespace only); email addresses aren't accessible from the API so contributors' identities are currently not merged with the ones from git/gerrit/bugzilla
Updated by Florian Effenberger about 6 years ago
and afterwards close this ticket, which has no /raison d'être/ IMHO,
especially not at "high" severity. Maintenance of the dashboard is now
taken care of like any other manual deployment, and since Redmine,
Jitsi, Etherpad, etc. have no assigned tickets, G-ELK shouldn't either.
Fine for me, and thanks for taking care of this! :)
Updated by Guilhem Moulin about 6 years ago
- Status changed from In Progress to Closed
- % Done changed from 90 to 100