%global _empty_manifest_terminate_build 0 Name: python-grimoirelab Version: 0.10.0 Release: 1 Summary: Tool set for software development analytics License: GPL-3.0+ URL: https://chaoss.github.io/grimoirelab/ Source0: https://mirrors.aliyun.com/pypi/web/packages/90/3f/f142bdef0bcd8b0dcde99fd74ea14327f6cd417f4c95773f7172d46de32d/grimoirelab-0.10.0.tar.gz BuildArch: noarch Requires: python3-grimoirelab-toolkit Requires: python3-perceval-mozilla Requires: python3-perceval-opnfv Requires: python3-perceval-puppet Requires: python3-perceval-weblate Requires: python3-sortinghat Requires: python3-kidash Requires: python3-grimoirelab-panels Requires: python3-grimoire-elk Requires: python3-sirmordred Requires: python3-cereslib Requires: python3-graal Requires: python3-statsmodels Requires: python3-perceval %description # GrimoireLab [![grimoirelab-showcase](https://user-images.githubusercontent.com/25265451/84442403-30dcce80-ac5b-11ea-9f5b-60266d875ebd.png "GrimoireLab | CHAOSS Bitergia Analytics")](https://chaoss.biterg.io/app/kibana#/dashboard/Overview) GrimoireLab is a [CHAOSS](https://chaoss.community) 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 make it easy to run analytics and visualizations on it. You can learn more about GrimoireLab in the [GrimoireLab tutorial](https://chaoss.github.io/grimoirelab-tutorial/), or visit the [GrimoireLab website](https://chaoss.github.io/grimoirelab). Metrics available in GrimoireLab are, in part, developed in the CHAOSS project. For more information regarding CHAOSS metrics, see the latest release at: https://chaoss.community/metrics/ # Getting started To ease the newcomer experience we are providing a [default setup](default-grimoirelab-settings) to analyze git activity for this repository. For this set up, there are several options to run GrimoireLab: ## Using `docker-compose` Requirements: * **Software**: [git](https://git-scm.com/), [docker client](https://docs.docker.com/get-docker/) and [docker compose](https://docs.docker.com/compose/install/). An example of working configuration: ```console root@test-68b8628f:~# git --version git version 2.17.1 root@test-68b8628f:~# docker --version Docker version 19.03.1, build 74b1e89 root@test-68b8628f:~# docker-compose --version docker-compose version 1.22.0, build f46880fe ``` * **Hardware**: 2 CPU cores, 8GB memory RAM and [enough virtual memory for Elasticsearch](https://www.elastic.co/guide/en/elasticsearch/reference/current/vm-max-map-count.html) Steps: 1. Clone this project: ```console foo@bar:~$ git clone https://github.com/chaoss/grimoirelab ``` 2. Go to `docker-compose` folder and run the following command: ```console foo@bar:~$ cd grimoirelab/docker-compose foo@bar:~/grimoirelab/docker-compose$ docker-compose up -d ``` Your dashboard will be ready after a while at `http://localhost:8000`. The waiting time depends on the amount of data to fetch from a repo, for small repositories you can expect your data to be visible in the dashboard after 10-15 minutes. More details in the [docker-compose folder](./docker-compose/README.md). ## Using `docker run` Requirements: * **Software**: [git](https://git-scm.com/) and [docker client](https://docs.docker.com/get-docker/). An example of working configuration: ```console root@test-68b8628f:~# git --version git version 2.17.1 root@test-68b8628f:~# docker --version Docker version 19.03.1, build 74b1e89 ``` * **Hardware**: 2 CPU cores, 8GB memory RAM and set * ElasticSearch and Kibana up and running. * SortingHat up and running Steps: 1. Clone this project: ```console $ git clone https://github.com/chaoss/grimoirelab ``` 2. Go to the project folder and run the following command: ```console foo@bar:~$ cd grimoirelab foo@bar:~/grimoirelab $ docker run --net=host \ -v $(pwd)/default-grimoirelab-settings/projects.json:/home/grimoire/conf/projects.json \ -v $(pwd)/default-grimoirelab-settings/setup-docker.cfg:/home/grimoire/conf/setup.cfg \ -t grimoirelab/grimoirelab ``` Your dashboard will be ready after a while at `http://localhost:8000`. The waiting time depends on the amount of data to fetch from a repo, for small repositories you can expect your data to be visible in the dashboard after 10-15 minutes. More details in the [docker folder](./docker/README.md). # GrimoireLab components Currently, GrimoireLab toolkit is organized in the following repositories: * Data retrieval related components: * [Perceval](https://github.com/chaoss/grimoirelab-perceval): retrieval of data from data sources * [Perceval (bundle for OPNFV)](https://github.com/chaoss/grimoirelab-perceval-opnfv) * [Perceval (bundle for Mozilla)](https://github.com/chaoss/grimoirelab-perceval-mozilla) * [Perceval (bundle for Puppet)](https://github.com/chaoss/grimoirelab-perceval-puppet) * [Perceval (bundle for Weblate)](https://github.com/chaoss/grimoirelab-perceval-weblate) * [Graal](https://github.com/chaoss/grimoirelab-graal): source data analysis with external tools * [KingArthur](https://github.com/chaoss/grimoirelab-kingarthur): batch processing for massive retrieval * Data enrichment related components: * [GrimoireElk](https://github.com/chaoss/grimoirelab-elk): storage and enrichment of data * [Cereslib](https://github.com/chaoss/grimoirelab-cereslib): generic data processor * [SortingHat](https://github.com/chaoss/grimoirelab-sortinghat): identity management * Data consumption related components: * [Kibiter](https://github.com/chaoss/grimoirelab-kibiter): dashboard, downstream version of Kibana * [Sigils](https://github.com/chaoss/grimoirelab-sigils): visualizations and dashboards * [Kidash](https://github.com/chaoss/grimoirelab-kidash): visualizations and dashboards manager * [Manuscripts](https://github.com/chaoss/grimoirelab-manuscripts): reporting * Platform management, orchestration, and common utils: * [Mordred](https://github.com/chaoss/grimoirelab-mordred): orchestration * [GrimoireLab Toolkit](https://github.com/chaoss/grimoirelab-toolkit): common utilities * [Bestiary](https://github.com/chaoss/grimoirelab-bestiary): web-based user interface to manage repositories and projects for Mordred There are also some [components built by the GrimoreLab community](community_components.md), which can be useful for you. Other related repositories are: * [GrimoireLab Tutorial](https://github.com/chaoss/grimoirelab-tutorial) * [GrimoireLab as a whole](https://github.com/chaoss/grimoirelab) (this repository) ## Contents of this repository This repository is for content 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. In this case, we would open a 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. * Release notes for most GrimoireLab components (directory [releases](releases)). * Docker container for showcasing GrimoireLab (directory [docker](docker)). Includes a Dockerfile 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](docker/README.md). * If you feel more comfortable with `docker-compose`, the [docker-compose](docker-compose) folder includes instructions and configuration files to deploy GrimoireLab using `docker-compose` command. * Source code of the GrimoireLab components is available in `src`. Each directory is a Git submodule, so its contents will not be available after cloning the repository. To fetch all the data, and get the latest version, you can run the following command: ```console $ git submodule update --init --remote ``` * How releases of GrimoireLab are built and tested: [Building](BUILDING.md) ## Citation If you use GrimoireLab in your research papers, please refer to [GrimoireLab: A toolset for software development analytics](https://doi.org/10.7717/peerj-cs.601): APA style: ``` Dueñas S, Cosentino V, Gonzalez-Barahona JM, del Castillo San Felix A, Izquierdo-Cortazar D, Cañas-Díaz L, Pérez García-Plaza A. 2021. GrimoireLab: A toolset for software development analytics. PeerJ Computer Science 7:e601 https://doi.org/10.7717/peerj-cs.601 ``` BibTeX / BibLaTeX: ``` @Article{duenas2021:grimoirelab, author = {Dueñas, Santiago and Cosentino, Valerio and Gonzalez-Barahona, Jesus M. and del Castillo San Felix, Alvaro and Izquierdo-Cortazar, Daniel and Cañas-Díaz, Luis and Pérez García-Plaza, Alberto}, title = {GrimoireLab: A toolset for software development analytics}, journaltitle = {PeerJ Computer Science}, date = {2021-07-09}, volume = 7, number = {e601}, doi = {10.7717/peerj-cs.601}, url = {https://doi.org/10.7717/peerj-cs.601}} ``` # Contributing Contributions are welcome, please check the [Contributing Guidelines](CONTRIBUTING.md). %package -n python3-grimoirelab Summary: Tool set for software development analytics Provides: python-grimoirelab BuildRequires: python3-devel BuildRequires: python3-setuptools BuildRequires: python3-pip %description -n python3-grimoirelab # GrimoireLab [![grimoirelab-showcase](https://user-images.githubusercontent.com/25265451/84442403-30dcce80-ac5b-11ea-9f5b-60266d875ebd.png "GrimoireLab | CHAOSS Bitergia Analytics")](https://chaoss.biterg.io/app/kibana#/dashboard/Overview) GrimoireLab is a [CHAOSS](https://chaoss.community) 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 make it easy to run analytics and visualizations on it. You can learn more about GrimoireLab in the [GrimoireLab tutorial](https://chaoss.github.io/grimoirelab-tutorial/), or visit the [GrimoireLab website](https://chaoss.github.io/grimoirelab). Metrics available in GrimoireLab are, in part, developed in the CHAOSS project. For more information regarding CHAOSS metrics, see the latest release at: https://chaoss.community/metrics/ # Getting started To ease the newcomer experience we are providing a [default setup](default-grimoirelab-settings) to analyze git activity for this repository. For this set up, there are several options to run GrimoireLab: ## Using `docker-compose` Requirements: * **Software**: [git](https://git-scm.com/), [docker client](https://docs.docker.com/get-docker/) and [docker compose](https://docs.docker.com/compose/install/). An example of working configuration: ```console root@test-68b8628f:~# git --version git version 2.17.1 root@test-68b8628f:~# docker --version Docker version 19.03.1, build 74b1e89 root@test-68b8628f:~# docker-compose --version docker-compose version 1.22.0, build f46880fe ``` * **Hardware**: 2 CPU cores, 8GB memory RAM and [enough virtual memory for Elasticsearch](https://www.elastic.co/guide/en/elasticsearch/reference/current/vm-max-map-count.html) Steps: 1. Clone this project: ```console foo@bar:~$ git clone https://github.com/chaoss/grimoirelab ``` 2. Go to `docker-compose` folder and run the following command: ```console foo@bar:~$ cd grimoirelab/docker-compose foo@bar:~/grimoirelab/docker-compose$ docker-compose up -d ``` Your dashboard will be ready after a while at `http://localhost:8000`. The waiting time depends on the amount of data to fetch from a repo, for small repositories you can expect your data to be visible in the dashboard after 10-15 minutes. More details in the [docker-compose folder](./docker-compose/README.md). ## Using `docker run` Requirements: * **Software**: [git](https://git-scm.com/) and [docker client](https://docs.docker.com/get-docker/). An example of working configuration: ```console root@test-68b8628f:~# git --version git version 2.17.1 root@test-68b8628f:~# docker --version Docker version 19.03.1, build 74b1e89 ``` * **Hardware**: 2 CPU cores, 8GB memory RAM and set * ElasticSearch and Kibana up and running. * SortingHat up and running Steps: 1. Clone this project: ```console $ git clone https://github.com/chaoss/grimoirelab ``` 2. Go to the project folder and run the following command: ```console foo@bar:~$ cd grimoirelab foo@bar:~/grimoirelab $ docker run --net=host \ -v $(pwd)/default-grimoirelab-settings/projects.json:/home/grimoire/conf/projects.json \ -v $(pwd)/default-grimoirelab-settings/setup-docker.cfg:/home/grimoire/conf/setup.cfg \ -t grimoirelab/grimoirelab ``` Your dashboard will be ready after a while at `http://localhost:8000`. The waiting time depends on the amount of data to fetch from a repo, for small repositories you can expect your data to be visible in the dashboard after 10-15 minutes. More details in the [docker folder](./docker/README.md). # GrimoireLab components Currently, GrimoireLab toolkit is organized in the following repositories: * Data retrieval related components: * [Perceval](https://github.com/chaoss/grimoirelab-perceval): retrieval of data from data sources * [Perceval (bundle for OPNFV)](https://github.com/chaoss/grimoirelab-perceval-opnfv) * [Perceval (bundle for Mozilla)](https://github.com/chaoss/grimoirelab-perceval-mozilla) * [Perceval (bundle for Puppet)](https://github.com/chaoss/grimoirelab-perceval-puppet) * [Perceval (bundle for Weblate)](https://github.com/chaoss/grimoirelab-perceval-weblate) * [Graal](https://github.com/chaoss/grimoirelab-graal): source data analysis with external tools * [KingArthur](https://github.com/chaoss/grimoirelab-kingarthur): batch processing for massive retrieval * Data enrichment related components: * [GrimoireElk](https://github.com/chaoss/grimoirelab-elk): storage and enrichment of data * [Cereslib](https://github.com/chaoss/grimoirelab-cereslib): generic data processor * [SortingHat](https://github.com/chaoss/grimoirelab-sortinghat): identity management * Data consumption related components: * [Kibiter](https://github.com/chaoss/grimoirelab-kibiter): dashboard, downstream version of Kibana * [Sigils](https://github.com/chaoss/grimoirelab-sigils): visualizations and dashboards * [Kidash](https://github.com/chaoss/grimoirelab-kidash): visualizations and dashboards manager * [Manuscripts](https://github.com/chaoss/grimoirelab-manuscripts): reporting * Platform management, orchestration, and common utils: * [Mordred](https://github.com/chaoss/grimoirelab-mordred): orchestration * [GrimoireLab Toolkit](https://github.com/chaoss/grimoirelab-toolkit): common utilities * [Bestiary](https://github.com/chaoss/grimoirelab-bestiary): web-based user interface to manage repositories and projects for Mordred There are also some [components built by the GrimoreLab community](community_components.md), which can be useful for you. Other related repositories are: * [GrimoireLab Tutorial](https://github.com/chaoss/grimoirelab-tutorial) * [GrimoireLab as a whole](https://github.com/chaoss/grimoirelab) (this repository) ## Contents of this repository This repository is for content 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. In this case, we would open a 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. * Release notes for most GrimoireLab components (directory [releases](releases)). * Docker container for showcasing GrimoireLab (directory [docker](docker)). Includes a Dockerfile 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](docker/README.md). * If you feel more comfortable with `docker-compose`, the [docker-compose](docker-compose) folder includes instructions and configuration files to deploy GrimoireLab using `docker-compose` command. * Source code of the GrimoireLab components is available in `src`. Each directory is a Git submodule, so its contents will not be available after cloning the repository. To fetch all the data, and get the latest version, you can run the following command: ```console $ git submodule update --init --remote ``` * How releases of GrimoireLab are built and tested: [Building](BUILDING.md) ## Citation If you use GrimoireLab in your research papers, please refer to [GrimoireLab: A toolset for software development analytics](https://doi.org/10.7717/peerj-cs.601): APA style: ``` Dueñas S, Cosentino V, Gonzalez-Barahona JM, del Castillo San Felix A, Izquierdo-Cortazar D, Cañas-Díaz L, Pérez García-Plaza A. 2021. GrimoireLab: A toolset for software development analytics. PeerJ Computer Science 7:e601 https://doi.org/10.7717/peerj-cs.601 ``` BibTeX / BibLaTeX: ``` @Article{duenas2021:grimoirelab, author = {Dueñas, Santiago and Cosentino, Valerio and Gonzalez-Barahona, Jesus M. and del Castillo San Felix, Alvaro and Izquierdo-Cortazar, Daniel and Cañas-Díaz, Luis and Pérez García-Plaza, Alberto}, title = {GrimoireLab: A toolset for software development analytics}, journaltitle = {PeerJ Computer Science}, date = {2021-07-09}, volume = 7, number = {e601}, doi = {10.7717/peerj-cs.601}, url = {https://doi.org/10.7717/peerj-cs.601}} ``` # Contributing Contributions are welcome, please check the [Contributing Guidelines](CONTRIBUTING.md). %package help Summary: Development documents and examples for grimoirelab Provides: python3-grimoirelab-doc %description help # GrimoireLab [![grimoirelab-showcase](https://user-images.githubusercontent.com/25265451/84442403-30dcce80-ac5b-11ea-9f5b-60266d875ebd.png "GrimoireLab | CHAOSS Bitergia Analytics")](https://chaoss.biterg.io/app/kibana#/dashboard/Overview) GrimoireLab is a [CHAOSS](https://chaoss.community) 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 make it easy to run analytics and visualizations on it. You can learn more about GrimoireLab in the [GrimoireLab tutorial](https://chaoss.github.io/grimoirelab-tutorial/), or visit the [GrimoireLab website](https://chaoss.github.io/grimoirelab). Metrics available in GrimoireLab are, in part, developed in the CHAOSS project. For more information regarding CHAOSS metrics, see the latest release at: https://chaoss.community/metrics/ # Getting started To ease the newcomer experience we are providing a [default setup](default-grimoirelab-settings) to analyze git activity for this repository. For this set up, there are several options to run GrimoireLab: ## Using `docker-compose` Requirements: * **Software**: [git](https://git-scm.com/), [docker client](https://docs.docker.com/get-docker/) and [docker compose](https://docs.docker.com/compose/install/). An example of working configuration: ```console root@test-68b8628f:~# git --version git version 2.17.1 root@test-68b8628f:~# docker --version Docker version 19.03.1, build 74b1e89 root@test-68b8628f:~# docker-compose --version docker-compose version 1.22.0, build f46880fe ``` * **Hardware**: 2 CPU cores, 8GB memory RAM and [enough virtual memory for Elasticsearch](https://www.elastic.co/guide/en/elasticsearch/reference/current/vm-max-map-count.html) Steps: 1. Clone this project: ```console foo@bar:~$ git clone https://github.com/chaoss/grimoirelab ``` 2. Go to `docker-compose` folder and run the following command: ```console foo@bar:~$ cd grimoirelab/docker-compose foo@bar:~/grimoirelab/docker-compose$ docker-compose up -d ``` Your dashboard will be ready after a while at `http://localhost:8000`. The waiting time depends on the amount of data to fetch from a repo, for small repositories you can expect your data to be visible in the dashboard after 10-15 minutes. More details in the [docker-compose folder](./docker-compose/README.md). ## Using `docker run` Requirements: * **Software**: [git](https://git-scm.com/) and [docker client](https://docs.docker.com/get-docker/). An example of working configuration: ```console root@test-68b8628f:~# git --version git version 2.17.1 root@test-68b8628f:~# docker --version Docker version 19.03.1, build 74b1e89 ``` * **Hardware**: 2 CPU cores, 8GB memory RAM and set * ElasticSearch and Kibana up and running. * SortingHat up and running Steps: 1. Clone this project: ```console $ git clone https://github.com/chaoss/grimoirelab ``` 2. Go to the project folder and run the following command: ```console foo@bar:~$ cd grimoirelab foo@bar:~/grimoirelab $ docker run --net=host \ -v $(pwd)/default-grimoirelab-settings/projects.json:/home/grimoire/conf/projects.json \ -v $(pwd)/default-grimoirelab-settings/setup-docker.cfg:/home/grimoire/conf/setup.cfg \ -t grimoirelab/grimoirelab ``` Your dashboard will be ready after a while at `http://localhost:8000`. The waiting time depends on the amount of data to fetch from a repo, for small repositories you can expect your data to be visible in the dashboard after 10-15 minutes. More details in the [docker folder](./docker/README.md). # GrimoireLab components Currently, GrimoireLab toolkit is organized in the following repositories: * Data retrieval related components: * [Perceval](https://github.com/chaoss/grimoirelab-perceval): retrieval of data from data sources * [Perceval (bundle for OPNFV)](https://github.com/chaoss/grimoirelab-perceval-opnfv) * [Perceval (bundle for Mozilla)](https://github.com/chaoss/grimoirelab-perceval-mozilla) * [Perceval (bundle for Puppet)](https://github.com/chaoss/grimoirelab-perceval-puppet) * [Perceval (bundle for Weblate)](https://github.com/chaoss/grimoirelab-perceval-weblate) * [Graal](https://github.com/chaoss/grimoirelab-graal): source data analysis with external tools * [KingArthur](https://github.com/chaoss/grimoirelab-kingarthur): batch processing for massive retrieval * Data enrichment related components: * [GrimoireElk](https://github.com/chaoss/grimoirelab-elk): storage and enrichment of data * [Cereslib](https://github.com/chaoss/grimoirelab-cereslib): generic data processor * [SortingHat](https://github.com/chaoss/grimoirelab-sortinghat): identity management * Data consumption related components: * [Kibiter](https://github.com/chaoss/grimoirelab-kibiter): dashboard, downstream version of Kibana * [Sigils](https://github.com/chaoss/grimoirelab-sigils): visualizations and dashboards * [Kidash](https://github.com/chaoss/grimoirelab-kidash): visualizations and dashboards manager * [Manuscripts](https://github.com/chaoss/grimoirelab-manuscripts): reporting * Platform management, orchestration, and common utils: * [Mordred](https://github.com/chaoss/grimoirelab-mordred): orchestration * [GrimoireLab Toolkit](https://github.com/chaoss/grimoirelab-toolkit): common utilities * [Bestiary](https://github.com/chaoss/grimoirelab-bestiary): web-based user interface to manage repositories and projects for Mordred There are also some [components built by the GrimoreLab community](community_components.md), which can be useful for you. Other related repositories are: * [GrimoireLab Tutorial](https://github.com/chaoss/grimoirelab-tutorial) * [GrimoireLab as a whole](https://github.com/chaoss/grimoirelab) (this repository) ## Contents of this repository This repository is for content 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. In this case, we would open a 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. * Release notes for most GrimoireLab components (directory [releases](releases)). * Docker container for showcasing GrimoireLab (directory [docker](docker)). Includes a Dockerfile 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](docker/README.md). * If you feel more comfortable with `docker-compose`, the [docker-compose](docker-compose) folder includes instructions and configuration files to deploy GrimoireLab using `docker-compose` command. * Source code of the GrimoireLab components is available in `src`. Each directory is a Git submodule, so its contents will not be available after cloning the repository. To fetch all the data, and get the latest version, you can run the following command: ```console $ git submodule update --init --remote ``` * How releases of GrimoireLab are built and tested: [Building](BUILDING.md) ## Citation If you use GrimoireLab in your research papers, please refer to [GrimoireLab: A toolset for software development analytics](https://doi.org/10.7717/peerj-cs.601): APA style: ``` Dueñas S, Cosentino V, Gonzalez-Barahona JM, del Castillo San Felix A, Izquierdo-Cortazar D, Cañas-Díaz L, Pérez García-Plaza A. 2021. GrimoireLab: A toolset for software development analytics. PeerJ Computer Science 7:e601 https://doi.org/10.7717/peerj-cs.601 ``` BibTeX / BibLaTeX: ``` @Article{duenas2021:grimoirelab, author = {Dueñas, Santiago and Cosentino, Valerio and Gonzalez-Barahona, Jesus M. and del Castillo San Felix, Alvaro and Izquierdo-Cortazar, Daniel and Cañas-Díaz, Luis and Pérez García-Plaza, Alberto}, title = {GrimoireLab: A toolset for software development analytics}, journaltitle = {PeerJ Computer Science}, date = {2021-07-09}, volume = 7, number = {e601}, doi = {10.7717/peerj-cs.601}, url = {https://doi.org/10.7717/peerj-cs.601}} ``` # Contributing Contributions are welcome, please check the [Contributing Guidelines](CONTRIBUTING.md). %prep %autosetup -n grimoirelab-0.10.0 %build %py3_build %install %py3_install install -d -m755 %{buildroot}/%{_pkgdocdir} if [ -d doc ]; then cp -arf doc %{buildroot}/%{_pkgdocdir}; fi if [ -d docs ]; then cp -arf docs %{buildroot}/%{_pkgdocdir}; fi if [ -d example ]; then cp -arf example %{buildroot}/%{_pkgdocdir}; fi if [ -d examples ]; then cp -arf examples %{buildroot}/%{_pkgdocdir}; fi pushd %{buildroot} if [ -d usr/lib ]; then find usr/lib -type f -printf "\"/%h/%f\"\n" >> filelist.lst fi if [ -d usr/lib64 ]; then find usr/lib64 -type f -printf "\"/%h/%f\"\n" >> filelist.lst fi if [ -d usr/bin ]; then find usr/bin -type f -printf "\"/%h/%f\"\n" >> filelist.lst fi if [ -d usr/sbin ]; then find usr/sbin -type f -printf "\"/%h/%f\"\n" >> filelist.lst fi touch doclist.lst if [ -d usr/share/man ]; then find usr/share/man -type f -printf "\"/%h/%f.gz\"\n" >> doclist.lst fi popd mv %{buildroot}/filelist.lst . mv %{buildroot}/doclist.lst . %files -n python3-grimoirelab -f filelist.lst %dir %{python3_sitelib}/* %files help -f doclist.lst %{_docdir}/* %changelog * Fri Jun 09 2023 Python_Bot - 0.10.0-1 - Package Spec generated