Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Mon, 2 Jan 2017 14:16:24 -0500
From: Rich Felker <>
Subject: Re: musl new-year's infrastructure resolutions

On Mon, Jan 02, 2017 at 10:52:38AM -0800, Kurt H Maier wrote:
> On Mon, Jan 02, 2017 at 01:36:52PM -0500, Rich Felker wrote:
> > 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.
> JIRA and Mantis support OAuth, Redmine and RT support OpenID, Redmine
> and JIRA support Shibboleth federation, and RT can be used by reporters
> entirely without authentication (via email). Bugzilla can be made to
> support OpenID.  None of these systems are particularly lightweight.

JIRA is everything I dislike about github's UI, but far worse, at
least from my experience using it on Atlassian/bitbucket. So it's
pretty much out of the question.

Mantis doesn't seem so bad as a user but I have no idea how bad it is
under the hood. Redmine looks kinda nice and Alpine uses it.

Re: OAuth and OpenID, I get the impression that OpenID is dead, so
support for it probably isn't useful. At least Google and likely other
providers have dropped it, right?


Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.