Ticket #3746 (closed defect: wontfix)

Opened 4 years ago

Last modified 4 years ago

migrate from trac to github

Reported by: sorin Owned by:
Priority: major Milestone:
Component: adm Version:
Keywords: Cc:
Blocked By: Blocking:
Branch state: no branch Votes for changeset:


I think that it would in MC interest as a project to have the issue tracker hosted on GitHub? and I am willing to help with the migration if that's ok.

Change History

comment:1 Changed 4 years ago by andrew_b

  • Status changed from new to closed
  • Resolution set to wontfix
  • Version master deleted
  • Component changed from mc-core to adm
  • Milestone Future Releases deleted

No. Github tracker sucks.

Last edited 4 years ago by andrew_b (previous) (diff)

comment:2 Changed 4 years ago by zaytsev

Longer version:

GitHub tracker is slowly becoming less shit than it used to be, i.e. they have added "milestones" not so long ago, but everything else you are supposed to emulate via labels (report type, priority, affected version, component), and to make it worse, they don't allow to group the labels (also sometimes called custom fields), so for anything more than 1-2 dimensions this is simply not practicable. Now, to make things worse, cross-referencing of issues is supported, but you can't see all references in a sidebar or something like that and have to read the entire thread (!!!11) to see which other tickets were referenced and at which point. All of that makes it unusable for larger projects.

I think that a possibility to move to a more decent supported & hosted system like YouTrack or JIRA (if JetBrains and/or Atlassian would want to sponsor the project) can be discussed, but GitHub is just too much of a pain, and I don't see the deal-breaking downsides of Trac, although, very clearly that's not the best possible system to use.

There have been some occasional whining on the lists that one needs to register on the Trac, but everybody has already got a GitHub account, and that a different issue tracking system cuts off valuable contributors, but so far the average quality of reports & patches from GitHub have been so low, that I'm unconvinced that it makes any sense to consider this argument in our situation.

Note: See TracTickets for help on using tickets.