Scripts for generating OpenStack development community statistics
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Zuul 59d12c214e Merge "Import Zuul job settings" 4 weeks ago
doc/source cleaning up index.rst file 5 years ago
projects Remove some non-oslo projects from oslo.json 1 month ago
reviewstats Add the ability to get reviewer stats across all stable branches 1 year ago
tests Add --csv-rows option 5 years ago
.coveragerc Change ignore-errors to ignore_errors 3 years ago
.gitignore Add a bug statistics tool. 5 years ago
.gitreview OpenDev Migration Patch 1 month ago
.mailmap Cookiecutterify reviewstats. 5 years ago
.testr.conf Cookiecutterify reviewstats. 5 years ago
.zuul.yaml Import Zuul job settings 1 month ago
CONTRIBUTING.rst Adjust wording for new Workflow URLs 4 years ago
LICENSE Cookiecutterify reviewstats. 5 years ago
MANIFEST.in Cookiecutterify reviewstats. 5 years ago
README.rst Add the ability to get reviewer stats across all stable branches 1 year ago
babel.cfg Cookiecutterify reviewstats. 5 years ago
genresults-openreviews.sh Removes tabs from .sh files 2 years ago
genresults-reviewers.sh Removes tabs from .sh files 2 years ago
genresults-reviews-for-bugs.sh Removes tabs from .sh files 2 years ago
openstack-common.conf Cookiecutterify reviewstats. 5 years ago
requirements.txt Remove argparse from requirements 3 years ago
setup.cfg python version changes 2 years ago
setup.py Cookiecutterify reviewstats. 5 years ago
test-requirements.txt Remove discover from test-requirements 2 years ago
tox.ini python version changes 2 years ago

README.rst

reviewstats

Utility scripts for generating stats about OpenStack development.

Features

  • openreviews.py - Get some stats on the number and age of open reviews.
  • reviewers.py - See how many reviews each person has done over a period of time.

Usage

Clone the git repository, then install the library:

pip install .

Run the scripts.

Project definitions

Each project has a JSON file describing what reviews, bugs and so on will count towards that projects statistics. The JSON file should have a single top level object containing the following keys:

  • name: The project name.
  • subprojects: A list of Gerrit projects to include.
  • core-team: A list of Gerrit usernames to consider as core reviewers across subprojects.
  • lp_projects: A list of Launchpad project ids to include.

Examples

  1. Get reviewer stats for the last 14 days (default) in the stable/pike branch:

$ reviewers --stable pike --output ~/reviewers-stable-pike-14

  1. Get reviewer stats for the last 90 days across all stable branches:

$ reviewers --stable all --days 90 --output ~/reviewers-stable-all-90