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.
 
 
Ben Nemec ac7d24cd70
Remove tuskar projects
6 years ago
doc/source cleaning up index.rst file 9 years ago
projects Remove tuskar projects 6 years ago
reviewstats Indicate the branch when generating stable checks 7 years ago
tests Add --csv-rows option 9 years ago
.coveragerc Change ignore-errors to ignore_errors 8 years ago
.gitignore Add a bug statistics tool. 9 years ago
.gitreview Add .gitreview file 10 years ago
.mailmap Cookiecutterify reviewstats. 9 years ago
.testr.conf Cookiecutterify reviewstats. 9 years ago
CONTRIBUTING.rst Adjust wording for new Workflow URLs 8 years ago
LICENSE Cookiecutterify reviewstats. 9 years ago
MANIFEST.in Cookiecutterify reviewstats. 9 years ago
README.rst Document installation from repository 8 years ago
babel.cfg Cookiecutterify reviewstats. 9 years ago
genresults-openreviews.sh Add GERRIT_KEY and GERRIT_SERVER options in scripts 8 years ago
genresults-reviewers.sh Fix user and pass in genresults-reviewers.sh 8 years ago
genresults-reviews-for-bugs.sh Add GERRIT_KEY and GERRIT_SERVER options in scripts 8 years ago
openstack-common.conf Cookiecutterify reviewstats. 9 years ago
requirements.txt Remove argparse from requirements 7 years ago
setup.cfg python version changes 6 years ago
setup.py Cookiecutterify reviewstats. 9 years ago
test-requirements.txt Remove discover from test-requirements 7 years ago
tox.ini python version changes 6 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.