Skip to content

Changes

Page history
Update gitlab roadmap authored by bgm's avatar bgm
Hide whitespace changes
Inline Side-by-side
gitlab-roadmap.md
View page @ 3010b387
......@@ -4,7 +4,7 @@
Early experiments using Gitlab ([lab.civicrm.org](https://lab.civicrm.org)) started around March 2017, as a tool to help with managing CiviCamps and the civicrm.org website, followed by the infrastructure issues, marketing, etc. The initial intention was to provide a collaboration space for areas that didn't fit in JIRA/Confluence. People often defaulted to using direct emails with many CCs/forwards, since it was hard to know who was responsible for what.
We let Gitlab grow organically as a sort of beta service, collecting feedback. In the beginning, replacing JIRA was not on the table initially, but Gitlab seemed to be a good candidate for replacing a lot of the left-over content of Confluence (after [the migration of dev/admin documentation to mkdocs](https://wiki.civicrm.org/confluence/display/CRMDOC/Content+migration+from+wiki+to+Developer+Guide)) and tracking non-core issues.
We let Gitlab grow organically as a sort of beta service, collecting feedback. In the beginning, replacing JIRA was not on the table. Gitlab seemed to be a good candidate for replacing a lot of the left-over content of Confluence (after [the migration of dev/admin documentation to mkdocs](https://wiki.civicrm.org/confluence/display/CRMDOC/Content+migration+from+wiki+to+Developer+Guide)) and tracking non-core issues.
We are now at a point (November 2017) where we have to evaluate what to do with JIRA, whether Gitlab can help with the extensions ecosystem, and how Gitlab can help the larger CiviCRM community.
......