[Nagiosplug-devel] Forking the contrib section?

Thomas Guyot-Sionnest dermoth at aei.ca
Sat Jul 18 00:41:48 CEST 2009


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 17/07/09 12:27 PM, Ton Voon wrote:
> On 17 Jul 2009, at 04:11, Thomas Guyot-Sionnest wrote:
> 
>> However many need the
>> Nagios-plugins tree to compile, and most lost their original authors.
>> Meanwhile some useful plugins in there get patches from time to time
>> that we don't really want to apply because we don't really want to
>> support that unsupported section.
> 
> Isn't the compile problem one that should be solved with a nagiosplug- 
> dev library?

Indeed, and I would really like to get this project started. The next
step is to decide whenever we want a functional or object-oriented api
and start designing it! We had some talks in #nagios about that recently.

>> I'd like to fork /contrib to a separate git repository and add a "mob"
>> user (unrestricted check-in access to the "mob" branch) for people to
>> commit things , then we can do a short review from time to time and
>> merge changes from the mob branch.
>>
>> Think of this as a service to help the community maintaining these
>> plugins without any guarantee regarding the quality and safety of  
>> these
>> plugins from the Nagios-Plugins team. I believe that it would  
>> relieve us
>> of that plugins section and help the community getting patches in.
>>
>> /contrib could then become a git submodule that can be included for
>> compiling the plugins.
> 
> I think this is a good idea, though I have doubts on how used it will  
> be.

It can't be worse than what it is now ;)

> I think we're getting to the stage where I think we can start  
> accepting some more plugins into the core. I'd welcome any one wishing  
> to join the team and look after specific new plugins.

Sure, we could start a review of some plugins. Maybe take some
interesting ones in Nagiosexange too if they fit.

OTOH if we add any new plugin I'd like that at least Perl plugins use
N::P and and C plugins do not use any deprecated code, so we don't add
ourself more work in the future :). And they should have tests too...


- --
Thomas
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFKYP4s6dZ+Kt5BchYRAilxAKDgerO4tgef89JI72txb27B1NOoTwCg4w4r
VmPCtUwP9y1h9aGapb/X97w=
=yJBH
-----END PGP SIGNATURE-----




More information about the Devel mailing list