Trac

Trac! located at https://bugs.devhack.net

general ticketing/todo/tasks system. Despised by many. Used by few

trac seems to elide all emails in tickets, and bugs are accessible publicly to everyone on the internet. please use a non-parseable email if you want to make your email known within a ticket

Why trac?

Trac was one of the first services we spun up, before we even had too many members at the space. The desires for some sort of ticketing system are self evident, so here are the more individual pieces of a ticketing system that were assesed:

• is a product specifically made for bug-tracking, and is separate from other kinds of tooling
  • trac actually doesn't do very good with thus but we just disabled the builtin wiki and called it a day.
• enforced hierarchical organization. having to group tickets under a multi-level "project" / "organization" structure. Unnecessary for generic devhack tasks
• Optional room for growth of structure. Allowing categorizing, milestones, tagging. Those kind ofs things, but not pushed in any way
• Extensibility/scriptability. How much of the culture of the product is providing an "all in one complete working service" vs how much of the culture is attaching on a bunch of various pieces in an ad-hoc manner (this is desirable for a hackerspace, of course)
• automations surrounding it. rss feeds. ease to post to it. APIs.
• LDAP/IPA/SSO support. either builtin or via a plugin.
• looks like it was made in the early 2000s/looks like shit
  • this is m's personal preference
  • extensibility also lends itself to re-stylability
• deployability within a docker environment / ease of deployability

Other tools that were assessed

• bugzilla
• redmine