Integrations group DRIs
Summary
In this issue we worked to shift responsibilities as DRIs of integrations to individual product teams within the domain areas across GitLab, where applicable.
The aim was to give groups full visibility and ownership in serving customers in their domains, based on group's comprehensive strategy. And also to make Integration category more sustainable. We want more integrations to be added over time, and sharing the ownership of these with other groups makes this possible and scalable.
Group Import and Integrate keeps ownership of the foundations of integrations and the Integration development guidelines. We keep offering guidance on integrations best practices to anyone that contribute.
The list below clarifies the current (29.04.2024) ownership of each integration.
Security related integrations, owned by group Anti-Abuse:
CI/CD integrations, owned by group Pipeline Execution:
- Bamboo CI
- Drone CI
- GitHub
- Jenkins
- JetBrains TeamCity CI
- Diffblue Cover
Integrations owned by group Project Management:
Integrations owned by group Source Code:
Integrations owned by group Incubation:
Elasticsearch integration is owned by group Global Search.
Datadog integration is owned by group Runner.
Gitpod integration is owned by group IDE.
Harbor integration is owned by group Container Registry.
Packagist is owned by group Package Registry.
Visual Studio Code extension is owned by group Editor Extensions.
External issue trackers, ownership negotiated with group Project Management, currently maintained by group Import and Integrate:
- Asana
- Bugzilla
- ClickUp
- Custom issue tracker
- EWM - IBM Enginnering Workflow Management
- Jira issue integration
- GitLab for Jira Cloud app
- Pivotal Tracker
- Redmine
- YouTrack
"Notification" integrations, maintained by group Import and Integrate:
- Slack Notifications (deprecated)
- Slack slash commands
- GitLab for Slack app
- Discord
- Gooogle chat
- Irker
- Mattermost notifications
- Mattermost slash commands
- Microsoft Teams
- Pumble
- Unify Circuit
- Webex Teams
- Telegram
Other integrations, currently maintained by group Import and Integrate:
- Trello PowerUp - ownership negotiated with group Project Management
- Pipeline status emails - ownership negotiated with stage Verify
- Emails on push
- Gmail Actions Buttons
- Mock CI
- Squash TM - ownership negotiated with group Product Planning
Context
We are working to shift responsibilities as DRIs of integrations to individual product teams within the domain areas across GitLab. This will empower product teams to own the comprehensive strategy in their domain, and allow us to best scale to support the needs of our customers.
There's a table listing integrations and their DRIs that needs clarification and update.
Once updated, the metadata of the docs of each integration can be updated as well, if needed.
What's expected from the DRI product group?
Product groups working within various domain areas across GitLab are in general expected to own comprehensive strategies in their domains. When it comes to integrations, it means to:
- Decide if new integrations contributed by Community should be added to GitLab codebase, according to the larger strategy for the respective domain.
- Decide if already existing integrations should stay in GL codebase, according to the larger strategy for the respective domain.
- If any integration should be removed, follow the process of deprecating and removing.
- Maintain the documentation - if there are any additions or changes to integrations.
- Re-assign integration related issues to the group, which doesn't mean working on them directly, but rather triaging and deciding if they should get prioritised or not. The DRI group becomes responsible for remediating bugs and security vulnerabilities within target SLOs, addressing infradev issues, responding to urgent requests, responding to Requests for Help, and iterating on an integration.
- Some integrations could be announced Community supported for improvements and any additional features - that's up to the product groups.
groupimport and integrate
What responsibilities will stay withShifting ownership of individual integrations to other groups is a way to make this category sustainable. We want more integrations to be added over time, and sharing the ownership of these with other groups makes this possible and scalable.
However, groupimport and integrate will keep ownership or oversight of the foundations of integrations. We will keep maintaining and making progress on foundational improvements (example: !140350 (merged), and documentation (example: !139864 (merged)). We will keep maintaining Integration development guidelines and offering guidance to others on best practices (example: #426147 (comment 1722423511)).
How can I help?
I have copied the original table below (added question marks where I was unsure of the information given), removed some integrations that have no code and no docs in GL codebase. I went through all the integrations, checked the docs metadata and in some cases did additional investigation. There's a few integrations that don't have user docs, and I need to figure out why that is the case. I've added additional columns to allow for discussion. I've added your handles where I would like to ask for your review.
- Please review the rows with your handle and give a YES/NO in the
Correct group DRI
column, if all looks fine. Otherwise please leave a comment in theComment
column or an issue comment. - You can update other columns if needed, but please cross out incorrect information, rather than removing them, and add correct info next to it.
Thank you!!
Table
Integration | Category | Owner (Group) | Author (Contributor/Maintainer) | PM | Correct group DRI | Docs metadata | Comments | |
---|---|---|---|---|---|---|---|---|
Spam Protection |
|
GitLab | ~~@sam.white~~ @jrandazzo | @jrandazzo |
point to groupanti-abuse |
|||
Security |
|
Arkose Protect | ~~@sam.white~~ @jrandazzo | @jrandazzo |
point to groupanti-abuse |
|||
Project Management | Plan:Project Management ? | GitLab |
point to groupimport and integrate |
change docs metadata? | ||||
Code Intelligence | Create:Source Code | N/A |
there's no user docs, only API, figure this out |
|||||
CI/CD |
Verify:Pipeline Execution grouppipeline execution |
GitLab | Yes |
point to groupimport and integrate |
change the docs metadata: !147432 (merged) |
|||
Project Management | Plan:Project Management ? | GitLab |
point to groupimport and integrate |
change docs metadata? | ||||
Buildkite | CI/CD | Verify:Pipeline Execution ? | N/A ? | No |
no user docs, just API docs |
add user docs? is it used? figure out [Rutvik] - It is hard to tell from the docs but it looks like it would show BK pipeline results during code review - so perhaps groupcode review |
||
Chat | Manage:Integrations | N/A ? |
no user docs, just API docs |
add user docs? is it used? figure out | ||||
Wiki |
|
GitLab |
no user docs, just API docs |
add user docs? is it used? figure out | ||||
Project Management | Plan:Project Management ? | GitLab |
point to groupimport and integrate |
change metadata? | ||||
Monitoring |
grouprunner, see comment |
DataDog |
point to groupimport and integrate |
@DarrenEastman is the DRI: #438682 (comment 1881506449) Change the docs metadata: !150988 (merged) |
||||
Chat | Manage:Integrations | GitLab | ||||||
Drone CI | Chat | GitLab | No |
no user docs, API only |
[Rutvik] - grouppipeline execution #438682 (comment 1830805350) |
|||
Manage:Integrations | GitLab | |||||||
Data Warehouse & Search | Data Stores:Global Search | GitLab |
point to groupglobal search |
|||||
Wiki | Plan:Knowledge | GitLab |
no user docs, just API docs |
add user docs? is it used? figure out | ||||
Chat | Manage:Integrations | GitLab | ||||||
SCM ?? looks like CI/CD |
|
GitLab | Yes |
change the docs metadata: !147432 (merged) |
There are also these related docs under grouppipeline execution |
|||
IDE | GitLab |
point to groupide |
||||||
Chat | Manage:Integrations | GitLab | ||||||
GitLab |
point to groupimport and integrate |
find another DRI? | ||||||
Package Management |
|
JiHu |
point to groupimport and integrate |
change the docs metadata: !147432 (merged) |
||||
Project Management | Plan:Project Management ? | Community contribution (open source) |
point to groupimport and integrate |
change docs metadata? | ||||
Chat | Manage:Integrations | GitLab | ||||||
CI/CD | GitLab | Yes |
point to groupimport and integrate |
change the docs metadata: !147432 (merged) |
Closed and open issues assigned mostly to grouppipeline authoring, grouppipeline execution and groupimport and integrate |
|||
CI/CD | GitLab | yes |
no user docs, only API |
add user docs? in use? figure out. [Rutvik] - grouppipeline execution #438682 (comment 1830805350) |
||||
Project Management | Plan:Project Management (temporarily supported by Manage:Integrations) | GitLab | ||||||
Diagramming | Plan:Project Management | GitLab |
point to groupproject management |
|||||
Plan:Project Management | GitLab |
point to groupproject management |
||||||
Chat | Manage:Integrations | GitLab | ||||||
Chat | Manage:Integrations | GitLab | ||||||
Chat | Manage:Integrations | GitLab | ||||||
CI/CD | Verify:Pipeline Execution ? | GitLab |
@rutshah ? |
No |
point to groupimport and integrate |
update docs metadata ? may be the group that owns GDK (found https://gitlab.com/gitlab-org/gitlab-mock-ci-service) |
||
CI/CD |
Package:Package grouppackage registry |
GitLab |
no user docs, just API |
why no user docs? should be added? | ||||
Manage:Integrations | GitLab |
@jreporter for help with understanding where this belongs |
point to groupimport and integrate |
|||||
Project Management | Plan:Project Management ? | GitLab |
point to groupimport and integrate |
update docs metadata ? | ||||
Diagramming |
|
GitLab |
point to groupsource code |
|||||
Chat | Manage:Integrations | Community contribution (open source) | ||||||
Project Management | Plan:Project Management ?? | Community contribution (open source) |
point to groupimport and integrate |
update docs metadata ? | ||||
Spam Protection |
|
GitLab |
point to groupanti-abuse |
|||||
Change Management | Manage:Integrations | ServiceNow |
point to groupimport and integrate |
this integration is fully on ServiceNOw side, no code on GL, mention this in docs? | ||||
Chat | Manage:Integrations | GitLab | ||||||
Chat | Manage:Integrations | GitLab | ||||||
Chat | Manage:Integrations | GitLab | ||||||
Code Intelligence |
|
GitLab |
point to groupsource code |
|||||
Project Management | Plan:Project Management ? | GitLab |
point to groupimport and integrate |
need to adjust docs metadata ? | ||||
Chat | Manage:Integrations | Community contribution (open source) | ||||||
IDE |
|
GitLab |
this docs point to groupeditor extensions |
there's no other integration docs, I think can be removed from this table | ||||
Chat | Manage:Integrations | Community contribution (open source) | ||||||
Project Management | Plan:Project Management ? | Community contribution (open source) |
point to groupimport and integrate |
change docs metadata? | ||||
GitLab Incubation Engineering groupincubation |
GitLab (Incubation Engineering) | Yes |
point to groupimport and integrate |
change the docs metadata: !147432 (merged) |
||||
in docs - unasssigned, experiment | GitLab? | the docs are placed under Authentication and Authorization, incorrect? | ||||||
Diffblue | Yes | Correct group | ||||||
in docs unassigned | looks like no integration component is on GL side, should that be mentioned in doc, that integrations is fully under AWS? | |||||||
Source Code Management | Create:Source Code | GitLab |
points to groupsource code |
|||||
Project Management | Plan:Project Management ? | Via community contribution/GitLab |
point to groupimport and integrate |
change docs metadata? | ||||
SCM | GitLab |
point to groupsource code |
||||||
GitLab Incubation Engineering groupincubation |
GitLab (Incubation Engineering) | Yes |
point to groupimport and integrate |
change the docs metadata: !147432 (merged) |
||||
Test/Quality Management |
Community Contribution (MR) |
point to groupimport and integrate |
change docs metadata? Issue is still open |
|||||
Chat |
groupimport and integrate (because chat type) |