9front - general discussion about 9front
 help / color / mirror / Atom feed
From: Kurt H Maier <khm@sciops.net>
To: 9front@9front.org
Subject: Re: [9front] PROPOSAL: New 9front Bug Tracker
Date: Thu, 8 Feb 2018 15:56:54 -0800	[thread overview]
Message-ID: <20180208235654.GA41727@wopr> (raw)
In-Reply-To: <0181CC86F20462F489E422A79155DEE5@5ess.inri.net>

On Wed, Feb 07, 2018 at 08:34:14PM -0500, sl@stanleylieber.com wrote:
> The existing bug tracker sucks.

To complicate matters, I have recently discovered an existing bug
tracker, written in python, which operates as a mercurial extension,
and stores bugs as maildirs inside the source tree.

It's got a weird license but maybe an email to the author could fix
that.  The license is almost, but not quite, BSD.  

http://www.mrzv.org/software/artemis/

Maybe something from which to draw inspiration.

khm


  parent reply	other threads:[~2018-02-08 23:56 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-08  1:34 sl
2018-02-08  2:08 ` [9front] " Lyndon Nerenberg
2018-02-08  8:37 ` Julius Schmidt
2018-02-08  9:07   ` Kurt H Maier
2018-02-08 16:54     ` Ethan Grammatikidis
2018-02-08 23:23       ` Steve Simon
2018-02-08 23:56 ` Kurt H Maier [this message]
2018-02-08  2:55 sl
2018-02-09  3:01 sl
2018-02-09  3:15 sl
2018-02-09  3:21 sl
2018-02-09  3:31 sl
2018-02-09  5:11 ` Eli Cohen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180208235654.GA41727@wopr \
    --to=khm@sciops.net \
    --cc=9front@9front.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).