mirror of
https://github.com/librenms/librenms.git
synced 2024-10-07 16:52:45 +00:00
b46735b9c2
1. "is ..." -> "has to do with ..." 2. reformulation of the sentence: it wasn't complete, because after "Thanks to one of our users, Dan Brown ..." there was just "additional information" about Dan Brown but not what we actually have thanks to him. I think this formulation makes it a little bit easier to understand the sentence 3. cpu architect -> CPU architecture (i thought it was the common way to state it. Also, abbreviations are generally uppercase) Hope this helps :)
63 lines
3.1 KiB
Markdown
63 lines
3.1 KiB
Markdown
source: General/Welcome-to-Observium-users.md
|
|
|
|
LibreNMS is a fork of Observium. The reason for the fork has nothing to do
|
|
with Observium's [move to community vs. paid versions][1]. It is simply
|
|
that we have different priorities and values to the Observium development
|
|
team. We decided to fork (reluctantly) because we like using Observium,
|
|
but we want to collaborate on a community-based project with like-minded
|
|
IT professionals. See [README.md][2] and the references there for more
|
|
information about the kind of community we're trying to promote.
|
|
|
|
LibreNMS was forked from [the last GPL-licensed version of Observium][3].
|
|
|
|
Thanks to one of our users, Dan Brown, who has written a [migration script][10], you can easily move your Observium install over to LibreNMS. This also takes care of moving from one CPU architecture to another. Give it a try :)
|
|
|
|
How LibreNMS will be different from Observium:
|
|
|
|
- We will have an inclusive community, where it's OK to ask stupid
|
|
questions, and OK to ask for things that aren't on the roadmap. If you'd
|
|
like to see something added, add or comment on the relevant issue in our
|
|
[Community forum][9].
|
|
- Development decisions will be community-driven. We want to make software
|
|
that fulfills its users' needs.
|
|
- There are no plans for a paid version, and we don't anticipate this ever
|
|
changing.
|
|
- There are no current plans for paid support, but this may be added later
|
|
if there is sufficient demand.
|
|
- We use git for version control and GitHub for hosting to make it as easy
|
|
and painless as possible to create forked or private versions.
|
|
|
|
Reasons why you might want to use Observium instead of LibreNMS:
|
|
|
|
- You have a financial investment in Observium and aren't concerned about
|
|
community contributions.
|
|
- You don't like the [GNU General Public License, version 3][5] or the
|
|
[philosophy of Free Software/copyleft][6] in general.
|
|
|
|
Reasons why you might want to use LibreNMS instead of Observium:
|
|
|
|
- You want to work with others on the project, knowing that [your
|
|
investment of time and effort will not be wasted][7].
|
|
- You want to add and experiment with features that are not a priority for
|
|
the Observium developers. See [CONTRIBUTING][8] for more details.
|
|
- You want to make use of the additional features LibreNMS can offer.
|
|
|
|
[1]: http://postman.memetic.org/pipermail/observium/2013-October/003915.html
|
|
"Observium edition split announcement"
|
|
[2]: https://github.com/librenms/librenms/blob/master/README.md
|
|
"LibreNMS README"
|
|
[3]: http://fisheye.observium.org/rdiff/Observium?csid=3251&u&N
|
|
"Link to Observium license change"
|
|
[5]: https://github.com/librenms/librenms/blob/master/LICENSE.txt
|
|
"LibreNMS copy of GPL v3"
|
|
[6]: http://www.gnu.org/philosophy/free-sw.html
|
|
"Free Software Foundation - what is free software?"
|
|
[7]: http://libertysys.com.au/blog/observium-and-gpl
|
|
"Paul's blog on what the GPL offers users"
|
|
[8]: https://docs.librenms.org/General/Contributing/
|
|
"Contribution guidelines"
|
|
[9]: https://community.librenms.org
|
|
"LibreNMS issue database at GitHub"
|
|
[10]: https://vlan50.com/2015/04/17/migrating-from-observium-to-librenms/
|
|
"Migrating from Observium to LibreNMS"
|