Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Ethan=2C
Thanks for theses responses
AP
> Date: Mon=2C 1 Mar 2010 22:55:29 -0600
> From: [email protected]
> To: [email protected]
> Subject: [Nagios-devel] Ask Ethan
>=20
>=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=2C 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=2C commercialization of Nagios=2C Nagios XI=2C tradema=
rks=2C=20
> community stuff=2C etc. - just ask. In order to expedite and coordinate=
=20
> responses to share with the community=2C 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=2C I'll do my best t=
o=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=2C 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)=2C 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=2C Nagios Core will always be free as in speech=
=20
> and beer.
>=20
> 2. Our commercial Nagios XI solution is not 100% Open Source=2C 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=2C commercialization o=
f=20
> Nagios is going to expand in the future=2C 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=2C and that new projects can be funded. If you=20
> object to the commercialization of Nagios=2C 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=2C are=2C 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 commercial=
=20
> legal requirements for brand protection=2C anti-dilution=2C and consumer=
=20
> confusion. Open Source licenses like the GPL only address copyright -=20
> not trademark. Trademarks are a separate type of intellectual property=20
> that is out of scope with what copyright covers.
>=20
> 5. I've dedicated the past 11 years to the Nagios project and have done=20
> my best to keep the project going and keep it within the scope of what a=
=20
>
...[email truncated]...
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]