forked from naemon/naemon.github.io
-
Notifications
You must be signed in to change notification settings - Fork 0
/
index.html
68 lines (49 loc) · 3.65 KB
/
index.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
<!DOCTYPE html>
<html>
<head>
<meta charset='utf-8' />
<meta http-equiv="X-UA-Compatible" content="chrome=1" />
<meta name="description" content="Naemon.github.io : The naemon website" />
<link rel="stylesheet" type="text/css" media="screen" href="stylesheets/stylesheet.css">
<title>Naemon.github.io</title>
</head>
<body>
<!-- HEADER -->
<div id="header_wrap" class="outer">
<header class="inner">
<a id="forkme_banner" href="https://github.com/naemon">View on GitHub</a>
<h1 id="project_title">Naemon.github.io</h1>
<h2 id="project_tagline">The naemon website</h2>
</header>
</div>
<!-- MAIN CONTENT -->
<div id="main_content_wrap" class="outer">
<section id="main_content" class="inner">
<h2>
<a name="welcome-to-naemon" class="anchor" href="#welcome-to-naemon"><span class="octicon octicon-link"></span></a>Welcome to Naemon</h2>
<p>This is the (very) brief homepage for Naemon, the latest fork of Nagios Core.</p>
<p>Naemon forks off on the latest release of Nagios 4.0.1, with some additional patches on top. Notably, NASA can use Naemon to monitor their supercomputer cluster without any special configuration tweaking, and rotated logs are no longer truncated. In the future, I expect compatibility will diverge, but we will make sure that external API's such as livestatus, the query handler, the object cache file and status data file remain more or less the same. Object configuration won't change hugely in the near future either. Instead we'll focus on extending existing integration points and improving performance and stability in the core.</p>
<h3>
<a name="why-fork" class="anchor" href="#why-fork"><span class="octicon octicon-link"></span></a>Why fork?</h3>
<p>I (Andreas Ericsson) got kicked out from being a Nagios core developer after having written an overwhelming majority (94.5%) of the changes that took Nagios from version 3 to version 4. Since I feel that was mostly a political move in order to prevent the project from being associated with me rather than Nagios Enterprises rather than based on technical or personal reasons, I decided to launch my own project. Fortunately for me, a lot of people expressed interest in the project right from the start, and a few of them even want to help out and make it really great.</p>
<h3>
<a name="whos-doing-what" class="anchor" href="#whos-doing-what"><span class="octicon octicon-link"></span></a>Who's doing what?</h3>
<ul>
<li>Andreas Ericsson (<a href="https://github.com/ageric" class="user-mention">@ageric</a>) - Core developer</li>
<li>Dan Wittenberg (<a href="https://github.com/dwittenberg2008" class="user-mention">@dwittenberg2008</a>) - RPM packaging and testing</li>
<li>Robin Sonefors (<a href="https://github.com/ozamosi" class="user-mention">@ozamosi</a>) - Core developer</li>
<li>Sven Nierlein (<a href="https://github.com/sni" class="user-mention">@sni</a>) - Core/GUI developer</li>
<li>You - Whatever you like and can :)</li>
</ul><h3>
<a name="how-can-i-help" class="anchor" href="#how-can-i-help"><span class="octicon octicon-link"></span></a>How can I help?</h3>
<p>Send an email to <a href="mailto:ageric79@gmail.com">ageric79@gmail.com</a>. Everyone's welcome, assuming you're competent, interested and friendly. We're currently in desperate need of a logo designer and web designer/maintainer but, as with all sane opensource projects, "patches welcome" ;-)</p>
</section>
</div>
<!-- FOOTER -->
<div id="footer_wrap" class="outer">
<footer class="inner">
<p>Published with <a href="http://pages.github.com">GitHub Pages</a></p>
</footer>
</div>
</body>
</html>