2020-06-19T19:49:26-04:00

9front Bug Tracker

Definitions

	1.  A bug is a directory whose name briefly describes the bug.

		a.  The bug directory contains a subdirectory mbox
		that contains mdir formatted e-mail files comprising
		the entirety of the discussion thread.

	2.  A bug's status is defined by its location under one of the
	following top directories:

		a.  open/

		b.  closed/

	3.  A bug's assignment (the developer to which the bug is
	assigned) is defined by the contents of a file owner under
	the bug's top directory.  For closed bugs, the owner is set
	to the person who closed the bug.

	4.  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 the sections under which manual
	pages are written, to wit:
	  Section (1) for general publicly accessible commands.
	  Section (2) for library functions, including system calls.
	  Section (3) for kernel devices (accessed via bind(1)).
	  Section (4) for file services (accessed via mount).
	  Section (5) for the Plan 9 file protocol.
	  Section (6) for file formats.
	  Section (7) for databases and database access programs.
	  Section (8) for things related to administering Plan 9.
	  /sys/doc for documentation.


Features

	1.  Create and close bugs by sending an e-mail.

		a.  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
	system.

		a.  Print a command to open an individual bug's e-mail
		thread in a dedicated nedmail(1).

		b.  Print a command to close an individual bug (by
		replying to the last mail in that bug's e-mail thread).

	3.  View bugs on the web.

	4.  View an individual bug's e-mail thread on the web.