Working session to determine whether or not to migrate away from Trac

We discussed gitlab vs Trac.

What are some important Trac features for power users?

  • Possibility to map Trac tickets to bugwarrior
  • Possibility to break down tickets into parent issues and sub tickets.

What is missing in Trac that is really important?

  • Code reviews
  • Continuous integration
  • It scares potential contributors away

Other projects from our community use gitlab successfully:

  • Micah @ Riseup
  • The guardian project
  • F-droid

This also means other projects have migrated away from another bug manager to gitlab, in fact there are importers.

It is possible to "hard-code" the issue id. This way we can have persistent issue numbers between trac and gitlab.

When working on gitlab some aspect of the work flow will have to change. Some ticket fields will have to be mapped to tags. The project flow is more flat on gitlab.

There are code reviewer assigned to a Merge Request. Also Merge Requests and Issues are two different things. If a Merge Request has WIP in the title it cannot be merged, this could be a way to have sub issues in a Merge review.

It is possible on gitlab to have search and custom reports of issues across different projects.

Last modified 2 years ago Last modified on Mar 27, 2017, 4:08:26 PM