Received: from localhost by CS.UTK.EDU with SMTP (cf v2.9s-UTK) id EAA14737; Fri, 25 Aug 1995 04:47:33 -0400 X-Resent-To: drums@CS.UTK.EDU ; Fri, 25 Aug 1995 04:47:31 EDT Errors-to: owner-drums@CS.UTK.EDU Received: from domen.uninett.no by CS.UTK.EDU with SMTP (cf v2.9s-UTK) id EAA14730; Fri, 25 Aug 1995 04:47:23 -0400 Received: from dale.uninett.no by domen.uninett.no with SMTP (PP) id <09034-0@domen.uninett.no>; Fri, 25 Aug 1995 10:46:30 +0200 Received: from dale.uninett.no (localhost [127.0.0.1]) by dale.uninett.no (8.6.9/8.6.9) with ESMTP id KAA01435; Fri, 25 Aug 1995 10:46:21 +0200 Message-Id: <199508250846.KAA01435@dale.uninett.no> X-Mailer: exmh version 1.5.3 12/28/94 From: Harald.T.Alvestrand@uninett.no To: Roger Fajman cc: drums@CS.UTK.EDU Subject: Re: Getting back on track In-reply-to: Your message of "Thu, 24 Aug 1995 21:19:35 EDT." <199508250121.VAA16603@CS.UTK.EDU> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Fri, 25 Aug 1995 10:46:20 +0200 Sender: hta@dale.uninett.no Folks, I agree that the procedure Keith proposed is probably so complex that it will be ignored. I suggest another method: - SOMEONE (VOLUNTEER HERE, PLEASE; LINE FORMS ON THE LEFT) takes responsibility for maintaining a chart of issues. This chart MUST be net-accessibe, and updated each day, not each month. Possibly it can be updated by all of us somehow??????? (Webforms?) - Each time someone wants to raise an issue, he mails the list; the maintainer (or the instigator) puts it on the chart. - The list discusses the issue in its usual chaotic fashion; this might lead to a better issue formulation, or possibly to a suggested solution; THESE TWO THINGS MUST BE SEPARATE. Changes that have rough consensus are entered on the chart, both in the "problem" and the "solution" box. - The Chair can rule on any issue that it is Out Of Scope; this is reflected in the chart. Decisions can be appealed (if mailed screaming doesn't help) to the ADs, of course. - Once debate over an issue has died down, any reopening of the issue MUST contain a suggested change in the wording on the chart. This role has in the past been done using "requirements" internet-drafts; I think the number of issues to be discussed here makes that approach difficult; we need a more dynamic mechanism. The chart should be seeded with the Danvers list. Comments? Volunteers? Harald A