jira-to-gitlab-migration.md

-Random thoughts on migrating the main 'CRM' project to Gitlab vs Github:
+[[_TOC_]]
+
+### Motivation
+
+Todo: clarify this.
+
+* We only use a fraction of the features of JIRA (i.e. we are perhaps not the target group for which JIRA is developed)
+* JIRA tends to be overly complicated for what we do with it
+* It's not user-friendly
+* It's a pain to host & maintain
+* It's proprietary and also requires managing plugins with their own licenses
+* It's slow.
+
+As a result, we tend to use JIRA for the issue title and brief description, with all the discussion happening on the Github pull-requests.
+
+### JIRA 'CRM' migration to Gitlab (or Github)
+
+On the topic of migrating the main 'CRM' project to Gitlab vs Github:
 
 * Github will not allow us to import the comment history while keeping the author intact. i.e. all comments will be imported as the same user.
 * By controlling registration (on civicrm.org), we can keep Community Profiles and better engage with the community/developers.
@@ -8,12 +25,16 @@ Random thoughts on migrating the main 'CRM' project to Gitlab vs Github:
   * Vendor-neutral dev spaces (shops could still promote their consulting/support services, like they do on drupal.org, but it would not be in the canonical URL of the git repo).
   * Gitlab templates could potentially run civix automatically? hook into gitlab's c-i to run tests? (instead of Jenkins)
 
+### Roadmap
+
 General draft tentative unofficial roadmap brainstorm for JIRA deprecation:
 
 * By March 2018: Move Extensions (EXT) to Gitlab
 * By March 2018: Move CiviVolunteer to either Gitlab or Github
 * By July 2018: Move CRM to Gitlab
 
+### Tech notes
+
 General notes for migrating non-CRM JIRA projects (ex: INFRA):
 
 * Script used: https://gist.github.com/florisb/1266d3584dbfdbd2a8a55d31e2518edd