Add more Quality Models using the extracted metrics

[vchrombie]

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.

[vchrombie]

I have used Developer QM for the assessments.

• Developer Quality
  • Product
    • Vitality
      • numberOfCommits
      • numberOfIssues
  • Community
    • Attention
      • numberOfIssuesAttended
      • numberOfIssuesClosed

This QM involves only two data sources (git and gitlab/github).

[vchrombie]

As of now, we have 4 data sources.

• git [metrics] git raw data #9
  • number of commits
  • number of lines added
  • number of lines removed
  • number of actions
  • number of files changed
• gitlab [metrics] gitlab raw data #8
  • number of issues created
  • number of issues closed
  • number of merges created
  • number of merges closed
  • number of merges merged
  • number of issue comments
  • number of merge comments
  • number of issues attended
  • number of merges attended
• pipermail [metrics] pipermail raw data #11
  • number of emails
  • number of replies
  • number of threads
  • number of users
• meetup [metrics] meetup raw data #14
  • number of RSVPS
  • number of comments
  • number of yes RSVPs (per event)
• github [metrics] github raw data #19
  • number of issues created
  • number of issues closed
  • number of pulls created
  • number of pulls closed
  • number of pulls merged
  • number of issue comments
  • number of review comments
  • number of issues attended
  • number of pulls reviewed

[vchrombie]

a few quality models used for previous GitLab.org study are

• developer-qm-gitlab

  • product
    • vitality
      • number of issues
      • number of merge requests
  • community
    • issues-attention
      • number of issues attended
      • number of issues closed
    • mrs-attention
      • number of merge requests attended
      • number of merge requests closed
      • number of merge requests merged

• developer-qm-meetup

  • community
    • events
      • count of yes rsvp
    • activity
      • number of comments
      • number of rsvps

[vchrombie]

quality model used for CHAOSS study

• developer-qm-chaoss
  • product
    • vitality
      • number of commits
      • number of issues
      • number of pull requests
  • community
    • issue-attention
      • number of issues attended
      • number of issues closed
    • pr-attention
      • number of pull requests reviewed
      • number of pull requests closed
      • number of pull requests merged

software project study threshold is 1,5,10,20,50
metrics wg study threshold is 5,10,15,20,50