-
Notifications
You must be signed in to change notification settings - Fork 12
/
Copy pathcontact.html
85 lines (73 loc) · 3.64 KB
/
contact.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
<!DOCTYPE html>
<html>
<style type="text/css" media="screen">
h2[id]::before {
display: block;
content: " ";
margin-top: -125px;
height: 125px;
}
</style>
<script src="scripts/matomo.js" defer></script>
<script src="scripts/myscripts.js" defer></script>
<script src="scripts/includeHTML.js" defer></script>
<div data-include="header.html"></div>
<body>
<div data-include="navbar.html"></div>
<main>
<div class="container">
<h1>Contact</h1>
<br>
<p>This page lists the contact points and communication channels for Gammapy </p>
<ul class="">
<li>
Gammapy slack (<a href="https://gammapy.slack.com">gammapy.slack.com</a>)
<br>
Many Gammapy developers and users are using the Gammapy Slack to chat.
There is a <strong>#general</strong> and some other Slack channels that will go to many people.
But you can also join and use the Gammapy slack for 1:1 text chat with someone from the Gammapy team to
get help with Python, git, Gammapy, ...
The Gammapy slack is private, and the history is not archived, i.e. is lost at some point.
<br>
To get access, sign-up <a href="https://join.slack.com/t/gammapy/signup">here</a>, and wait a bit for moderator approval.
</li>
<li>
Gammapy CTAO mailing list
(<a href="mailto:[email protected]">gammapy-cta-l [at] in2p3 [dot] fr</a>,
<a href="https://listserv.in2p3.fr/archives/gammapy-cta-l.html">archive</a>)
<br>
Ask any question about CTAO data analysis with Gammapy.
This is a private mailing list, so discussing CTAO-internal information is OK.
<br>
Sign up <a href="https://listserv.in2p3.fr/cgi-bin/wa?SUBED1=GAMMAPY-CTA-L&A=1">here</a>, and wait a bit
for moderator approval.
</li>
<li>
Gammapy coordination committee mailing list
(<a href="mailto:[email protected]">gammapy-coordination-l [at] in2p3 [dot] fr</a>,
<a href="https://listserv.in2p3.fr/archives/gammapy-coordination-l.html">archives</a>)
<br>
Use this mailing list to contact the Gammapy coordination committee.
Anyone can post, but only coordination committee members can read it.
Don't be shy: just email us if you have any question or comment about Gammapy!
</li>
<li>
Github (<a href="https://github.com/gammapy/gammapy">https://github.com/gammapy/gammapy</a>)
<br>
The place where we develop Gammapy (code, tests, documentation).
If you want to report an issue, you can do it directly in the issue tracker there,
or by posting on the mailing lists mentioned above.
<br>
You can make a GitHub account yourself, it's free.
</li>
</ul>
</div>
</main>
<!-- Footer Section -->
<div data-include="footer.html"></div>
<script src="https://cdn.jsdelivr.net/npm/@popperjs/[email protected]/dist/umd/popper.min.js"></script>
<script src="https://cdn.jsdelivr.net/npm/[email protected]/dist/js/bootstrap.bundle.min.js" integrity="sha384-YvpcrYf0tY3lHB60NNkmXc5s9fDVZLESaAA55NDzOxhy9GkcIdslK1eN7N6jIeHz" crossorigin="anonymous"></script>
<script src="https://cdn.jsdelivr.net/npm/[email protected]/dist/js/bootstrap.bundle.min.js"></script>
<script src="scripts/navbarCollapse.js" defer></script>
</body>
</html>