RFC: Enable contributitions by separating data from backend code
Request for comments
Need
Currently, both data and backend code for Zendesk (and other areas) maintained by Support Operations is in one place. This makes contributions tricky when not coming from Support Operations, as there is a high risk of damage to the system itself.
We need to enable contributions from those outside of Support Operations on the data itself.
Approach
Move the data to new repos that can be maintained by Support (and others if desired). Initially speaking, Support Managers, but the maintainers could then decide process/workflows/etc. to determine how changes and the like to said repos would work.
Those repos would become submodules on the backend code projects.
Proof of Concept examples
- ZD Global Automations
- data is at https://gitlab.com/gitlab-com/support/zendesk-global/automations
- edits there are synced to the backend code via a git submodule
- ZD Global Triggers
- data is at https://gitlab.com/gitlab-com/support/zendesk-global/triggers
- edits there are synced to the backend code via a git submodule
NOTE These are proof of concept projects, they are not "live".
Benefit
This enables others outside of Support Operations to safely contribute to the data they care about without causing potential harm to the backend side of things (and the systems it syncs to).
This follows our Everyone Can Contribute mentality and enables us to maintain a secure and efficiently running system.
Competition / Alternatives
- Keep doing what we are doing now
- Figure out something else I guess?
CC @dtragjasi for Support Operations triage of this issue