Scripts for generating OpenStack development community statistics
You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
Russell Bryant 7ad92d8088 Fix CSV output
A previous commit that removed the 'received reviews' from the default
output totally broke CSV output.  This gets it working again.

Change-Id: I76775c496b5b450332f0e8f9d6fa4f7383ffc630
10 years ago
doc/source Cookiecutterify reviewstats. 10 years ago
projects Add barbican.json project file 10 years ago
reviewstats Fix CSV output 10 years ago
.coveragerc Cookiecutterify reviewstats. 10 years ago
.gitignore Cookiecutterify reviewstats. 10 years ago
.gitreview Add .gitreview file 10 years ago
.mailmap Cookiecutterify reviewstats. 10 years ago
.testr.conf Cookiecutterify reviewstats. 10 years ago
CONTRIBUTING.rst Cookiecutterify reviewstats. 10 years ago
LICENSE Cookiecutterify reviewstats. 10 years ago
MANIFEST.in Cookiecutterify reviewstats. 10 years ago
README.rst Document the JSON schema a little. 10 years ago
babel.cfg Cookiecutterify reviewstats. 10 years ago
genresults-openreviews.sh Move openreviews into the reviewstats namespace. 10 years ago
genresults-reviewers.sh Move reviewers.py into the reviewstats namespace. 10 years ago
genresults-reviews-for-bugs.sh Move reviews_for_bugs into reviewstats. 10 years ago
openstack-common.conf Cookiecutterify reviewstats. 10 years ago
requirements.txt Cookiecutterify reviewstats. 10 years ago
setup.cfg Move reviewers.py into the reviewstats namespace. 10 years ago
setup.py Cookiecutterify reviewstats. 10 years ago
test-requirements.txt Cookiecutterify reviewstats. 10 years ago
tox.ini E128 really isn't sane. 10 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

pip install reviewstats

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.