From: Szabolcs Nagy <nsz@port70.net>
To: musl@lists.openwall.com
Subject: Re: Time for an issue tracker?
Date: Fri, 7 Sep 2012 18:34:50 +0200 [thread overview]
Message-ID: <20120907163450.GB32384@port70.net> (raw)
In-Reply-To: <87ehmddhxq.fsf@gmail.com>
* Christian Neukirchen <chneukirchen@gmail.com> [2012-09-07 16:30:09 +0200]:
> I'd like to propose the github bug tracker (even if the project is not
> hosted by github right now) mainly because it is rather simple, can be
> controlled by mail, and almost everyone has a github account already.
> Please do not force users to make accounts to report bugs.
>
forcing registration for bug reporting is bad
but that rules out github (and i think all other
options mentioned so far)
i don't see an easy solution
the minimum requirements are:
- search/browse the bug database (through web)
- query a bug by unique id (through permanent url)
- open a bug (by mail)
- comment on a bug (by mail)
- get notifications about a bug (by mail)
- simple administration (change status, mark duplicates)
i think server side email applications are hard to do
because of mime parsing and other smtp difficulties
and they can have huge latency
next prev parent reply other threads:[~2012-09-07 16:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-07 6:35 philomath
2012-09-07 6:41 ` Igmar Palsenberg
2012-09-07 8:22 ` Luca Barbato
2012-09-07 9:10 ` Igmar Palsenberg
2012-09-07 14:30 ` Christian Neukirchen
2012-09-07 14:44 ` Igmar Palsenberg
2012-09-07 14:50 ` Christian Neukirchen
2012-09-07 16:34 ` Szabolcs Nagy [this message]
2012-09-07 16:41 ` Rich Felker
2012-09-07 21:01 ` Kurt H Maier
2012-09-07 13:47 ` Rich Felker
2012-09-07 16:54 ` Isaac Dunham
2012-09-07 18:18 ` Rich Felker
2012-09-10 8:44 ` Igmar Palsenberg
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=20120907163450.GB32384@port70.net \
--to=nsz@port70.net \
--cc=musl@lists.openwall.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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).