From cf752076d5c202b304681c3154cf93ecd5b6b4b2 Mon Sep 17 00:00:00 2001 From: Ton Voon Date: Fri, 21 Jan 2005 00:01:54 +0000 Subject: Changing copyright to the Nagios Plugins Development Team, rather than individual names. Also, clarified use of ACKNOWLEDGEMENTS, THANKS.in and AUTHORS git-svn-id: https://nagiosplug.svn.sourceforge.net/svnroot/nagiosplug/nagiosplug/trunk@1091 f882894a-f735-0410-b71e-b25c423dba1c --- doc/developer-guidelines.sgml | 81 ++++++++----------------------------------- 1 file changed, 14 insertions(+), 67 deletions(-) diff --git a/doc/developer-guidelines.sgml b/doc/developer-guidelines.sgml index 1b9faa5d..c531fbb0 100644 --- a/doc/developer-guidelines.sgml +++ b/doc/developer-guidelines.sgml @@ -5,68 +5,13 @@ - Karl - DeBisschop - -
karl@debisschop.net
-
-
- - - Ethan - Galstad - - Author of Nagios - - - -
netsaint@linuxbox.com
-
-
- - - Hugo - Gayosso - -
hgayosso@gnu.org
-
-
- - - - Subhendu - Ghosh - -
sghosh@sourceforge.net
-
-
- - - Stanley - Hopcroft - -
stanleyhopcroft@sourceforge.net
-
-
- - - Ton - Voon - -
tonvoon@users.sourceforge.net
-
-
- - - Jeremy T - Bouse - -
undrgrid@users.sourceforge.net
-
+ + Nagios Plugins Development Team +
- 2002 + 2005 Nagios plug-in development guidelines @@ -77,7 +22,7 @@ - 2000 - 2004 + 2000 - 2005 Nagios Plugins Development Team @@ -89,8 +34,8 @@ the plug-in developers and encourage the standarization of the different kind of plug-ins: C, shell, perl, python, etc. - Nagios Plug-in Development Guidelines Copyright (C) 2000-2003 - (Karl DeBisschop, Ethan Galstad, Stanley Hopcroft, Subhendu Ghosh, Ton Voon, Jeremy T. Bouse) + Nagios Plug-in Development Guidelines Copyright (C) 2000-2005 + (Nagios Plugins Team) Permission is granted to make and distribute verbatim copies of this manual provided the copyright notice and this @@ -642,10 +587,12 @@
Comments You should use /* */ for comments and not // as some compilers do not handle the latter form. - There should not be any named credits in the source code - contributors - should be added - into the AUTHORS file instead. The only exception to this is if a routine - has been copied from another source. + If you have copied a routine from another source, make sure the licence + from your source allows this. Add a comment referencing the ACKNOWLEDGEMENTS + file, where you can put more detail about the source. + For contributed code, do not add any named credits in the source code + - contributors should be added into the THANKS.in file instead. +
CVS comments @@ -665,7 +612,7 @@ If the change is due to a contribution, please quote the contributor's name and, if applicable, add the SourceForge Tracker number. Don't forget to -update the AUTHORS file. +update the THANKS.in file.
-- cgit v1.2.3-74-g34f1