Changes between Initial Version and Version 1 of org/meetings/2017Amsterdam/Notes/Trac


Ignore:
Timestamp:
Mar 27, 2017, 4:08:26 PM (2 years ago)
Author:
alison
Comment:

added session notes

Legend:

Unmodified
Added
Removed
Modified
  • org/meetings/2017Amsterdam/Notes/Trac

    v1 v1  
     1== Working session to determine whether or not to migrate away from Trac ==
     2
     3We discussed gitlab vs Trac.
     4
     5What are some important Trac features for power users?
     6
     7- Possibility to map Trac tickets to bugwarrior
     8
     9- Possibility to break down tickets into parent issues and sub tickets.
     10
     11What is missing in Trac that is really important?
     12
     13- Code reviews
     14
     15- Continuous integration
     16
     17- It scares potential contributors away
     18
     19Other projects from our community use gitlab successfully:
     20
     21- Micah @ Riseup
     22
     23- The guardian project
     24
     25- F-droid
     26
     27This also means other projects have migrated away from another bug
     28manager to gitlab, in fact there are importers.
     29
     30It is possible to "hard-code" the issue id. This way we can have
     31persistent issue numbers between trac and gitlab.
     32
     33When working on gitlab some aspect of the work flow will have to change.
     34Some ticket fields will have to be mapped to tags. The project flow is
     35more flat on gitlab.
     36
     37There are code reviewer assigned to a Merge Request. Also Merge Requests
     38and Issues are two different things. If a Merge Request has WIP in the
     39title it cannot be merged, this could be a way to have sub issues in a
     40Merge review.
     41
     42It is possible on gitlab to have search and custom reports of issues
     43across different projects.
     44