On 20/04/12 18:26, Max Thayer wrote:
> Luke, maybe I don't understand something about Trac, but some of the...
> issues raised by you or those you quoted seem easily fixed. Consider:
> "- there isn't a notion of "component", so there's no way to ask
> Why not tag all relevant issues "contrib.auth"?
They are very different things in reality.
> "- we can't put customized flags on tickets (easy, ui/ux) -- there are
> Could you explain this more? "customized flag" sounds exactly like a tag.
With tags, it is up to people to decide which kind of tagging they think
Without this, tagging quickly becomes next to useless for querying.
Also, tags are unstructured, so if you use it for more than one purpose,
Also, the tracking on these things is basically non-existant in GitHub.
It also seems that only managers can set tags in GitHub Issues, which
> "- it's hard to navigate when there are more than 200 open ticketsFor one thing, the Trac UI just makes much better use of screen space.
> There are easily that many open tickets on Trac (a quick look seems to
There is no comparison between these two in terms of easily finding the
information you want:
Trac also has pretty nice reporting abilities, and report building
No-one thinks Trac is ideal, it's just much better than GitHub Issues
Luke Plant || http://lukeplant.me.uk/
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.