Return-Path: <rjbarbal@MIT.EDU>
Received: from central-city-carrier-station.mit.edu by po11.mit.edu (8.9.2/4.7) id XAA12168; Tue, 8 Jan 2002 23:20:20 -0500 (EST)
Received: from manawatu-mail-centre.mit.edu (MANAWATU-MAIL-CENTRE.MIT.EDU [18.7.21.85])
	by central-city-carrier-station.mit.edu (8.9.2/8.9.2) with ESMTP id XAA25196;
	Tue, 8 Jan 2002 23:17:32 -0500 (EST)
Received: from starbase.mit.edu (STARBASE.MIT.EDU [18.101.0.114])
	by manawatu-mail-centre.mit.edu (8.9.2/8.9.2) with ESMTP id XAA16502;
	Tue, 8 Jan 2002 23:17:34 -0500 (EST)
Received: (from rjbarbal@localhost) by starbase.mit.edu (8.9.3)
	id XAA07656; Tue, 8 Jan 2002 23:17:35 -0500 (EST)
Message-Id: <200201090417.XAA07656@starbase.mit.edu>
To: sipb-staff@MIT.EDU
Cc: sipb-private@MIT.EDU
Subject: Fixing sipb-private
Date: Tue, 08 Jan 2002 23:17:35 -0500
From: "Richard J. Barbalace" <rjbarbal@MIT.EDU>

You will notice that this email has a To line containing sipb-staff
and a Cc line containing sipb-private.  This should not be necessary
since sipb-private should be kept up to date with sipb-staff, which
of course does not happen.

Following up on the SIPB_Staff_Archive[7630] discussion, I propose:
1) sipb-private be brought up to date with sipb-staff.
2) sipb-staff contain only:
   sipb-private
   sipb-staff-mtg@charon.LOCAL
3) new members be added to sipb-private, not sipb-staff.
4) sipb-private be more widely used for discussions that are
   not wished to be archived.  An example of that might be
   discussion about nominating a prospective.

Unless someone has big objections to this, I'll make this a motion
at the next meeting.

+ Richard
