Hi all,
I start to hack the master tree for the new modules layout. Now it pass all
tests, but it add a new mandatory parameter for the configuration.
I think with the change that will occurs, it won't be a simple update, but
a more deep change. So It won't be a 1.6 version, but a 2.0 one.
I think we will also change the project vision. The "all in one solution"
was maybe too much. What make us happy to code is when we add a new feature
or thing like the new shinken.io website, not to hack again and again the
install script to manage more and more add-ons.
The new version will be also a way to change this, and to make us focus on
where Shinken is really great : distributed env and flexibility. So I'll
propose soon a new vision, with no more a "monitoring solution" point of
view, but more with a "monitoring framework" one.
Numerous trainees around the world will hate me for doing this, but I think
we should more focus on making devops job easier, than to help a trainee to
install a tool without having to read a documentation.
The next change in the master tree will be remove of the modules that will
be put in the github organization part. I'll open a call so every one will
have a way to be the official maintainer on the shinken.io website, so if
you are proud about a module, it's will be time to show it :)
Jean
------------------------------------------------------------------------------
How ServiceNow helps IT people transform IT departments:
1. A cloud service to automate IT design, transition and operations
2. Dashboards that offer high-level views of enterprise services
3. A single system of record for all IT processes
http://p.sf.net/sfu/servicenow-d2d-j
_______________________________________________
Shinken-devel mailing list
Shinken-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/shinken-devel
