|
|
|
[[_TOC_]]
|
|
|
|
|
|
|
|
### Related issues
|
|
|
|
### Related
|
|
|
|
|
|
|
|
* #817
|
|
|
|
|
|
|
|
### Motivation
|
|
|
|
|
|
|
|
Todo: clarify this.
|
|
|
|
This wiki page has mostly technical information, and some overview of the pros/cons of Github/Gitlab.
|
|
|
|
|
|
|
|
* 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
|
|
|
|
* Requires to signup for two user accounts (JIRA/civicrm.org and Github)
|
|
|
|
* It's not user-friendly, even to most developers
|
|
|
|
* It's a pain to host & maintain
|
|
|
|
* It's proprietary and also requires managing plugins with their own licenses
|
|
|
|
* It's slow.
|
|
|
|
Please see:
|
|
|
|
|
|
|
|
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.
|
|
|
|
* [Gitlab Roadmap](gitlab-roadmap)
|
|
|
|
* #817
|
|
|
|
|
|
|
|
### JIRA 'CRM' migration to Gitlab (or Github)
|
|
|
|
|
| ... | ... | @@ -34,15 +25,7 @@ On the topic of migrating the main 'CRM' project to Gitlab vs Github: |
|
|
|
|
|
|
|
### Roadmap and process
|
|
|
|
|
|
|
|
General draft tentative unofficial roadmap brainstorm for JIRA deprecation:
|
|
|
|
|
|
|
|
* September-December 2017: Brainstorm/experiment period, get feedback from active contributors.
|
|
|
|
* By February 2018: Formal position of the Core Team
|
|
|
|
* 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
|
|
|
|
|
|
|
|
Some of the above steps could be done earlier, if there is consensus.
|
|
|
|
See: #817
|
|
|
|
|
|
|
|
### Tech notes
|
|
|
|
|
| ... | ... | |
