GrimoireLab: toolset for software development analytics
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
bin Create structure for a grimoirelab Python package. Jul 12, 2018
docker [docker] Changes to work with kibiter 6.1.4 Nov 12, 2018
docs Fix mixed href to Bitergia site Nov 14, 2018
grimoirelab Release 0.2.2 Dec 12, 2018
releases Release 0.2.2 Dec 12, 2018
tests [tests] Fix README.md, and references to testing dashboard in it Dec 28, 2017
utils
.dockerignore [docker] Fix some details of the images. Jan 10, 2018
BUILDING.md [docker] Clarify variable names in ansible file for building release. Sep 11, 2018
CONTRIBUTING.md
LICENSE
MANIFEST.in [setup] Add requirements.txt file to manifest. Nov 26, 2018
README.md [doc] Added file for community components. Sep 14, 2018
community_components.md
requirements.txt Release 0.2.2 Dec 12, 2018
setup.py Prepare some machinery for including grimoirelab itself in the release Aug 23, 2018

README.md

GrimoireLab

GrimoireLab is a toolset for software development analytics. It includes a coordinated set of tools to retrieve data from systems used to support software development (repositories), store it in databases, enrich it by computing relevant metrics, and making it easy to run analytics and visualizations on it.

You can learn more about GrimoireLab in the GrimoireLab tutorial, or visit the GrimoireLab website.

Currently, GrimoireLab is organized in the following repositories:

GrimoireLab is a CHAOSS project.

There are also some components built by the GrimoreLab community, which can be useful for you.

Contents of this repository

This repository is for stuff relevant to GrimoireLab as a whole. For example:

  • Issues for new features or bug reports that affect more than one GrimoireLab module. In this case, let's open an issue here, and when implementing the fix or the feature, let´s comment about the specific tickets in the specific modules that are used. For example, when supporting a new datasource, we will need patches (at least) in Perceval, GrimoireELK and panels. We would open here the feature request (or the user story) for the whole case, an issue (and later a pull request) in Perceval for the data retriever, same for GrimoireELK for the enriching code, and same for panels for the Kibiter panels.

  • Information about "coordinated releases" for most of GrimoireLab components (directory releases). Coordinated releases are snapshots (specific commits) of most of the GrimoireLab components that are expected to work together. See more information in the releases README.md file.

  • Utils (directory utils) for doing stuff relevant to GrimoireLab as a whole. Includes a script to produce Python packages for a coordinated release, etc.

  • Docker containers for showcasing GrimoireLab (directory docker). Includes dockerfiles and configuration files for the GrimoireLab containers that can be used to demo the technology, and can be the basis for real deployments. See more information in the docker README.md file.

  • How releases of GrimoireLab are built and tested: Building