3 files changed, 0 insertions, 85 deletions
diff --git a/doc/LEAVERS b/doc/LEAVERS
deleted file mode 100644
index 9764fda8..00000000
--- a/doc/LEAVERS
+++ /dev/null
@@ -1,14 +0,0 @@
-LEAVERS
-
-These are the steps for someone leaving the team.
-
-Leaver has to:
-  - Update all current tracker items
-
-Administration tasks:
-  - Reassign leaver's tracker items to project lead
-  - Remove from Sourceforge's list of developers. This will include CVS access. Do not
-    need to remove from CVS avail file
-  - If applicable, remove from mailing list administrators
-  - Keep on nagiosplug-team mailing list, unless specifically requested to be removed
-
diff --git a/doc/NEW_STARTERS b/doc/NEW_STARTERS
deleted file mode 100644
index 23f1a4aa..00000000
--- a/doc/NEW_STARTERS
+++ /dev/null
@@ -1,24 +0,0 @@
-NEW STARTERS
-
-These are the steps for adding someone to the team.
-
-Need to know:
-  - Name
-  - Primary email for nagiosplug-team mailings
-  - Sourceforge id
-  - Type of member (translator, developer, release manager, project administrator)
-
-1. Add member to nagiosplug-team mailing list (https://lists.sourceforge.net/lists/admin/nagiosplug-team)
-   and to the nagiosplug-checkins mailing list (https://lists.sourceforge.net/lists/admin/nagiosplug-checkins,
-   add sourceforge email address via Privacy Options->Sender filters)
-2. Add Sourceforge access:
-  - Translator: CVS access, Shell access, Release Tech (no)
-  - Developer: Project role: Developer, CVS access, Shell access, Release Tech (no), Task Manager (A&T),
-               Forums (Moderator), Doc Manager (Editor)
-               Update Developer Permissions.
-	       For each tracker, set to Technician (need to add all trackers first, then change to 
-		technician for each one)
-3. Add to CVS avail file:
-  - Translator: Add member to translation files
-  - Developer: Add member to CVSROOT/avail for all files
-4. Send email to nagiosplug-team introducing new member
diff --git a/doc/RELEASING b/doc/RELEASING
deleted file mode 100644
index c5d81951..00000000
--- a/doc/RELEASING
+++ /dev/null
@@ -1,47 +0,0 @@
-NOTES ON RELEASING NEW VERSION OF NAGIOSPLUG
-
-svn update in main area
-. tools/devmode, if feeling adventurous
-check compilation, check tinderbox screens
-
-Update BUGS, NEWS file
-Update AUTHORS if new members
-Update configure.in and package.def with version
-Run svn2cl (get from http://ch.tudelft.nl/~arthur/svn2cl):
-svn2cl.sh --break-before-msg --reparagraph -i http://nagiosplug.svn.sourceforge.net/svnroot/nagiosplug/nagiosplug/trunk
-commit BUGS NEWS configure.in package.def ChangeLog
-
-svn copy http://nagiosplug.svn.sourceforge.net/svnroot/nagiosplug/nagiosplug/trunk 
-http://nagiosplug.svn.sourceforge.net/svnroot/nagiosplug/nagiosplug/tags/release-1.4.10
-
-checkout new version:
-cd /tmp
-rm -fr nagiosplug
-svn export http://nagiosplug.svn.sourceforge.net/svnroot/nagiosplug/nagiosplug/tags/release-1.4.10 nagiosplug
-cd nagiosplug
-tools/setup
-./configure
-make dist
-
-sftp upload.sf.net
-cd uploads
-put file
-
-SF -> Submit News about release. Make sure it is called "Nagios Plugins" (with those caps)
-Link to download at http://sourceforge.net/project/showfiles.php?group_id=29880
-Include contents of NEWS for this release
-List all people on team involved. 
-Add acknowledgement to contributors
-Submit. Get URL to news item
-
-SF -> Admin -> File Releases
-Add a release to nagiosplug and create a file release
-Name: 1.4.1 
-Create release
-Step 1: Add release notes pointing to news item
-Step 2: add file
-Step 3: *.tar.gz, Platform Independent, Source .gz
-Step 4: Send notice
-
-Send email to nagiosplug-help, nagios-announce with the news text
-Add a news item to http://nagiosplugins.org