From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from th.inri.net ([216.126.196.42]) by ur; Mon Dec 19 17:24:08 EST 2016
Received: (qmail 71664 invoked from network); 19 Dec 2016 22:24:06 -0000
Received: from mirv.inri.net (HELO pav1) (167.88.120.88)
  by th.inri.net with SMTP; 19 Dec 2016 22:24:06 -0000
Subject:  bugs.9front.org: update file structure
Date: Mon, 19 Dec 2016 17:23:58 -0500
From: sl@stanleylieber.com
To: 9front@9front.org
Message-ID: <4706ccfef7309d2e1a2579ddb816eb9f@pav1.example.com>
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: proven reduce/map persistence interface 

I am unhappy with the way user input is currently mangled.  I am
working on a slight overhaul of the way submitting a bug works, and
the way files are stored once a bug is submitted.

Proposed:

	- Save the entire original message in bugname/mbox/filename. filename
		is an mdir file, which is suitable for opening with either
		upas or nupas (upas just treats it as an mbox that contains
		one message).
	- bugs/close will then reply to the saved message, cc: bugs@9front.org
		and the original submitter. All relevant links to the bug
		(/n/bugs/closed/bugname, etc.) will be automatically added
		to the message.

Pros:
	- This will preserve attachments and make replying much easier.

Cons:
	- No mechanism has yet been invented for closing a bug via e-mail.
		However, this is a step towards that goal.

sl