Project & Team

Introduction

This page describes the Gammapy project organisation and the main roles and responsibilities in the Gammapy team.

This structure was put in place in January 2018 based on our experience developing Gammapy since 2013, as well more generally with science tool software development in the H.E.S.S. and CTA collaborations. We also took inspiration from the way the Astropy and Sunpy projects are organised, since they are in a similar situation as Gammapy: a distributed development team and a variety of people and projects using and depending on them.

We expect this structure to evolve over the coming years, adapting to the size and composition of the Gammapy development team, and the requirements and needs of scientists and projects using Gammapy. If you would like to become part of the Gammapy team, please get in contact. Help is always welcome!

Overview

The following sections describe the major roles and responsibilities in the Gammapy team:

Coordination Committee

The Gammapy coordination committee (CC) is the board that is responsible to promote, coordinate and steer Gammapy developments. It also serves as main contact point for the Gammapy project.

Gammapy is developed and used by people and projects from several institutes and countries, with different needs, priorities and schedules. Members of the CC are representatives for the major stakeholders, i.e. groups that have contributed significantly to Gammapy development, as well as projects like H.E.S.S. and CTA that are using Gammapy. In addition, the Gammapy project manager and lead developer are part of the Gammapy CC.

Responsibilities include:

Current CC members (alphabetical order):

Project manager

The project manager is the non-technical executive lead for the Gammapy project.

The project manager is appointed by the Gammapy coordination committee, and works closely with the Gammapy coordination committee, contributors and users.

Responsibilities include:

The current project manager is Bruno Khelifi, the deputy project manager is Christopher van Eldik.

Lead developer

The lead developer is the technical executive lead for the Gammapy project.

The lead developer is appointed by the Gammapy coordination committee, and works closely with the Gammapy coordination committee, project manager and contributors.

Responsibilities include:

The current lead developers are Axel Donath and Régis Terrier.

Contributors

Anyone is welcome to contribute to Gammapy! Start by using Gammapy. Then if you notice a missing feature or issue, please report it (see contact page), and if you're interested in contributing, we can team you up with a mentor from the Gammapy team to do it.

The following people have contributed commits to the Gammapy repository (first name alphabetical order):

There is no useful automatic way to measure how much someone contributed. The most common measure used is commits to the code repository. This is visible for Gammapy on GitHub and Open Hub. However, please note that the number of commits isn't a useful measure. There are people that have spent several days to find and fix an important bug, or implement a big and complex feature and make one commit. If someone makes a good bug report or does code review or mentoring or organisational work for Gammapy it doesn't show up in the commit stats at all.

Please know that any contribution to the Gammapy project is valued!

Supporting institutions

Several institutions support the Gammapy project, making it possible, and grants have been obtained for our functioning.

People evolved on gammapy are coming from different institutions, laboratories and universities. We acknowledge them for their daily support. Here are listed the main institutions (alphabetical order):

Institutions supporting the project


Several grants has been granted to support the development of gammapy: