From 550a1b5f02d94b1683d4d0a8dcf0977bdcad6a13 Mon Sep 17 00:00:00 2001 From: Michael DeHaan Date: Sat, 9 Feb 2013 13:48:28 -0500 Subject: [PATCH] Remove mercurial module reference now that we have a cleaned up hg module in core now! --- docsite/rst/contrib.rst | 11 ++++------- 1 file changed, 4 insertions(+), 7 deletions(-) diff --git a/docsite/rst/contrib.rst b/docsite/rst/contrib.rst index fe17caebcc1..686f3f02b81 100644 --- a/docsite/rst/contrib.rst +++ b/docsite/rst/contrib.rst @@ -9,20 +9,17 @@ Ansible Modules ``````````````` Ansible modules are a way of adding new client-side logic to ansible. -They can be written in any language. +They can be written in any language. Generally our goal is to include most modules in core, +though a few may remain outside of core depending on use cases and implementations. - `Official "core" ansible modules `_ - various -- `mercurial `_ - bradobro - `zypper (bash module example) `_ - jp\_mens - `homebrew `_ - swehack - `additional provisioning-related modules `_ - jhoekx and dagwieers - `dynamic dns updates `_ - jp\_mens -- `RabbitMQ `_ - elventear -Python modules using 0.6 and later can and should use the common "AnsibleModule" -class to dramatically reduce the amount of boilerplate code required. -Not all modules above yet take advantage of this feature. See the -official documentation for more details. +All python modules should use the common "AnsibleModule" class to dramatically reduce the amount of boilerplate code required. +Not all modules above may take advantage of this feature. See the official documentation for more details. Selected Playbooks ``````````````````