From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Re: musl new-year's infrastructure resolutions
Date: Mon, 2 Jan 2017 13:36:52 -0500 [thread overview]
Message-ID: <20170102183652.GD1555@brightrain.aerifal.cx> (raw)
In-Reply-To: <20170102182700.GB16144@wopr>
On Mon, Jan 02, 2017 at 10:27:00AM -0800, Kurt H Maier wrote:
> On Mon, Jan 02, 2017 at 06:39:37AM +0000, Khem Raj wrote:
> > Have you considered github
>
> The biggest problem with using github for this is that users will then
> be required to have github accounts to file issues. Good issue trackers
> do not put this burden on reporters.
While I agree it's a burden to require that, it's also a convenience
to be able to use an existing identity (especially if you're given a
choice of which identity provider to use, which is not the case with
github of course) rather than having to create a new account to report
bugs. It would be nice if we could allow that but I don't see the
capaibility in any existing issue trackers.
Rich
next prev parent reply other threads:[~2017-01-02 18:36 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-31 23:37 Rich Felker
2017-01-01 22:37 ` A. Wilcox
2017-01-02 2:31 ` Rich Felker
2017-01-02 2:33 ` Rich Felker
2017-01-02 5:32 ` A. Wilcox
2017-01-02 5:40 ` Rich Felker
2017-01-02 6:39 ` Khem Raj
2017-01-02 16:58 ` Rich Felker
2017-01-02 18:11 ` Alexander Monakov
2017-01-02 18:23 ` Rich Felker
2017-01-02 18:15 ` Solar Designer
2017-01-02 18:25 ` Rich Felker
2017-01-02 18:27 ` Kurt H Maier
2017-01-02 18:36 ` Rich Felker [this message]
2017-01-02 18:52 ` Kurt H Maier
2017-01-02 19:16 ` Rich Felker
2017-01-02 20:06 ` Kurt H Maier
2017-01-02 22:59 ` A. Wilcox
2017-01-02 23:09 ` Kurt H Maier
2017-01-02 19:10 ` Matias A. Fonzo
2017-01-02 19:18 ` Rich Felker
2017-01-02 19:28 ` Matias A. Fonzo
2017-01-03 1:20 ` Laurent Bercot
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=20170102183652.GD1555@brightrain.aerifal.cx \
--to=dalias@libc.org \
--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).