From 101dec2f8fbfb7cce4dfad03cf052936859a0c8b Mon Sep 17 00:00:00 2001 From: Ton Voon Date: Wed, 9 Nov 2005 09:31:58 +0000 Subject: Updated dev guidelines to link to NagiosExchange. Removed project admin notes from guidelines into separate file git-svn-id: https://nagiosplug.svn.sourceforge.net/svnroot/nagiosplug/nagiosplug/trunk@1275 f882894a-f735-0410-b71e-b25c423dba1c diff --git a/doc/NEW_STARTERS b/doc/NEW_STARTERS new file mode 100644 index 0000000..89a1a9a --- /dev/null +++ b/doc/NEW_STARTERS @@ -0,0 +1,20 @@ +NEW STARTERS + +These are the steps for adding someone to the team. + +Need to know: + - Name + - Sourceforge id + - Type of member (translator, developer, release manager, project administrator) + +1. Add member to nagiosplug-team mailing list and to the nagiosplug-checkins + mailing list (via Privacy Options) +2. Add Sourceforge access: + - Translator: CVS access, Shell access, Release Tech (no) + - Developer: CVS access, Shell access, Release Tech (no), Task Manager (A&T), + Forums (Moderator), Doc Manager (Editor). Need to set tracker + access individually +3. Add to CVS avail file: + - Translator: Add member to translation files + - Developer: Add member to CVSROOT/avail for all files + diff --git a/doc/developer-guidelines.sgml b/doc/developer-guidelines.sgml index c531fbb..fe21bba 100644 --- a/doc/developer-guidelines.sgml +++ b/doc/developer-guidelines.sgml @@ -637,14 +637,16 @@ update the THANKS.in file.
New plugins - If you would like others to use your plugins and have it included in - the standard distribution, please include patches for the relevant - configuration files, in particular "configure.in". Otherwise submitted - plugins will be included in the contrib directory. - - Plugins in the contrib directory are going to be migrated to the - standard plugins/plugin-scripts directory as time permits and per user - requests. The minimum requirements are: + + If you would like others to use your plugins, please add it to + the official 3rd party plugin repository, + NagiosExchange. + + + We are not accepting requests for inclusion of plugins into + our distribution at the moment, but when we do, these are the minimum + requirements: + @@ -663,75 +665,21 @@ update the THANKS.in file. It should also follow code format guidelines, and use functions from -utils (perl or c or sh) rather than cooking it's own +utils (perl or c or sh) rather than using its own + + + Includes patches to configure.in if required (via the EXTRAS list if + it will only work on some platforms) + + + If possible, please submit a test harness. Documentation on sample + tests coming soon - New plugins should be submitted via - SourceForge's - tracker system for Nagiosplug new plugins - and be announced to the nagiosplug-devel mailing list. - - For new plugins, provide a diff to add to the EXTRAS list (configure.in) - unless you are fairly sure that the plugin will work for all platforms with - no non-standard software added. - - If possible please submit a test harness. Documentation on sample - tests coming soon.
- -
Using Sourceforge -Project Member Access - - - - Member type - CVS Access - Shell Access - Release Tech - Tracker Manager - Task Manager - Forums - Doc Manager - News - Screenshots - Notes - - - - - Translator - Yes - Yes - No - - - - - - - - - - - - - Add developer to CVSROOT/avail for translation files - - - Developer - Yes - Yes - No - - - A&T - Moderator - Editor - - - - - Need to set tracker access individually. Add developer to CVSROOT/avail for all files - - - -
-Add all members to the nagiosplug-team mailing list -
-- cgit v0.10-9-g596f