## Description We are creating a [working group](https://about.gitlab.com/company/team/structure/working-groups/) related to the GitLab API vision. The API is a cross-cutting concern, and many engineers in the organization develop, update and use the API. The Ecosystem:Integrations group is responsible for the core/foundational code of the API. But, due to the importance of the subject, we believe it is appropriate to include more engineers to understand the current problems and help us reach the best possible solution. The idea of creating the working group is a follow-up from https://gitlab.com/gitlab-org/gitlab/-/merge_requests/74461#note_750377473. You can join the working group ([roles thread](https://gitlab.com/gitlab-org/gitlab/-/issues/348558#note_809860349)) if you want to collaborate actively with us. But if not, we would love to hear any comments you want to make on this issue. This is a list of topics that we want to discuss. Feel free to add more or join the discussion in the [topic thread](https://gitlab.com/gitlab-org/gitlab/-/issues/348558#note_810209544): * Discuss responsibilities, DRIs, and technical experts * REST first vs. GraphQL first vs. another approach * Review APIs architecture * Review APIs coverage * API performance * API testing coverage and tools, eg. Postman collections * REST v5 API * API deprecations life cycle * API Standards, including OpenAPI specification * SCIM API * Documentation * Automatization of the new documentation * First time API user experience * Learning paths for team members, especially about GraphQL --- - [x] Preparation - [x] Create a working group page - [x] Assemble a team from required functions - [x] Share in appropriate Slack channel(s) to encourage a diverse group of participants - [x] Create an agenda doc public to the company - [x] Create a Slack channel (with #wg_ prefix) that is public to the company - [x] Schedule a recurring Zoom meeting - [x] Define a goal and exit criteria - [ ] Gather metrics that will tell you when the goal is met - [ ] Organize activities that should provide incremental progress - [ ] Ship iterations and track the metrics - [ ] Communicate the results - [ ] Consider regular updates to the #whats-happening-at-gitlab slack channel as progress is made towards goal. - [ ] Communicate outcomes using multi modal communication. - [ ] Notify widely of exit outcomes via channels such as the engineering week in review. - [ ] Disband the working group - [ ] Celebrate. Being able to close a working group is a thing to be celebrated! - [ ] Move the working group to the "Past Working Groups" section on this page - [ ] Update the working group's page with the close date and any relevant artifacts for prosperity - [ ] Archive the slack channel - [ ] Delete the recurring calendar meeting Reference: https://about.gitlab.com/company/team/structure/working-groups/