From b66863abf0cb51295ba20caba9d206a4d1a82c72 Mon Sep 17 00:00:00 2001 From: Pilou Date: Thu, 11 Jan 2018 05:23:36 +0100 Subject: [PATCH] =?UTF-8?q?dev=5Fguide:=20don't=20ask=20to=20use=20'=C2=A9?= =?UTF-8?q?=20Ansible=20Project'=20(#34704)?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit contributor don't sign any copyright assignment, then this makes no sense. --- .../dev_guide/developing_modules_documenting.rst | 13 ++++++------- 1 file changed, 6 insertions(+), 7 deletions(-) diff --git a/docs/docsite/rst/dev_guide/developing_modules_documenting.rst b/docs/docsite/rst/dev_guide/developing_modules_documenting.rst index 902e909a5d..8961b8b973 100644 --- a/docs/docsite/rst/dev_guide/developing_modules_documenting.rst +++ b/docs/docsite/rst/dev_guide/developing_modules_documenting.rst @@ -43,15 +43,14 @@ code. #!/usr/bin/python - # Copyright: (c) 2017, Ansible Project + # Copyright: (c) 2018, Terry Jones # GNU General Public License v3.0+ (see COPYING or https://www.gnu.org/licenses/gpl-3.0.txt) -Every file should have a copyright line with the original copyright holder. -Major additions to the module (for instance, rewrites) may add additional -copyright lines. Code from the Ansible community should typically be assigned -as "Copyright (c) 2017 Ansible Project" which covers all contributors. Any -legal questions need to review the source control history, so an exhaustive -copyright header is not necessary. +Every file should have a copyright line (see `The copyright notice `_) +with the original copyright holder. Major additions to the module (for +instance, rewrites) may add additional copyright lines. Any legal questions +need to review the source control history, so an exhaustive copyright header is +not necessary. The license declaration should be ONLY one line, not the full GPL prefix. If you notice a module with the full prefix, feel free to switch it to the