vchrombie / gsoc Goto Github PK

Work on adding gitlabcomments enricher to get a better understanding of how enrichers work in ELK.

• structure of the index data #7

• Implement a first enricher (gitlab) whose output should be processable by Prosoul

  • discuss what metrics can be extracted from gitlab #8
  • implement the enrichers which can extract the metrics #6
  • show results #5 (comment)

• Implement git enricher

  • discuss what metrics can be extracted from git #9
  • implement the enrichers which can extract the metrics #6
  • show results #5 (comment)

- [ ] Implement pipermail enricher (moved to coding period 2)

• perform an assessment #5 (comment)
  - [ ] plot heat maps and bar charts with prosoul assessment results (moved to coding period 2)

• Work on the initial steps (setting up project-tracker, plan meetings, etc.)
• Get familiar with Django
• UML diagram (or any similar representation) of the current implementation of Prosoul.
• It can be useful if you can explore how to create an enriched index with a format similar to the one consumed by Prosoul. The target data for this evaluation could GitHub issues (or anything that is easy to process).
• It can be useful if you can explore how to create a study index with a format similar to the one consumed by Prosoul. The target data for this evaluation could GitHub issues (or anything that is easy to process).
• Learn the internals of Perceval and ELK.

Additional tasks:

• Explore a possible alternative to represent the quality model dendrogram with JS libraries.
• Create activity diagrams to understand the Prosoul workflow (perform an assessment, create a quality model).

• Discuss the tasks for the initial coding period in the last project meeting of the community-bonding phase.

Opening this issue for any discussion or questions regarding the tests for the enrichers.

Opening this issue to discuss about the work on the documentation required for the project.

Need to plan for the structure of the index data which is consumed by Prosoul.

opening this, in reference to the task planned in the last meeting, to discuss performing of assessments on a various set of projects

• pilot study 1: amFOSS (gitlab, git) #13 (comment)
• pilot study 2: GitLab.org (gitlab, meetup) #13 (comment)
• pilot study 3: CHAOSS Community (git, github) #13 (comment)

• Implement tests for the existing enrichers #15

• Update sirmordred repo with the configurations of the qm enrichers chaoss/grimoirelab-sirmordred#486

• Add the qm results dashboard to sigils repository chaoss/grimoirelab-sigils#470

• case study with different organizations #13

  • gitlab.org - gitlabqm, meetupqm #13 (comment)
  • chaoss githubqm, gitqm #13 (comment)

• Implement githubqm enricher #17 (comment)

Implement slackqm enricher (moved to wishlist)

• Documentation for the project #20

• Work on tutorials, walk-through videos #17 (comment)

• complete the basic structure of the project-tracker
• discuss and schedule the meeting timings
• setup blog for posting weekly posts
• plan the communication medium with the community members

Opening this issue to discuss the possible metrics which can be extracted from the gitlab raw data for gitlabqm enricher.

Implement the QM enrichers whose output should be processable by Prosoul.

currently working on

• gitlabqm
• gitqm
• pipermailqm
• meetupqm
• githubqm

planned enrichers
- slackqm (moved to wishlist)

• Implement pipermailqm enricher

  • discuss what metrics can be extracted from git #11
  • implement the enrichers which can extract the metrics #6
  • show results #12 (comment)

• Implement meetupqm enricher

  • discuss what metrics can be extracted from git #14
  • implement the enrichers which can extract the metrics #6
  • show results #12 (comment)

• perform an assessment #5 (comment)

  • plot heat maps and bar charts with prosoul assessment results #12 (comment)

• case study with different organizations #13

  • amfoss - gitlabqm, gitqm #13 (comment)
    - [ ] gitlab.org - gitlabqm, gitqm, meetupqm (moved to coding period 3)

- [ ] Implements tests for the existing enrichers #15 (moved to coding period 3)

opening this issue, in reply to @valeriocos's comment in #13 (comment).

Hi @vchrombie, the problem may be related to the fact that some raw items have been generated before chaoss/grimoirelab-perceval@9b5a7ac, which introduced the attribute "search_fields".

We had a conversation time ago about using the attribute "origin" instead of "search_fields". If this is still not possible, a workaround is to modify the raw items to include the search_fields (it could be achieved with an update_by_query), wdyt?

I solved the issue, used the origin to derive the project for the current scenario, but I would like to discuss the possible workaround and also over the implementation too.

Opening this issue to discuss the possible metrics which can be extracted from the git raw data for gitqm enricher.

Work on adding perceval support for Zulip chat to get a better understanding of how Perceval works.

Implement a gitlab enricher (say gitqm) whose output should be processable by Prosoul.

I understand that the metrics would be the same as of gitlabqm #8.

But still, opening this issue for any discussion regarding it.

Opening this issue to discuss the possible metrics which can be extracted from the pipermail raw data for pipermailqm enricher.

Opening this issue to discuss the possible metrics which can be extracted from the meetup raw data for meetupqm enricher.

As of now, we have a few Quality Models in the Bitergia/prosoul.

Link: https://github.com/Bitergia/prosoul/tree/master/django-prosoul/prosoul/data

Opening this issue for discussions to add more quality models using the metrics extracted from the project.