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.
 
 
Jenkins 41a4857171 Merge "Add --server param to reviewers" 9 years ago
doc/source cleaning up index.rst file 9 years ago
projects Add jaypipes to nova-core 9 years ago
reviewstats Merge "Add --server param to reviewers" 9 years ago
tests Add --csv-rows option 10 years ago
.coveragerc Cookiecutterify reviewstats. 10 years ago
.gitignore Add a bug statistics tool. 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 Add a bug statistics tool. 10 years ago
babel.cfg Cookiecutterify reviewstats. 10 years ago
genresults-openreviews.sh Show 15 oldest in single project results 9 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 The argparse module was added in requirements 9 years ago
setup.cfg Add a bug statistics tool. 10 years ago
setup.py Cookiecutterify reviewstats. 10 years ago
test-requirements.txt Pin Sphinx. 10 years ago
tox.ini Remove tox locale overrides 9 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.
  • lp_projects: A list of Launchpad project ids to include.