------=_Part_7570_4630138.1267552232940
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Hi Ethan,=20
I don't want to response in mailing-list.=20
Thanks a lot Ethan for this idea and your response. We wanted a roadmap and=
your opinion in the future. We didn't want to insult Nagios Core Team or o=
ther, we just want to work, communicate with you to answer questions from t=
he community and not answer them "Wait and See".=20
I think that I use your Ask Ethan to give you my opinion and ideas to devel=
op the communication between Community and You.=20
Regards=20
Fronteau Romuald=20
=C3=89quipe Communaut=C3=A9 Nagios Francophone=20
[email protected]=20
http://www.nagios-fr.org=20
----- Mail Original -----=20
De: "Ethan Galstad" =20
=C3=80: "Nagios Developers List" =20
Envoy=C3=A9: Mardi 2 Mars 2010 05:55:29=20
Objet: [Nagios-devel] Ask Ethan=20
The recent messages on this list indicate a need for better=20
communication between parties. It may be exciting to start a flame war=20
or launch personal attacks based on unfounded assumptions, but its not=20
effective or beneficial.=20
If you have questions for me about what I think regarding the future of=20
the Nagios Project, commercialization of Nagios, Nagios XI, trademarks,=20
community stuff, etc. - just ask. In order to expedite and coordinate=20
responses to share with the community, I've created a new "Ask Ethan"=20
form online where you can submit questions to me about whatever you'd=20
like. I'll answer these questions in the monthly Nagios News that goes=20
out. As long as there continues to be new questions, I'll do my best to=20
make "Ask Ethan" a permanent monthly section in the newsletter. Submit=20
a question at:=20
http://www.nagios.com/askethan=20
Here are some quick responses to questions I've seen asked. If you want=20
more detail on any of these, submit an "Ask Ethan" question at the link=20
above and I'll go into more depth in the newsletter...=20
1. Nagios Core and other OSS components of the Nagios Project are=20
important to both myself and Nagios Enterprises. Nagios XI (like many=20
other commercial solutions) is based on those components and we=20
definitely want those projects to flourish in the future. *I* may not=20
be the person actually coding or integrating patches (I've done that for=20
over a decade now), but I'm dedicated to finding ways to ensure the=20
project continues for at least the next decade. And just so there's no=20
confusion on the subject, Nagios Core will always be free as in speech=20
and beer.=20
2. Our commercial Nagios XI solution is not 100% Open Source, and it=20
probably won't ever be in its entirety. There are some really great=20
components that we license from other parties and we plan to include=20
other licensed components in the future. Why? They provide a better=20
solution to our customers than OSS alternatives (if they even exist).=20
Most all other commercial Nagios solutions out there go the same route.=20
3. While its relatively new for Nagios Enterprises, commercialization of=20
Nagios is going to expand in the future, so we can continue to provide=20
more great solutions for the people that need them. Commercialization=20
also makes it easier to provide resources to ensure the existing free=20
OSS projects prosper, and that new projects can be funded. If you=20
object to the commercialization of Nagios, consider this: the only=20
reason I wrote Nagios and released it as an OSS project in the first=20
place is because I intended to use it for commercial purposes.=20
4. We have, are, and will continue to regulate the use of the Nagios=20
mark and prevent its misuse to ensure the integrity of the Nagios name=20
and the future of the Nagios Project - just as I was personally doing=20
long before the conception of Nagios Enterprises. Our trademark policy=20
is almost an exact clone of the Ubuntu trademark policy. Its a great=20
policy that fits the needs of both community advocacy and the commerci
...[email truncated]...
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]