4 <title>grml.org - Contact</title>
5 <meta name="Title" content="grml.org - Contact" />
6 <meta name="Author" content="the grml team [www.grml.org/team/]" />
7 <meta name="Keywords" content="grml.org, grml" />
8 <meta name="Description" content="Contact at grml.org" />
9 <meta name="Abstract" content="grml, just another linux-distribution" />
10 <meta name="fdse-index-as" content="http://www.grml.org/contact/" />
11 <meta name="Robots" content="index,follow" />
12 <meta name="Language" content="english" />
13 <meta name="identifier-url" content="http://www.grml.org/" />
14 <meta name="MSSmartTagsPreventParsing" content="true" />
15 <meta http-equiv="imagetoolbar" content="no" />
16 <link rel="home" href="/" title="grml.org" />
17 <link rel="help" href="/features/" title="About" />
18 <link rel="author" href="/team/" title="Team" />
19 <link rel="icon" href="/favicon.png" type="image/png" />
20 <link rel="stylesheet" href="/style.css" type="text/css" />
24 [% INCLUDE static.inc %]
28 <p><img style="float: right; border: 0" src="/img/mail.png" alt="*" /></p>
32 <p>For general questions please join the Grml user mailinglist (see below).</p>
34 <p>If you have found a bug please <a href="/bugs/">report it</a>.</p>
36 <p>For commercial support and services please send us mail
37 to business (at) grml.org.</p>
39 <a name="mailinglist"></a>
40 <h2>Mailing lists</h2>
42 <p>If you want to be notified when a <strong>new Grml
43 release</strong> is available, subscribe to the
44 read-only <a href="http://ml.grml.org/mailman/listinfo/grml-announce">Grml
45 announce mailing list</a>.</p>
47 <p>If you want to participate in the <strong>mailing list of
48 Grml</strong>, please subscribe to the <a
49 href="http://ml.grml.org/mailman/listinfo/grml">Grml user
50 mailing list</a>. Anyone can post to this mailing list, but if you
51 are not already subscribed, your message will need moderator approval before being posted. This way
52 we limit the amount of spam that makes it to the list. The Grml user
53 mailing list is available <a
54 href="http://dir.gmane.org/gmane.linux.distributions.grml.user">via
55 gmane</a> as well.</p>
57 <p>If you are interested in following the <strong>development of Grml</strong> you might be
58 interested in the <a href="http://ml.grml.org/mailman/listinfo/grml-devel">Grml developer
59 mailing list</a>. The <a
60 href="http://ml.grml.org/mailman/listinfo/git-commits">Grml repository
61 commits mailing list</a> tracks all the pushed commits to <a
62 href="https://git.grml.org/">Grml's git repositories</a>, while we're
63 also present on <a href="https://github.com/grml/">github</a>. Changes
64 in Grml's Debian repository can be tracked via the <a
65 href="http://ml.grml.org/mailman/listinfo/grml-testing-changes">Grml
66 Testing-changes mailing list</a>. We track issues at <a
67 href="https://github.com/grml/grml/issues">github.com/grml/grml/issues</a>.
68 Several Grml sub-projects (grml-debootstrap, grml-etc-core,
69 grml2usb,...) have their own repository and issue tracking, see <a
70 href="https://github.com/grml/">github.com/grml/</a> to get an
71 overview. If you're unsure where to report an issue though, feel free
72 to use github.com/grml/grml/issues though.</p>
74 <p><strong>Notice:</strong> All Grml mailing lists are <strong>English
80 <p>You can find us in <a href="irc://irc.freenode.net/grml">#grml on
81 irc.freenode.org</a>. Channel language is English.</p>
85 [% INCLUDE static_bottom.inc %]