/
team.html
449 lines (418 loc) · 24.1 KB
/
team.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
<!DOCTYPE html>
<html>
<style type="text/css" media="screen">
h2[id]::before {
display: block;
content: " ";
margin-top: -125px;
height: 125px;
}
</style>
<head>
<!-- Global site tag (gtag.js) - Google Analytics -->
<script async src="https://www.googletagmanager.com/gtag/js?id=UA-110956727-1"></script>
<script>
window.dataLayer = window.dataLayer || [];
function gtag() {
dataLayer.push(arguments);
}
gtag('js', new Date());
gtag('config', 'UA-110956727-1');
</script>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1, shrink-to-fit=no">
<title>Gammapy - Team</title>
<link href="https://fonts.googleapis.com/css?family=Fira+Sans" rel="stylesheet">
<link rel="stylesheet" href="https://maxcdn.bootstrapcdn.com/bootstrap/4.0.0/css/bootstrap.min.css"
integrity="sha384-Gn5384xqQ1aoWXA+058RXPxPg6fy4IWvTNh0E263XmFcJlSAwiGgFAW/dAiS6JXm" crossorigin="anonymous">
<link rel="stylesheet" href="style.css" media="screen">
<link rel="icon" type="image/x-icon" href="img/gp_favicon.ico">
<meta name="viewport" content="width=device-width, initial-scale=1">
<link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/font-awesome/4.7.0/css/font-awesome.min.css">
<style>
table, th {
border: 1px solid #000;
border-collapse: collapse;
text-align: center;
overflow: hidden;
text-overflow: ellipsis;
white-space: nowrap;
padding: 10px;
}
td {
border: 1px solid #000;
border-collapse: collapse;
text-align: left;
overflow: hidden;
text-overflow: ellipsis;
white-space: nowrap;
padding: 10px;
}
</style>
</head>
<body>
<nav class="navbar navbar-expand-md navbar-dark fixed-top bg-dark">
<a class="navbar-brand" href=".">Gammapy</a>
<button class="navbar-toggler" type="button" data-toggle="collapse" data-target="#navbarCollapse"
aria-controls="navbarCollapse" aria-expanded="false" aria-label="Toggle navigation">
<span class="navbar-toggler-icon"></span>
</button>
<div class="collapse navbar-collapse" id="navbarCollapse">
<ul class="navbar-nav mr-auto">
<li class="nav-item">
<a class="nav-link" href="https://github.com/gammapy/gammapy" target="_blank" rel="noopener"
aria-label="GitHub">
<svg width="20px" height="20px" class="navbar-nav-svg" xmlns="https://www.w3.org/2000/svg"
viewbox="0 0 512 499.36" focusable="false"><title>GitHub</title>
<path d="M256 0C114.64 0 0 114.61 0 256c0 113.09 73.34 209 175.08 242.9 12.8 2.35 17.47-5.56 17.47-12.34 0-6.08-.22-22.18-.35-43.54-71.2 15.49-86.2-34.34-86.2-34.34-11.64-29.57-28.42-37.45-28.42-37.45-23.27-15.84 1.73-15.55 1.73-15.55 25.69 1.81 39.21 26.38 39.21 26.38 22.84 39.12 59.92 27.82 74.5 21.27 2.33-16.54 8.94-27.82 16.25-34.22-56.84-6.43-116.6-28.43-116.6-126.49 0-27.95 10-50.8 26.35-68.69-2.63-6.48-11.42-32.5 2.51-67.75 0 0 21.49-6.88 70.4 26.24a242.65 242.65 0 0 1 128.18 0c48.87-33.13 70.33-26.24 70.33-26.24 14 35.25 5.18 61.27 2.55 67.75 16.41 17.9 26.31 40.75 26.31 68.69 0 98.35-59.85 120-116.88 126.32 9.19 7.9 17.38 23.53 17.38 47.41 0 34.22-.31 61.83-.31 70.23 0 6.85 4.61 14.81 17.6 12.31C438.72 464.97 512 369.08 512 256.02 512 114.62 397.37 0 256 0z"
fill="currentColor" fill-rule="evenodd"/>
</svg>
</a>
</li>
<li class="nav-item">
<a class="nav-link" href="gammapy_song.mp3" target="_blank" rel="noopener"
aria-label="Listen to the Gammapy song">
<svg width="20px" height="20px" class="navbar-nav-svg" xmlns="https://www.w3.org/2000/svg"
viewbox="0 0 512 499.36" focusable="false"><title>Listen to the Gammapy song</title>
<path d="M159.582,75.459v285.32c-14.274-10.374-32.573-16.616-52.5-16.616c-45.491,0-82.5,32.523-82.5,72.5s37.009,72.5,82.5,72.5 s82.5-32.523,82.5-72.5V168.942l245-60.615v184.416c-14.274-10.374-32.573-16.616-52.5-16.616c-45.491,0-82.5,32.523-82.5,72.5 s37.009,72.5,82.5,72.5s82.5-32.523,82.5-72.5V0L159.582,75.459z"
fill="currentColor" fill-rule="evenodd"/>
</svg>
</a>
</li>
<li class="nav-item">
<a class="nav-link" href="https://twitter.com/gammapyST" rel="noopener" target="_blank" title="Twitter" aria-label="Twitter">
<span><i class="fa fa-twitter-square" style="font-size:20px" fill="currentColor" fill-rule="evenodd"></i></span>
</a>
</li>
<li class="nav-item"><a class="nav-link" href="about.html">About</a></li>
<li class="nav-item"><a class="nav-link" href="news.html">News</a></li>
<li class="nav-item"><a class="nav-link" href="cta.html">CTA</a></li>
<li class="nav-item"><a class="nav-link" href="contact.html">Contact</a></li>
<li class="nav-item"><a class="nav-link active" href="team.html">Team</a></li>
<li class="nav-item"><a class="nav-link" href="contribute.html">Contribute</a></li>
<li class="nav-item"><a class="nav-link" href="https://docs.gammapy.org/">Documentation</a></li>
<li class="nav-item"><a class="nav-link" href="CoC.html">Code of Conduct</a></li>
<li class="nav-item"><a class="nav-link" href="acknowledging.html">Acknowledging</a></li>
</ul>
</div>
</nav>
<main role="main">
<div class="container">
<h1>Project & Team</h1>
<br>
<p>
<a href="#introduction">Introduction</a> | <a href="#overview">Overview</a>
</p>
<br><br>
<h2 id="introduction"><a href="#introduction"> Introduction </a></h2>
<p class="lead">
This page describes the Gammapy project organisation and the main roles and responsibilities in the Gammapy
team.
</p>
<p>
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 <a
href="https://www.mpi-hd.mpg.de/hfm/HESS/">H.E.S.S.</a>
and <a href="https://www.cta-observatory.org/">CTA</a> collaborations. We also took inspiration from the way
the <a href="https://www.astropy.org/team.html">Astropy</a> and <a
href="https://sunpy.org/project/">Sunpy</a>
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.
</p>
<p>
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 <a
href="contact.html">contact</a>.
Help is always welcome!
</p>
<br><br>
<h2 id="overview"><a href="#overview"> Overview </a></h2>
<p>
The following sections describe the major roles and responsibilities in the Gammapy team:
</p>
<ul>
<li><a href="#coordination-committee">Coordination committee</a></li>
<li><a href="#project-manager">Project managers</a></li>
<li><a href="#lead-developer">Lead developers</a></li>
<li><a href="#module-maintainer">Sub-package maintainers</a></li>
<li><a href="#contributors">Contributors</a></li>
<li><a href="#support">Institutional support</a></li>
<li><a href="#grants">Grants</a></li>
</ul>
<br><br>
<h2 id="coordination-committee"><a href="#cc"> Coordination Committee </a></h2>
<p class="lead">
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.
</p>
<p>
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 managers and lead developers are part of the Gammapy
CC.
</p>
<p>
Responsibilities include:
</p>
<ul>
<li>
Ensure that scientists and projects that are using Gammapy have reliable, good and long-term support
</li>
<li>
Promote the use of Gammapy by new projects, especially as science tool for CTA
</li>
<li>
Support and grow the Gammapy team (help find manpower and funding)
</li>
<li>
Make decisions on the scope, content and development priorities for the Gammapy package. <br>
In many cases this will be done via <a href="https://docs.gammapy.org/dev/development/pigs/">Proposal for
improvement of Gammapy (PIG)</a> documents.
</li>
<li>
Support and coordinate the use of Gammapy for scientific or technical studies and papers
</li>
<li>
The CC is the official contact point for the Gammapy project.
</li>
<li>
Appoint the Gammapy project managers (non-technical lead) and lead developers (technical lead)
</li>
<li>
CC members should join the Gammapy CC mailing list and calls for important discussions <br>
(day-to-day management is left to the project managers and lead developers).
</li>
</ul>
<p>
Current CC members (alphabetical order):
</p>
<ul>
<li><strong>Axel Donath</strong> (CfA/Harvard, U.S.A.)</li>
<li><strong>Bruno Khélifi</strong> (APC, France)</li>
<li><strong>Catherine Boisson</strong> (LUTh, France)</li>
<li><strong>Christopher van Eldik</strong> (Erlangen University, Germany)</li>
<li><strong>David Berge</strong>, as deputy <strong>Emma de Ona Wilhelmi</strong> (DESY, Germany)</li>
<li><strong>Fabio Acero</strong> (CEA/Irfu/DAp-AIM, France)</li>
<li><strong>Fabio Pintore</strong> (IASF Palermo/INAF, Italy), as deputy <strong>Martina Cardillo</strong> (Roma, INAF)</li>
<li><strong>Jim Hinton</strong> (MPIK, Germany)</li>
<li><strong>Jose Luis Contreras</strong> (UCM, Spain)</li>
<!-- <li><strong>Jose Enrique Ruiz</strong> (IAA/CSIC, Spain)</li> -->
<li><strong>Matthias Fuessling</strong> (S.U.S.S. coordinator of CTAO)</li>
<li><strong>Régis Terrier</strong> (APC, France)</li>
<li><strong>Roberta Zanin</strong> (Project Scientist of CTAO)</li>
<li><strong>Rubén López-Coto</strong> (IAA/CSIC, Spain)</li>
<li><strong>Stefan Funk</strong> (Erlangen University, Germany)</li>
</ul>
<br><br>
<h2 id="project-manager"><a href="#pm"> Project managers </a></h2>
<p class="lead">
The project manager and the deputy project manager are the non-technical executive lead for the Gammapy project.
</p>
<p>
The project managers are appointed by the Gammapy coordination committee, and work closely with the Gammapy
coordination committee, lead developers, contributors and users.
</p>
<p>
Responsibilities include:
</p>
<ul>
<li>
Organise and drive all non-technical aspects of the project on a day-to-day basis.
Keep the overview of ongoing activities, schedules and action items and follow up
to make sure all important things get done.
</li>
<li>
Serve as Gammapy coordination committee secretary (schedule and moderate calls; give status reports;
write minutes)
</li>
<li>Organise Gammapy user calls and training events via <a
href="https://github.com/gammapy/gammapy-meetings/">gammapy-meetings</a>
</li>
<li>
Keep an overview and help coordinate all activities that have some involvement of Gammapy,
such as e.g. papers, presentations or posters about or using Gammapy at gamma-ray astronomy meetings or
conferences, or tutorials at schools / workshops on gamma-ray astronomy data analysis.
</li>
<li>
Maintain Gammapy communication channels (mailing lists, slack, github, ...)
as well as the content at <a href="https://gammapy.org/">https://gammapy.org/</a>
</li>
</ul>
<p>
The current project manager is <strong>Bruno Khélifi</strong>, the deputy project manager is <strong> Christopher van Eldik</strong>.
</p>
<br><br>
<h2 id="lead-developer"><a href="#ld">Lead developers</a></h2>
<p class="lead">
The lead developers are the technical executive leads for the Gammapy project.
</p>
<p>
The lead developers are appointed by the Gammapy coordination committee, and work closely with the Gammapy
coordination committee, project managers and contributors.
</p>
<p>
Responsibilities include:
</p>
<ul>
<li>
Organise and drive all technical aspects of the project on a day-to-day basis.
Keep the overview of ongoing activities, schedules and action items and follow up
to make sure all important things get done.
</li>
<li>
Serve on the Gammapy coordination committee, as the link between CC and the development team.
</li>
<li>
Ensure that <a href="https://docs.gammapy.org/dev/development/pigs/">Proposal for
improvement of Gammapy (PIG)</a> documents are properly reviewed and
eventually decisions made by the CC.
</li>
<li>
Manage the Gammapy developer / maintainer / contributor team. Distribute tasks and assign
responsibilities to other Gammapy core developers.
</li>
<li>
Ensure that anyone interested in contributing to Gammapy development has good resources (documentation,
communication, mentoring) to get started. Specifically: maintain the Gammapy <a
href="https://docs.gammapy.org/dev/development">developer documentation</a>
that describes all aspects of Gammapy development (code, testing, documentation, processes).
</li>
<li>
Ensure Gammapy infrastructure is well set up and maintained (issue tracker and pull requests on Github,
continuous integration tests, documentation builds, releases and distribution).
</li>
<li>Organise Gammapy developer calls and coding sprints via <a
href="https://github.com/gammapy/gammapy-meetings/">gammapy-meetings</a>
</li>
<li>
Schedule Gammapy releases and define which fixes and features go in which release, taking the needs of
people and projects using Gammapy as well as available manpower for developments into account.
Either execute releases directly or assign a release manager.
</li>
</ul>
<p>
The current lead developers are <strong>Axel Donath</strong> and <strong>Régis Terrier</strong>.
</p>
<br><br>
<h2 id="module-maintainer"><a href="#mainteners">Sub-package maintainers</a></h2>
<p>Among the Gammapy core developer team, they are some experts that are devoted to the maintenance of some sub-packages.</p>
<p>They are in charge of:
<ul>
<li>perform initial triage of issues and pull requests,</li>
<li>supporting developers on tasks associated to the sub-package(s),</li>
<li>evaluating new pull requests for quality, API consistency and Gammapy coding standards,</li>
<li>taking care of the global design of the sub-package(s) in the context of the global Gammapy architecture,</li>
<li>participating to the User Support for questions related to the sub-package(s).</li>
</ul>
</p>
<p> The list of sub-package maintainers is given below:
<table width="80%" border="0" cellspacing="0" cellpadding="0">
<tr>
<th>Maintainer</th>
<th>Sub-package(s)</th>
</tr>
<tr>
<td>Quentin Remy (MPIK)</td>
<td><a href="https://docs.gammapy.org/dev/api-reference/catalog.html">catalog</a>,
<a href="https://docs.gammapy.org/dev/api-reference/datasets.html">datasets</a>,
<a href="https://docs.gammapy.org/dev/api-reference/modeling.html">modeling</a></td>
</tr>
<tr>
<td>Atreyee Sinha (GAE-UCM)</td>
<td><a href="https://docs.gammapy.org/dev/api-reference/datasets.html">datasets</a>,
<a href="https://docs.gammapy.org/dev/api-reference/irf.html">irf</a>,
<a href="https://docs.gammapy.org/dev/api-reference/makers.html">makers</a></td>
</tr>
</table>
</p>
<br><br>
<h2 id="contributors"><a href="#contributor">Contributors</a></h2>
<p>
As of March 2021, there have been ~70 different contributors to Gammapy from ~10 countries and
~200 people are subscribed to the Gammapy Slack. An overview of all contributors can be found on
<a href="https://github.com/gammapy/gammapy/graphs/contributors">GitHub</a>.
</p>
<p>
There is no useful automatic way to measure how much someone contributed. The most common measure used
is commits to the code repository. However the number of commits is not the only a useful measure.
Some contributors spent several days to find and fix an important bug, or implement a big and complex
feature that only results in a single commit. If someone makes a good bug report or does code review
or mentoring or organisational work for Gammapy it does not show up in the commit statistic at all.
Please know that any contribution to the Gammapy project is valued!
</p>
<p>
The list of contributions into conferences, hands-on sessions and schools, and for recipies can be found on the following list:
<ul>
<li><a href="https://github.com/gammapy/gammapy-presentations">conferences</a>, </li>
<li><a href="https://github.com/gammapy/gammapy-recipes">recipies</a>, </li>
<li><a href="https://github.com/gammapy/gammapy-handson">hands-on sessions and schools</a>. </li>
</ul>
</p>
<br><br>
<h2 id="support"><a href="#support">Supporting institutions</a></h2>
<p>
People involved in Gammapy are coming from different institutions, laboratories and universities. We acknowledge
them for their daily support. Here are listed the main institutions (alphabetical order):
<ul>
<li><strong>AIM</strong> (Astrophysique, instrumentation, modélisation), DAp-CEA/CNRS, Saclay/France -
<a href="http://irfu.cea.fr/Phocea/Vie_des_labos/Ast/ast_service.php?id_unit=3">Web site</a></li>
<li><strong>APC</strong> (AstroParticules et Cosmologie), Université de Paris/CNRS, Paris/France -
<a href="https://www.apc.univ-paris7.fr/APC_CS/">Web site</a></li>
<li><strong>DESY</strong> (Deutsches Elektronen-Synchrotron), Zeuthen/Germany -
<a href="https://www.desy.de/research/astroparticle_physics/index_eng.html">Web site</a></li>
<li><strong>ECAP</strong> (Erlangen Center for Astroparticle Physics), Friedrich-Alexander Univervität, Erlangen/Germany -
<a href="https://ecap.nat.fau.de/">Web site</a></li>
<li><strong>IAA-CSIC</strong> (Instituto de Astrofísica de Andalucía), Consejo Superior de Investigaciones Científicas, Granada/Spain -
<a href="https://www.iaa.csic.es/">Web site</a></li>
<li><strong>INAF</strong> (Istituto Nazionale di Astrofisica), Italy -
<a href="http://www.inaf.it/en">Web site</a></li>
<li><strong>LUTh</strong> (Laboratoire Univers et Théorie), CNRS/Observatoire de Paris, Meudon/France -
<a href="https://luth.obspm.fr/">Web site</a></li>
<li><strong>MPIK</strong> (Max-Planck-Institut für Kernphysik), Max-Planck-Gesellschaft, Heidelberg/Germany -
<a href="https://www.mpi-hd.mpg.de/mpi/de/">Web site</a></li>
<li><strong>Observatoire de Paris</strong>, Paris-Meudon-Nançay/France -
<a href="https://www.obspm.fr/">Web site</a></li>
<li><strong>UCM</strong> (Universidad Complutense Madrid), Madrid/Spain -
<a href="https://www.ucm.es/">Web site</a></li>
<li><strong>CTA Observatory</strong> - <a href="https://www.cta-observatory.org/">Web site</a></li>
</ul>
</p>
<br>
<center>
<img src="img/LogoList_V2021_V2.png" style="width:70%;" alt="Institutions supporting the project" align="middle">
</center>
<br><br>
<h2 id="grants"><a href="#grants">Grants</a></h2>
<p>
Several grants have helped to support the development of Gammapy, including:
<ul>
<li><strong>ESCAPE H2020 project</strong> (European Science Cluster of Astronomy & Particle Physics ESFRI research Infrastructure):
grant agreemant n. 824064, 2019/2022 in Germany and France (from EU)</li>
<li><strong>PECORA ANR project</strong>: 2019/2022 (from France)</li>
<li><strong>Action Fédératrice CTA</strong>: 2018, 2019, 2020, 2021 (from Observatoire de Paris)</li>
<li><strong>Action Pluri-annauelle Initiatrice "Astrophysique des hautes énergies"</strong>: 2022,
2023 (from Observatoire de Paris)</li>
<li><strong>ASTERICS H2020 project</strong> (Astronomy ESFRI & Research Infrastructure Cluster):
grant agreement n. 653477, 2015/2019 in France and Spain (from EU)</li>
<li><strong>Spanish MINECO/AEI projects</strong>: FPA2015-69210-C6-3-R, FPA2017-82729-C6-3-R, AYA2016-8089-P (from Spain)</li>
</ul>
</p>
</div>
</main>
<footer class="container">
<hr>
<p>© Gammapy project</p>
</footer>
<script src="https://code.jquery.com/jquery-3.2.1.slim.min.js"
integrity="sha384-KJ3o2DKtIkvYIK3UENzmM7KCkRr/rE9/Qpg6aAZGJwFDMVNA/GpGFF93hXpG5KkN"
crossorigin="anonymous"></script>
<script src="https://cdnjs.cloudflare.com/ajax/libs/popper.js/1.12.9/umd/popper.min.js"
integrity="sha384-ApNbgh9B+Y1QKtv3Rn7W3mgPxhU9K/ScQsAP7hUibX39j7fakFPskvXusvfa0b4Q"
crossorigin="anonymous"></script>
<script src="https://maxcdn.bootstrapcdn.com/bootstrap/4.0.0/js/bootstrap.min.js"
integrity="sha384-JZR6Spejh4U02d8jOt6vLEHfe/JQGiRRSQQxSfFWpi1MquVdAyjUar5+76PVCmYl"
crossorigin="anonymous"></script>
</body>
</html>