GitLab Ecosystem, 16 Feb 2022

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: GitLab 14.9 Kickoff - Ecosystem:Integrations

Description

Learn more about our plans for %14.9:
https://gitlab.com/gitlab-org/ecosystem-stage/team-tasks/-/issues/107

Learn more about our overall Direction:
https://about.gitlab.com/direction/ecosystem/integrations/

A

Hello, welcome to the 14 9 kickoff, I'm grant hickman, I'm the senior product manager for the ecosystem integrations team at gitlab.

A

Our team is responsible for expanding our ecosystem of technology partners, extending new integrations and integration features to get live users and leading the strategy around gitlab's apis. You can find more information about what we do on our direction, page, which I'll share in the description before jumping to the 149 milestone planning.

A

I wanted to start by taking a look at our okrs. We are starting a new quarter and we've established a few okrs that will will guide our work over the next few milestones.

A

So under the both product and engineering categories you'll actually see, we have a few themes tied to security and usability on the product side. We want to improve issues tied to our system, usability scores. We want to improve those scores.

A

We also have some improvements that will be related to our sister group, the foundations team under the ecosystem stage, where we'll be migrating, pajamas components, improving the pajamas design system on the engineering side, you'll see a few more of the technical security related issues that we're covering.

A

So we have a few remaining issues that are high security issue, high priority security issues, we're wrapping up a few missed slo issues, and we want to raise the mr rate 2 to 10., and then the last one I want to highlight is our okr around the delivering the first phase of slack work so, prior to this milestone for the past several months, we've had a focus on usability on security, and so now we're actually getting more of our team back fully focused on adding value that's customer facing in terms of integration work, and so the first thing that we want to prioritize here is development on our slack integration, so that kind of covers our okrs.

A

Let's jump into the actual themes for 14.9, uh so under 49 we have our slack integration updates. This will include two spike issues. uh The first spike issue is around our self-managed first approach versus a dot-com first approach.

A

We've had some discussion with the slack team and identified that there could be some some value or it could be a better approach essentially to to start by delivering value, delivering updates first through to our self-managed users, and we would do this using what's called app manifest, which are yaml-based packages that our self-managed users could pick up and and with no uh no delay start to update their configuration of their of their own gitlab slack apps.

A

This would help us to more quickly get feedback from those customers and start integrating new functionality. As we begin developing. The second spike that we'll be focusing on is around our security model and I'll pop that open.

A

We would like to better understand how permissions and and users will work within the security model of our slack application. So is this an integration that needs to be enabled at the group level? Is this something that should be enabled at the project level?

A

And can we inherit permissions from uh from the get lab gitlab security model directly so that we can enable features through those through those roles?

A

So, just as an example, as we kind of lay this foundation with these spikes, you know we'll be able to to kind of understand how we can give more granular permissions and access to manage configuration settings within the slack app, and this is kind of a maybe far-looking view or concept- that's still in flux, but we envisioned being able to have an a home app screen a home, app screen that would allow for users to kind of see what projects are connected to the application and kind of choose the granularity of the settings that they want to enable the notifications they want to receive per project.

A

So I think this would be really awesome. We want to just lay the foundation work and understand, what's involved, to make these types of features available, so jumping back into the themes.

A

The next key theme that we're going to be focusing on the 149 is around our jira cloud. App for self-managed get live users, so today we do have a cloud app for com. We've had plenty of feedback. This is just a key capability, that's missing, and so we're working to close that gap and make it super easy in terms of the interactive workflow to enable that through the atlassian marketplace,.

A

And so we have a couple screens here that will show you a little bit about what that looks like being able to jump into the atlassian marketplace, go to the gitlab for jira application and choose. If you are a sas customer or self-managed customer a link to your name space and and be able to enable that integration.

A

So we've we've done a little bit of the ground work or a lot of a lot of the ground work. Really. But there's there's a, I think, an oauth workflow, that's missing here and some of the front-end pieces that that will be wrapping up so that we can expose this in the new in the gitlab for jira application in the atlassian marketplace.

A

All right, the next theme is around tech. Debt, security and system usability score related issues, as we were discussing a few of the issues related here, would be improving discoverability of integrations through the left, sidebar.

A

And you're happy to follow this link and and learn more about this, but just being able to once you've enabled an integration to be able to surface that in the left sidebar.

A

We also will be working on adding adding integrations, adding logos to each of our integrations in the project settings page.

A

See if I have that tab open.

A

So, as you're navigating in your project settings going to integrations, we want to add some usability improvements here. Make it easy to understand what integrations are available and be able to present a logo. So it's easier to kind of traverse and navigate through those options, and there are a number of other issues related to security related to reliability of our web.

A

Hooks all right- and the last theme here for this milestone- is the dynatrace mvp integration with this integration will be included in dynatrace's cloud automation, marketplace, and this is going to start with a minimal web hook based integration, some light documentation on how to use gitlab through the cloud automation platform, and this will also lead towards future deeper integration efforts between get lab and dynatrace, and so we're really excited to be working more closely with dynatrace.

A

And you can see here is an example of where you might see us in their marketplace and be able to discover our documentation all right. That kind of covers everything for this milestone. You are welcome to follow up and follow the link that I'll add to the description to see more about our milestone plan share feedback. You can also go to our direction page this. This shares more information about how to find us what issues we're working on and how to share feedback.

A