Updated QGISbugtracker (markdown)

QGISbugtracker.md

@@ -134,3 +134,13 @@ AGAINST:
     - (Vincent) Possibly, but not necessarily (hence put this remark here)
 
 - (Vincent) As for the poll, I personally think that the way the question was asked had a strong bias, as it did not consider any alternative, and was not clear on what would happen in case of a yes or no vote. It also seemed premature to ask at that time, when the discussion on the list was still ongoing with a lot of points still unknown and necessitating more study.
+
+- (Jorge Gustavo) 
+Moving issues from Redmine to GitLab makes things more simple for new users. We can have more people submitting, reviewing and fixing bugs. With this “small” change, it became much more easy to explain to new comers the QGIS workflow. It also enables a closer integration between tickets and code.
+
+- (Jorge Gustavo) Move to a completely new infrastructure, like GitLab, is complicated. The wisest path is to move to Github and then move to Gitlab. It will be easier to do such migration in the future, if everything is already in GitHub, but we do not urgently need to change. Let’s do it in smaller steps.
+
+- (Jorge Gustavo) Moving from Redmine does not mean clear the history. The history is there and we can work there for 2.x. But we have the opportunity filter a very good percentage of quit old issues.
+
+
+