Assembla ticket creation requires administrative privileges?

Vegard Øye vegard_oye at hotmail.com
Mon Jul 5 17:26:55 CEST 2010


On 2010-06-28 13:42, Štěpán Němec wrote:

> Vegard Øye <vegard_oye at hotmail.com> writes:
>
>> My guess is that the Git+Trac integration is still a bit betaish.
>> I know that non-members could create tickets when we used
>> SVN+Trac,[1] and I'm not aware of any settings for changing that.
>
> Dunno. One would say Trac is independent from Git, i.e. it should
> work just the same no matter whether you use Git or SVN?

Well, the server is different. In the SVN days, the tracker was at
http://my-trac.assembla.com/vimpulse/; now it is at
http://trac-git.assembla.com/vimpulse/. Maybe the latter isn't
configured properly.

>> But it's not a huge matter; the bug tracker is mostly a "discussion
>> tracker" these days. If you want to contribute code, the preferred
>> approach is to submit a patch to the mailing list which can be
>> committed with "git am". That way, you also get credit in the
>> version history.
>
> Cool, this paradigm switch is great news ;-) But then we should
> really adjust the bug reporting information we give to discourage
> use of the bug tracker, at least until the issues are sorted out.

Yes. For starters, I think we should remove references to the tracker
from EmacsWiki, as well as from Vimpulse's headers.

> Also, IMO the mailing list is much better for discussion as well --
> you get every new message without need to periodically check the
> tracker (I imagine there is some mailing notification integrated,
> but why, when you could just use e-mail in the first place. And I
> find writing mails much more convenient than using a web interface
> (I don't use webmail BTW, despite my address suggesting otherwise)).

I agree. In particular, the Gmane interface makes it easier to
retrieve old threads, rendering the tracker even more obsolete.

For documentation purposes, maybe we should use Assembla's wiki
instead of Trac's. I'm not sure. Benefits of the Trac wiki is that it
is exportable, has more fine-grained formatting, and doesn't use the
dreaded Markdown syntax.

-- 
Vegard



More information about the implementations-list mailing list