GitLab 12.10 Release Kick Off, 17 Mar 2020

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: GitLab 12.10 Kickoff - Ecosystem

Description

The 12.10 Kickoff for the GitLab Ecosystem group. This month we touch on the continued work on mass-integration and then dive in to some changes to the Ecosystem group, a shift in direction, and the new scope it will cover.

Group Direction page: https://about.gitlab.com/direction/ecosystem/
Mass integrations epic: https://gitlab.com/groups/gitlab-org/-/epics/2137

A

Hello, I'm Patrick, Dooley I'm, the senior product manager for get labs ecosystem group- and this is the 1210 kickoff I- want to touch briefly on the work that we're doing right now and the work that we'll be doing over the next couple of iterations, but I'd really like to focus on some changes that are being made to the ecosystem group and the scope that we are now going to have and some of the new and exciting work that we'll be adding to our portfolio of things.

A

We work on so real, quick, let's jump into mass integration at a group, an instance level over the last couple of iterations we've been talking about the work that's been required to get this done. There were a lot of backend changes.

A

There's been a ton of work under the hood to get this ready, but we've just completed some end-to-end mock-ups that we'll be executing against and over the next couple of iterations we'll be rolling out these UI changes, so these features will finally be available and as a quick overview for for those who may just be tuning in this will allow you to integrate an integration with many projects, whereas today, each time you want to integrate something. For example JIRA you have two integrated per project.

A

This will allow you to integrate it at a group, or instance, level where those integrations can roll out to lots of places. So that's still in progress, we're almost there we're gonna in the homestretch and so that work will be wrapping up here in the next couple of milestones, we're hoping to see group level integration launched in 13.0, but everything is still still up in the air right now, as we actually get this work completed. So we're hoping to have some good news here soon. But meanwhile we have some more interesting things to talk about.

A

So over the last month we have merged a new group contributor experience into ecosystem, and so that does a few things we're still covering integrations.

A

Although that work has shifted slightly and we'll get back to that, we're still covering the api's, although we have removed SDKs from our scope, but we are now adding the GDK and front-end and UX foundations, and so let's talk a little bit about what each one of these categories is and then the work that we're doing is kind of a refresher and that'll be more aligned with the work that we're doing going forward, so integrations hasn't changed much we're still working on third-party integrations, but the goal previously was to kind of support all of those integrations and instead, we've shifted.

A

Our focus specifically to a handful of high-priority integrations. So right now we're working on mass integration because it was the number one request for JIRA. We've also touched on Jenkins in a few places, but we're looking at addressing service now and rally sometime this year and then we have some considerations for other Enterprise focused integrations that we may touch later in the year. But the goal being creating new integrations that will drive new customers and create new value in places that were not able to work in today.

A

So things like ServiceNow are really important to customers who have compliance or change management needs rally is popular among enterprise customers for agile project management, so things like this are really important to certain sets of customers and we're gonna do more supporting more supporting of those features directly.

A

Our API category will be shifting to focus on governance and guidance across the entire organization so again. Similarly, our goal previously was to kind of peanut butter ourselves and try to keep the API up and running across the entire application. But really we found that it's better when we just support individual groups throughout the company to get them able to produce their own api's and support their own api's. So this category will focus on creating best practices and refining those best practices over time so that we're all marching in the same direction.

A

Now the GDK is a new category for us for those who haven't used it. Yet the GDK is the gitlab development kit. This is what allows you to create a local development environment where you can work on get lab on your own machine, so this is a really important tool. Every developer, who is working on get lab is using the get lab development kit to run that environment in man. So this is a really important tool for both our internal get lab team members and external team.

A

It's external contributors who may want to add code now. One of the things that's really exciting for me is pairing this with our API s and sitting it next to integrations is a really cool move for integrators for third party integrators who create integrations. Most recently, we had source graph and white source, both in the last few milestones have added integrations with their third-party products.

A

They were having to use the GDK to open up our code base and create their own integration, so this is really exciting that we can have all of the different aspects of integrating with get lab into one place, either contributing code directly integrating via the api's or otherwise, like all of them are here in one place.

A

To that end, we're also now the home of the front-end and UX foundations, so fern and UX foundations is where pyjamas lives so similar to the GDK. Pyjamas is the place where designers will do work, so this is a library of all of our components that are used inside of the get lab application. So, if you're looking to create new pieces of gitlab UI, you can use these components.

A

So here are our breadcrumbs, for example, right, like here, guidelines around how to use those and the actual view components are part of the get lab UI library. So this is really exciting, because we now have kind of an end-to-end view of contributing and integrating to get lab. So the new group is going to be a little bit bigger, we're adding some new team members.

A

We've got a couple more hires that we'll be making this year to also support all of these issues, but it's just a really exciting time as we grow our team and grow the scope of things that we're covering so that's 1210.

A

We've got some great work that we're gonna be doing around mass integration, we're hoping to pull that in and finish it out, and it's gonna be a good time for our team to settle into some of these new responsibilities, get to know our new team members and start driving forward with some of this new work. So it's going to be the best release ever for us and we're super excited to do it. Everybody stay safe, stay home and we'll see you next release.