Creating Quality models using GrimoireLab and CHAOSS metrics
Project Abstract | Discussions | Pull Requests | Weekly Updates | Links
Check out my blog or follow me on Twitter for more updates.
GrimoireLab is a powerful open-source platform that provides support for monitoring and in-depth analysis of software projects. It produces a rich set of dashboards, which can be easily inspected by decision-makers to help them understand the evolution and health of their projects. Despite the large set of dashboards available in GrimoireLab, comparing projects between each other is not straightforward since it requires navigating and drilling down the data in different dashboards.
Prosoul is a web application that empowers decision-makers with the means to create and manage their own quality models, which are useful means to evaluate and compare software projects. This project idea is about supporting the definition of Quality Models using GrimoireLab data and Prosoul.
The main aim of the project is to design an approach to shape the GrimoireLab data in a format that can easily be consumed by Prosoul and implement it on the data obtained from a few data sources like git, github and mailing list repositories to obtain simple quality models.
Mentors: @Polaris000, @inishchith, @dlumbrer and @valeriocos.
- #216: [doc] Update prosoul-grimoirelab.md
/cp3 - #215: [docker] Update docker-compose.yml
/cp3 - #213: [doc] Update the repo with the latest images
/cp3 - #212: Update README.md
/ap - #210: [docs] Revamp README.md
/ap - #209: [travis] Upgrade setuptools and pip
/ap - #207: [panels] update attribute-template.json
/ap - #206: [views] update the viz result kibana_url
/ap - #203: [assessment] Fix the TemplateSyntaxError
/ap - #201: [UI] Improve the Login UI
/ap - #200: [docs] Update README.md with installation video
/ap - #199: add license headers and copyright information
/ap - #196: [docs] fixed minor typos in README.md
/ap
- #926: [qm-elk] Add support for QM data enrichment
/cp2 - #902: [qm-elk] Add support for QM data enrichment
/cp1 - #892: [enriched-gitlabqm] New enricher for QM GitLab data
/cp1 - #881: [enriched-gitlabcomments] New enricher to handle gitlab comments
/cb - #815: [schema] Update mattermost.csv
/ap - #814: [schema] Update dockerhub.csv
/ap - #812: [schema] Update askbot.csv
/ap - #788: Update README.md
/ap - #787: [doc] fix mistake in README.md
/ap
- #667: [backend] Add Zulip Backend
/cb - #624, #623: [perceval] Update license and copyright information
/ap - #615: [github] Update the docstrings
/ap
- #486: [doc] Add instructions for QM Enrichers
/cp3 - #476: [docs] Update Getting-Started.md result image
/cp1 - #450: [docs] revamp of getting-started.md
/ap - #431: Fix askbot configuration typos
/ap
Tags:
- application period :
/ap- community bonding period :
/cb- coding period x -
/cpx
- GSoC Acceptance, aceptación gsoc.
- Week 1: unión comunitaria 1 👉 Report.
- Week 2: unión comunitaria 2 👉 Report.
- Week 3: unión comunitaria 3 👉 Report.
- Week 4: unión comunitaria 4 👉 Report.
- Community Bonding Period, período de vinculación comunitaria.
- Week 1: semana uno 👉 Report.
- Week 2: semana dos 👉 Report.
- Week 3: semana tres 👉 Report.
- Week 4: semana cuatro 👉 Report.
- Coding Period 1, período de codificación uno.
- 🚴 First Evaluation Period (June 29 - July 3): PASSED ☑️.
- Week 5: semana cinco 👉 Report.
- Week 6: semana seis 👉 Report.
- Week 7: semana siete 👉 Report.
- Week 8: semana ocho 👉 Report.
- Coding Period 2, período de codificación dos.
- 🏄 Second Evaluation Period (June 27 - July 31): PASSED ☑️.
- Week 9: semana nueve 👉 Report.
- Week 10: semana diez 👉 Report.
- Week 11: semana once 👉 Report.
- Week 12: semana doce 👉 Report.
- Final Report, reporte final.
- 🪂 Final Evaluation Period (August 24 - September 7): PASSED ☑️ 🎉.
- GSoC 2020 Proposal CHAOSS - Venu
- Project Link on GSoC Website.
- Microtasks repository.
- Contributions during application period.
- We will be discussing about the progress of this project every week at the
#grimoirelabchannel on freenode IRC (scheduled for every Thursday17h to 18h18h to 19h (CEST) or20h30 to 21h3021h30 to 22h30 (IST)). The transcripts of the meetings (chats) are available in meetings directory. - I will be writing a blog post every week (mostly on Monday) explaning the work I did over the week. You can find the links to the work summary in the work directory.