Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[GitHub] Add study to create a "backlog" index #761

Closed
florentk opened this issue Jan 14, 2020 · 6 comments
Closed

[GitHub] Add study to create a "backlog" index #761

florentk opened this issue Jan 14, 2020 · 6 comments

Comments

@florentk
Copy link
Contributor

With the current Github enriched datas, we have the backlog only from actual data, we have not the evolution. For example we have not the evolution of the number of opened issues or the evolution of average issue resolution time. We can compute these metrics in add a new study index based on Github enirched datas.

We have implement this in a fork of grimoirelab_elk for the dev of Kiwix metric. Are you interested in including it as a pull request ?

@jgbarah
Copy link
Contributor

jgbarah commented Jan 14, 2020

Thanks a lot, this is quite interesting!

For this kind of stuff, we usually write an specific "study", which is a way of producing a "special" index (such as the one we write for the "areas of code" panels). This way, we keep the core of GrimoireELK reasonably simple, while we can have those optional studies performed as a part of what SirMordred does.

@valeriocos, @sduenas do you agree this would be the best approach to integrate this code? Do you have any pointer to studies, so that @florentk can consider if it makes sense in this case?

@alpgarcia
Copy link
Contributor

Related to chaoss/grimoirelab-sigils#410

@valeriocos
Copy link
Member

Thank you @florentk for sharing your work. I'll have a look at it tomorrow.

@florentk
Copy link
Contributor Author

@valeriocos Do you have look my proposition ? Can I change something to integrate my code in a branche of your repository (is the best way for us !)

@valeriocos
Copy link
Member

Hi @florentk sorry for the late reply! Yes, I had a look to your fork and the approach looks ok!
Could you submit a PR with the study? There, we can comment on some details of the study, WDYT?

Thanks and sorry again!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants