[3399] in BarnOwl Developers
Re: Non-MIT access to barnowl's issue tracker
daemon@ATHENA.MIT.EDU (Geoffrey Thomas)
Wed May 1 16:33:00 2013
Date: Wed, 1 May 2013 13:32:54 -0700 (PDT)
From: Geoffrey Thomas <geofft@ldpreload.com>
To: Quentin Smith <quentin@mit.edu>
cc: barnowl-dev@mit.edu
In-Reply-To: <alpine.DEB.2.00.1305011401190.26213@dr-wily.mit.edu>
On Wed, 1 May 2013, Quentin Smith wrote:
> On Wed, 1 May 2013, Geoffrey Thomas wrote:
>
>> I don't know of a terribly good way to enable Trac access to the outside
>> world and avoid the usual spam etc. problems, so since we're already using
>> Github for code hosting and pull requests, I'd like to move all our Trac
>> tickets to Github Issues and deprecate the Trac issue tracker. (Possibly
>> moving the wiki content to Github would also be worthwhile.)
>>
>> Is this sane, insane, etc.?
>
> Why not just use the hybrid cert + password login that other SIPB Tracs use?
Provisioning accounts is annoying. It's hard for me to say "go file a bug"
when it involves some manual approval step. (If it doesn't require manual
approval, then it has the spam problem, even leaving aside the overhead of
registering.)
If we can easily set up Trac with OpenID logins or something, that'd be
fine with me. But, it seems to me that using Github for pull requests is
itself an argument for consolidating issue tracking there -- I can't see a
real advantage in keeping the Trac.
--
Geoffrey Thomas
geofft@mit.edu
