Project

General

Profile

Task #1836

dashboard maintenance

Added by Florian Effenberger over 2 years ago. Updated about 17 hours ago.

Status:
Closed
Priority:
High
Category:
-
Target version:
Team - Recurring
Start date:
Due date:
% Done:

100%

Estimated time:
Tags:
URL:

Description

For the dashboard we need to maintain it
Details TBD


Related issues

Related to Infrastructure - Task #2612: Replace all instances of pie charts in the Dashboard with more appropriate chartsClosed

History

#1 Updated by Florian Effenberger over 2 years ago

  • Status changed from New to Feedback

#2 Updated by Florian Effenberger over 2 years ago

Contract signed, which contains training for infra staff
Tentatively only as soon as the dashboard is delivered

#3 Updated by Florian Effenberger about 2 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

#4 Updated by Florian Effenberger about 2 years ago

  • Status changed from Feedback to In Progress

#5 Updated by Florian Effenberger almost 2 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

#6 Updated by Florian Effenberger almost 2 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

#7 Updated by Florian Effenberger about 1 year 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 :-)

#8 Updated by Florian Effenberger 7 months ago

Out of curiosity, when was the last update installed? Are we up to date?

#9 Updated by Guilhem Moulin 7 months 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.

#10 Updated by Florian Effenberger 7 months ago

Would be good then to sync with Italo, so we don't miss important
upgrades and bugfixes :)

#14 Updated by Florian Effenberger about 2 months ago

Did you manage to get in touch with them through Italo?

#15 Updated by Florian Effenberger 29 days ago

Florian Effenberger wrote:

Did you manage to get in touch with them through Italo?

Ping?

#16 Updated by Guilhem Moulin 29 days 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.

#17 Updated by Guilhem Moulin 5 days ago

  • Related to Task #2612: Replace all instances of pie charts in the Dashboard with more appropriate charts added

#18 Updated by Guilhem Moulin 1 day 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

#19 Updated by Florian Effenberger about 21 hours 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! :)

#20 Updated by Guilhem Moulin about 17 hours ago

  • Status changed from In Progress to Closed
  • % Done changed from 90 to 100

Also available in: Atom PDF