[3401] in BarnOwl Developers
Re: Non-MIT access to barnowl's issue tracker
daemon@ATHENA.MIT.EDU (Nelson Elhage)
Wed May 1 17:21:24 2013
In-Reply-To: <CA+ZNE3NwZQd7_V8Z_PPtGTCqBerw_17p2syuwzrCAJf-86Kdhw@mail.gmail.com>
Date: Wed, 1 May 2013 17:21:21 -0400
From: Nelson Elhage <nelhage@nelhage.com>
To: David Benjamin <davidben@mit.edu>
Cc: Geoffrey Thomas <geofft@ldpreload.com>, Quentin Smith <quentin@mit.edu>,
barnowl-dev@mit.edu
Not that I really consider myself involved in barnowl any more, but I
suspect that moving to github from trac can probably only make you
happier with your life. It'll put everything in one place, and you can
stop maintaining trac, which is basically everyone's least favorite
thing.
- Nelson
On Wed, May 1, 2013 at 5:16 PM, David Benjamin <davidben@mit.edu> wrote:
> I said this on zephyr, but moving to Github Issues doesn't seem insane
> to me. It's been fine enough for my personal projects, and I don't
> like Trac very much. Someone mentioned the TracZephyrPlugin, but that
> shouldn't be too difficult to replicate. This guy looks like it
> provides the API we'd want. (Maybe we could get a prospective to write
> it! Would be generally handy for SIPB.)
>
> http://developer.github.com/v3/repos/hooks/
>
> There is also something to be said for having the pull requests,
> issues, and source viewer live in the same place. (Yes, I know Trac
> has a source viewer too, but who actually uses that?) And I'm all for
> having someone else deal with maintaining the issue tracker for us. I
> recall that Trac install being pretty screwy and occasionally requires
> fiddling when things on scripts update.
>
> On Wed, May 1, 2013 at 4:32 PM, Geoffrey Thomas <geofft@ldpreload.com> wrote:
>> 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
