[Nagiosplug-checkins] nagiosplug/doc NEW_STARTERS,NONE,1.1 developer-guidelines.sgml,1.25,1.26

[Ton Voon]

Update of /cvsroot/nagiosplug/nagiosplug/doc
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv21061

Modified Files:
	developer-guidelines.sgml 
Added Files:
	NEW_STARTERS 
Log Message:
Updated dev guidelines to link to NagiosExchange. Removed project admin
notes from guidelines into separate file


Index: developer-guidelines.sgml
===================================================================
RCS file: /cvsroot/nagiosplug/nagiosplug/doc/developer-guidelines.sgml,v
retrieving revision 1.25
retrieving revision 1.26
diff -u -d -r1.25 -r1.26
--- developer-guidelines.sgml	21 Jan 2005 00:01:54 -0000	1.25
+++ developer-guidelines.sgml	9 Nov 2005 09:31:58 -0000	1.26
@@ -637,14 +637,16 @@
 	</section>
 
 	<section id="Newplugins"><title>New plugins</title>
-	<para>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.</para>
-	
-	<para>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:</para>
+
+	<para>If you would like others to use your plugins, please add it to
+	the official 3rd party plugin repository, 
+	<ulink url="http://www.nagiosexchange.org">NagiosExchange</ulink>.
+	</para>
+
+	<para>We are not accepting requests for inclusion of plugins into 
+	our distribution at the moment, but when we do, these are the minimum
+	requirements:
+	</para>
 
       <orderedlist>
 	<listitem>
@@ -663,75 +665,21 @@
 	</listitem>
 	<listitem>
 	  <para>It should also follow code format guidelines, and use functions from
-utils (perl or c or sh) rather than cooking it's own</para>
+utils (perl or c or sh) rather than using its own</para>
+	</listitem>
+	<listitem>
+	  <para>Includes patches to configure.in if required (via the EXTRAS list if 
+	  it will only work on some platforms)</para>
+	</listitem>
+	<listitem>
+	  <para>If possible, please submit a test harness. Documentation on sample
+	  tests coming soon</para>
 	</listitem>
       </orderedlist>
 
-	<para>New plugins should be submitted via 
-	<ulink url="http://sourceforge.net/tracker/?group_id=29880&atid=541465">SourceForge's
-	tracker system for Nagiosplug new plugins</ulink> 
-	and be announced to the nagiosplug-devel mailing list.</para>
-	
-	<para>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.</para>
-
-	<para>If possible please submit a test harness. Documentation on sample
-	tests coming soon.</para>
 	</section>
 
 </section>
-
-<section id="UsingSourceforge"><title>Using Sourceforge</title>
-<table id="Projectmemberaccess"><title>Project Member Access</title>
-	<tgroup cols="9">
-		<thead>
-			<row>
-				<entry><para>Member type</para></entry>
-				<entry><para>CVS Access</para></entry>
-				<entry><para>Shell Access</para></entry>
-				<entry><para>Release Tech</para></entry>
-				<entry><para>Tracker Manager</para></entry>
-				<entry><para>Task Manager</para></entry>
-				<entry><para>Forums</para></entry>
-				<entry><para>Doc Manager</para></entry>
-				<entry><para>News</para></entry>
-				<entry><para>Screenshots</para></entry>
-				<entry><para>Notes</para></entry>
-			</row>
-		</thead>
-		<tbody>
-			<row>
-				<entry><para>Translator</para></entry>
-				<entry><para>Yes</para></entry>
-				<entry><para>Yes</para></entry>
-				<entry><para>No</para></entry>
-				<entry><para>-</para></entry>
-				<entry><para>-</para></entry>
-				<entry><para>-</para></entry>
-				<entry><para>-</para></entry>
-				<entry><para>-</para></entry>
-				<entry><para>-</para></entry>
-				<entry><para>Add developer to CVSROOT/avail for translation files</para></entry>
-			</row>
-			<row>
-				<entry><para>Developer</para></entry>
-				<entry><para>Yes</para></entry>
-				<entry><para>Yes</para></entry>
-				<entry><para>No</para></entry>
-				<entry><para>-</para></entry>
-				<entry><para>A&T</para></entry>
-				<entry><para>Moderator</para></entry>
-				<entry><para>Editor</para></entry>
-				<entry><para>-</para></entry>
-				<entry><para>-</para></entry>
-				<entry><para>Need to set tracker access individually. Add developer to CVSROOT/avail for all files</para></entry>
-			</row>
-		</tbody>
-	</tgroup>
-</table>
-<para>Add all members to the nagiosplug-team mailing list</para>
-</section>
 </article>
   
 </book>

--- NEW FILE: NEW_STARTERS ---
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