Scripts for generating OpenStack development community statistics
Go to file
2014-07-08 20:04:03 +00:00
doc/source cleaning up index.rst file 2014-05-29 11:20:35 +02:00
projects Updating Horizon core with recent changes 2014-07-03 11:25:36 -06:00
reviewstats Fix small grammatical errors 2014-06-17 00:34:03 +00:00
tests Add --csv-rows option 2013-12-16 11:27:22 -05:00
.coveragerc Cookiecutterify reviewstats. 2013-11-25 03:26:57 +00:00
.gitignore Add a bug statistics tool. 2013-12-06 08:13:37 +13:00
.gitreview Add .gitreview file 2013-07-01 15:03:59 +00:00
.mailmap Cookiecutterify reviewstats. 2013-11-25 03:26:57 +00:00
.testr.conf Cookiecutterify reviewstats. 2013-11-25 03:26:57 +00:00
babel.cfg Cookiecutterify reviewstats. 2013-11-25 03:26:57 +00:00
CONTRIBUTING.rst Cookiecutterify reviewstats. 2013-11-25 03:26:57 +00:00
genresults-openreviews.sh Show 15 oldest in single project results 2014-02-09 18:13:50 -05:00
genresults-reviewers.sh Move reviewers.py into the reviewstats namespace. 2013-11-25 11:18:12 -05:00
genresults-reviews-for-bugs.sh Move reviews_for_bugs into reviewstats. 2013-11-25 11:18:12 -05:00
LICENSE Cookiecutterify reviewstats. 2013-11-25 03:26:57 +00:00
MANIFEST.in Cookiecutterify reviewstats. 2013-11-25 03:26:57 +00:00
openstack-common.conf Cookiecutterify reviewstats. 2013-11-25 03:26:57 +00:00
README.rst Add a bug statistics tool. 2013-12-06 08:13:37 +13:00
requirements.txt The argparse module was added in requirements 2014-06-29 16:18:20 +08:00
setup.cfg Add a bug statistics tool. 2013-12-06 08:13:37 +13:00
setup.py Cookiecutterify reviewstats. 2013-11-25 03:26:57 +00:00
test-requirements.txt Pin Sphinx. 2013-12-13 20:13:56 +13:00
tox.ini Remove tox locale overrides 2014-02-10 03:03:04 +00:00

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.