kiwix / metrics Goto Github PK

• Title should be "Time to solve"
• Y axis legend should "Average tickets lifetime (days)"
• Colors should be like in chart "Backlog size"
• Same bars as "Backlog size" should be used".

I got this error :

2019-12-31 17:40:08 > 2019-12-31 16:40:05,843 - grimoire_elk.elk - ERROR - Error enriching ocean from cocom (https://github.com/kiwix/tools): 'message'
2019-12-31 17:40:08 > Traceback (most recent call last):
  File "/usr/local/lib/python3.5/dist-packages/grimoire_elk/elk.py", line 672, in enrich_backend
    enrich_count = enrich_items(ocean_backend, enrich_backend)
  File "/usr/local/lib/python3.5/dist-packages/grimoire_elk/elk.py", line 452, in enrich_items
    total = enrich_backend.enrich_items(ocean_backend)
  File "/usr/local/lib/python3.5/dist-packages/grimoire_elk/enriched/cocom.py", line 223, in enrich_items
    rich_items = self.get_rich_items(item)
  File "/usr/local/lib/python3.5/dist-packages/grimoire_elk/enriched/cocom.py", line 183, in get_rich_items
    eitem['message'] = entry['message']
2019-12-31 17:40:08 > KeyError: 'message'

with theses repository :

• https://github.com/kiwix/web
• https://github.com/kiwix/tools
• https://github.com/kiwix/kiwix-tools
• https://github.com/kiwix/kiwix-lib
• https://github.com/kiwix/apple

I see no reason for that. Maybe it should just be removed

What is the value of keeping this view?

Is evaluate with the last value (last closed issue), but change with time !!

KPIS:

• Size of the backlog (number of tickets with the status open, differentiation of label "bug" from other)
• Number of tickets opened and closed
• Size of of code base in lines with (differentiation per language)
• Number of lines commited (differenciation per contributor)
• Number of code contributors/committers (in the last period)
• Average to ticket time to solve (differenciation bugs from others)
• Number of ticket participants
• Number of releases (in the last period)

Remarks:

• All the stats are over time (period of 1 days or 1 month, ...) in x axis.
• This KPIs are global (all openzim+kiwix repos together), but each KPI should be computable for one or many selected repos.

25 november

Allow to add new "visualisations" in docker image (needed for new KPIs)
Allow to init Overviews panel on container creation from a config file
Create a new "overview" panel with first KPIs:

• Size of backlog
• Number of tickets opened and closed
• Average to ticket time to solve
• Number of added line & removed lines

9 december

Integrate Graal to docker image
Add the KPI "Size of code base in lines" to owerview panel

16 december

Add other KPIs :

• Number of code contributors/committers
• Number of ticket authors
• Number defined tags

23 december

Allow to easily use the panel interface to choose differentiation :

• code language
• label (bug, enhancement ...)
• organisation (kiwix/openzim)
• contributor
• period

https://github.com/chaoss/grimoirelab-graal is a Generic Repository AnALyzer for Grimoirelab. He uses among other things coloc or lizard tools.

The actual docker don't include the Graal integration but a first version of this integration is proposed as a fork here (see docker subdirectory) based on the work of inishchith at Google Summer of code 2019.

Graal integration allow to add a new dashboard to show metric :

• Total line of code (LOC)
• Total line of comment
• Total number of function
• Code complexity
• Comments per LOC
• LOC per function
• Statistics on file extension

we adding github backlog study code in forks of grimoirelab-elk and grimoirelab-sirmordred. We need to integrate code in official repos or add a patch.

It should have Kiwix and openZIM

If I show a chart only over the last two years, the current value is around 500 but if I configure the chart to look over the past 5 years then it show around 1000 tickets. This has to be wrong, it should always display the same amount of ticket with the status open at a certain date.

We can bypass this bug by saved the dashboard on an other name

We have:

• C++
• C/C++/C#

I want only:

• C/C++

Current chart default period seems to be last two years. I think last 12 (a year) should be better in an attempt to reduce the number of of information and focus on the essential.

In the graph the last value down

A simple manual verification shows that numbers are understimated

User : admin
Pass : admin

Many charts have one of these problems:

• Not unit
• Underscores in label

There is never more tickets closed than opened. This is really strange... in particular if you consider that at the same time the overall number of tickets might decrease!?

I have configured HTTPs on Sloppy and restart the container... and now no content is available at all.

To add studies in grimoire-elk, I modified files in grimoire-elk repos, then I have fork this repos. To use this fork in docker file, I must to use the build_grimoirelab modified script and re-build full docker image. We choose to rewrite our own Dockerfile instead a Dockerfile based on grimoirelab/full image.

• Legend should be "opened" and "closed"
• Colors should be the same as on Github for an open (green) and closed (red) ticket
• Y axis legend should be "Number of tickets"
• I want things displayes in a form of curves
• A third "ratio" curve in black should show the opened - closed (so can be negative)

?

favicon should be the one of Kiwix
Title should be something like "Kiwix development metrics"

• Size of backlog is absolutely stable
• "Time to solve" and "Evolution of open tickets" are empty

When I select a file extension, no filter is apply on cocom graph (e.g. number of line)

Add "project" field (Organization is a alias of project field) in the Cocom index

svg or png. That would really help to share charts. Would Kibana allow such an option? We have exports in CSV already.

A picture is worth a thousand words, they say:

Also, we've been solving a lot more tickets recently (particularly on android) which should mechanically drag that average down. But not create a trough.

This is totally missing (in place we have other charts, but this is not what was required).

• For bugs (tag "bug")
• For others (non-tag "bug")

Data have to be wrong. With such a ratio between "open" and "closed", we would not have any ticket more to open anymore.

On Metrics.kiwix.org I'm currently looking at the Size of backlog chart and I have no idea what 600 is. But we're between it and 500.

We can edit/add files in /usr/local/lib/python3.5/dist-packages/panels/json

for the last 6 days!

Git backend of GrimoireELK do not set the "tags". We need to modify it to allow to create the new visualization " Number defined tags".

Copy item['data']['defs'] to eitem in grimoire_elk/enriched/git.py:get_rich_item

• Swift
• ObjectiveC

On start of the container, Kibiter ask default index. We must define git on creation of the docker container

In the Size of Backlog chart:

• Cool: I can zoom in on a particular date range by simply clicking on the chart.
• Uncool: there is no button nor indication to zoom out.

• Title should be "Size of codebase"

• Put "Total lines of code" un fourth position after "Average time to solve"

• Colors should come from https://docs.servicenow.com/bundle/istanbul-performance-analytics-and-reporting/page/use/reporting/image/BarChart.png

• Languages should be proper "Java", "C++", "Kotlin"

• Most common languages should be at the bottom

• Comments should not be counted (=deducted to the total number of lines) (but I don't want it to appear in the chart)

• Chart should be of type "area"
  

The numbers are more realistic now. Here a re few things I would like to do:

• Make it first in the list (top left)
• Title should be "Number of open tickets"
• Color for bugs should red (like in https://docs.servicenow.com/bundle/istanbul-performance-analytics-and-reporting/page/use/reporting/image/BarChart.png)
• Color for enhancement should be blue (like in https://docs.servicenow.com/bundle/istanbul-performance-analytics-and-reporting/page/use/reporting/image/BarChart.png)
• Bugs should be at the bottom and other at the top.
• Legend should be "bugs" and "others"

Then we should be good I guess with that chart.

Like required

For example:

• HTML
• JSON
• XML
• Markdown
• CSS

Kibana settings : histogram:barTarget seem work (set to 20), but histogram:maxBars has not effect.

issue already reported here : elastic/kibana#14823

Not part of the requirements

To support filter by label, we need to enhance backlog studie : compute the average for each repos and for Bug and Enhancement label.

As a label can be defined multiple times, we need to define priority : if Bug and Enhancement are define, considere is Bug.

It seems the default duration of any point on the X axis is not optimal. Charts display a lot of points/bars because this point (duration) is really short. This is difficult to read the charts because of this.

It seems to display a day (even if I believe this an aggreate of values over many days). I don't think having more than 20-30 values on the X axis makes a lot of sense. To me depending of the overall period selected, we should display days/weeks/months smartly (but maybe we choose have somehow a chooser)? Or do we have an alternative approach?

This might cause clutter if the tool is looking at all Kiwix/Openzim repos, but right now I don't know what these numbers are for on the landing page.