head	1.1;
access;
symbols;
locks
	mohlerb:1.1; strict;
comment	@# @;


1.1
date	99.05.30.19.31.03;	author mohlerb;	state Exp;
branches;
next	;


desc
@@


1.1
log
@Initial revision
@
text
@The following guidelines will govern the collaborative development
of syssumm ("system summaries").

$Header$

$Revision$

$Log$

This document is the first draft of these guidelines and is therefore
a proposal for the collaborative development process.  Your comments
are welcome.  Send them to Bruce Mohler (bruce.w.mohler@@cpmx.saic.com).

Software License

1.	This software (ie., syssumm) will be distributed under the
	GNU GPL.  At the top of each source and documentation file 
	you'll find:

	"This program is free software; you can redistribute it and/or
	modify it under the terms of the GNU General Public License
	as published by the Free Software Foundation; either version 
	2 of the License, or (at your option) any later version.

	"This program is distributed in the hope that it will be 
	useful, but WITHOUT ANY WARRANTY; without even the implied
	warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR
	PURPOSE.  See the GNU General Public License for more details."

2.	The first version of the source will be distributed under the
	GNU GPL (as described above), copyright SAIC.

3.	A copy of the GNU GPL will be distributed with the source
	code (both while under development and later if we push
	syssumm to the point of being useful).

Syssumm Source Archive

4.	The current maintainer of the syssumm source archive is 
	Bruce Mohler.  It's possible that this might change in the
	future.

5.	All changes to the source will be sent to Bruce Mohler in 
	patch format (unless it's an entirely new file).  He will 
	merge them into the source tree.  The source will then be 
	checked in using RCS.

	Please make sure to send your patches as a "context diff"
	so that the surrounding lines are included in the patch
	as well as the actual lines that have been changed.  This
	makes it much easier to merge into the source since the
	line numbers change over time.  This does suggest that I'm
	merging patches in my hand too.

6.	As members of the syssumm development team make contributions
	that specific set of changes as they are checked in via RCS
	are associated with that author.  Part of the comments as 
	the changes are checked in will include:

	"Copyright (C) 19__ <name of author>"

	This will protect your investment (at least in theory).

7.	Periodically, (until such time as we can get a CVS archive)
	the source tree will be redistributed to the syssumm 
	development team in shar format via the mailing list.  
	Without knowing how many changes will occur, let's assume 
	that this will be monthly.

	At the present time, developers will submit patches each
	week until *your* "close of business" on Thursday.  I'll
	merge the patches as I get them, completing the work Friday
	morning with a new release each Friday (if there have been
	patches).

Syssumm Development Team

8.	As you get the source code and install it and get it working,
	you may decide that you wish to contribute to the development
	of syssumm.  If so, please contact Bruce Mohler and let me 
	what area(s) you wish to *actively* work on (e.g., Solaris 
	2.6, Oracle, AIX, etc.).  I will maintain a list of people 
	working on various areas and will distribute that list to 
	the syssumm development team through the mailing list every 
	couple of weeks or so so that people working in the same area 
	can form smaller teams (if you so choose).

9.	Conditions in our lives change and people can "opt out" of
	participating in the development of syssumm at any time 
	with no guilt.  Any contributions that you've made to the
	source code stay in place.

Note that the original concept of syssumm was developed by Bruce Mohler
while working for SAIC.  SAIC has graciously donated time for me to do
the original development of this software.  SAIC has also graciously
given its permission to distribute the source code to the system 
development team.

@
