From bab46e817fdd198ddf11f533ef50cad3149f65e8 Mon Sep 17 00:00:00 2001 From: Thomas Guyot-Sionnest Date: Fri, 6 Feb 2009 06:35:03 -0500 Subject: Revert "Moving project administration documents to nagiosplugins.org site" This reverts commit f4a52594818e7c3634a397ac1f86ef87a68bd121. diff --git a/doc/LEAVERS b/doc/LEAVERS new file mode 100644 index 0000000..9764fda --- /dev/null +++ b/doc/LEAVERS @@ -0,0 +1,14 @@ +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 new file mode 100644 index 0000000..23f1a4a --- /dev/null +++ b/doc/NEW_STARTERS @@ -0,0 +1,24 @@ +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 new file mode 100644 index 0000000..c5d8195 --- /dev/null +++ b/doc/RELEASING @@ -0,0 +1,47 @@ +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 -- cgit v0.10-9-g596f