| ... | ... | @@ -26,14 +26,18 @@ On the topic of 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
|
|
|
|
### 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.
|
|
|
|
|
|
|
|
### Tech notes
|
|
|
|
|
|
|
|
General notes for migrating non-CRM JIRA projects (ex: INFRA):
|
| ... | ... | |
