From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from 5ess.inri.net ([107.161.31.183]) by ewsd; Thu Feb  8 22:31:33 EST 2018
Received: from k.inri ([107.161.31.183]) by 5ess; Thu Feb  8 22:31:32 EST 2018
Message-ID: <3D11D54F48BA3C150017F155D1B4259D@5ess.inri.net>
Date: Thu, 8 Feb 2018 22:31:27 -0500
From: sl@stanleylieber.com
To: 9front@9front.org
Subject: Re: [9front] PROPOSAL: New 9front Bug Tracker
In-Reply-To: 797918FABB22A9492E3134BD9D4E04BA@5ess.inri.net
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
List-ID: <9front.9front.org>
List-Help: <http://lists.9front.org>
X-Glyph: ➈
X-Bullshit: stable reduce/map XMPP interface realtime-java cache element control 

The draft proposal has been updated:

	http://9front.org/bugtracker

Diff follows:

src/bugtracker:9,30 - /n/ewsd/usr/sl/www/werc/sites/9front.org/bugtracker:9,39
  		the entirety of the discussion thread.
  
  	2.  A bug's status is defined by its location under one of the
- 	following directories:
+ 	following top directories:
  
- 		a.  open/
+ 		a.  new/
  
  		b.  closed/
  
  		c.  [tba]
  
- 	3.  A bug's priority is defined by [tba].
+ 	3.  A bug's priority is defined by its location under one of
+ 	the top directories listed in Definitions-2.
  
  	4.  A bug's assignment (the developer to which the bug is
  	assigned) is defined by [tba].
  
+ 	5.  The subsystem to which a bug applies is defined by the
+ 	contents of a file subsystem under the bug's top directory.
+ 	Valid subsystems include:
+ 
+ 		a.  [tba]
+ 
  Features
  
- 	1.  Create and close bugs by sending an e-mail.
+ 	1.  Create and close bugs by sending an e-mail.  In both cases
+ 	the e-mail is forwarded to the regular 9front@9front.org
+ 	mailing list.
  
  	2.  View bugs, their status, priority, and assignment via
  	command line tool, to be included with the default 9front