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:21:55 EST 2018 Received: from k.inri ([107.161.31.183]) by 5ess; Thu Feb 8 22:21:53 EST 2018 Message-ID: <797918FABB22A9492E3134BD9D4E04BA@5ess.inri.net> Date: Thu, 8 Feb 2018 22:21:49 -0500 From: sl@stanleylieber.com To: 9front@9front.org Subject: Re: [9front] PROPOSAL: New 9front Bug Tracker In-Reply-To: 20180208235654.GA41727@wopr MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: content-driven realtime grid > 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. One of the reasons I am interested in rolling a custom bug tracker is because I like the idea of using the 9front system to maintain and host the 9front system. Every outside facility is something we don't control and will probably have to replace later (in this case, if we ever get rid of python, which everyone says we want to do). In my opinion, alien software (as in, not Plan 9 native) should always be considered a last resort. Otherwise, why are we doing any of this at all? That said, we could just use this. sl