GitLab GitLab Group Kickoffs - Create:Ecosystem, 16 Jul 2020

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Create:Ecosystem 13.3 Kickoff

Description

13.3 Kickoff!

Here's all the stuff I talk about:

Solution validation for viewing Jira issues in GitLab: https://gitlab.com/gitlab-org/ux-research/-/issues/969

Add a dropdown for selecting namespaces in Jira Connect App: https://gitlab.com/gitlab-org/gitlab/-/issues/13020

Improve GitLab for Jira listing page on Atlassian Marketplace: https://gitlab.com/gitlab-org/gitlab/-/issues/229542

Integrations: Instance-level and project-level configuration: https://gitlab.com/groups/gitlab-org/-/epics/2430

Project-level integration: Implement project-level setting selector: https://gitlab.com/gitlab-org/gitlab/-/issues/218250

Add Telemetry For Enabled Instance-Level Integrations: https://gitlab.com/gitlab-org/gitlab/-/issues/204802

Deprecate Procfile: https://gitlab.com/gitlab-org/gitlab-development-kit/-/issues/904

Allow some services to be run under Docker: https://gitlab.com/gitlab-org/gitlab-development-kit/-/issues/867

A

Hey Patrick Dooley, here senior product manager forget Labs ecosystem group, and this is our thirteen three kickoff I want to highlight some of the work we just did talked about an integration that we've just expanded and then we'll talk about the work we're doing over the next month. So first super excited. This has been a really exciting month. It's been a ton of work. This is my test. Project will do Louisville. This is our existing two, your integration right when you add that it adds a thing in the sidebar. It sends you over there.

A

It also allows you to do notifications. If activity happens, so you run a commit. You reference a JIRA issue. It sends data over to JIRA we're also now able to go down to the JIRA integration. We can also view issues in get lab if you click this I take these credentials. You've provided I take a project key that you're, pointing at and inside of your project. You now see JIRA issues which still allows you to go navigate to JIRA, but it also shows an issue list.

A

So I can remind myself to watch more George, Clooney movies and bake quadrillions of cookies, and this is really cool, because this is a good foundation for our ability to start pulling more data in from JIRA inside of the get lab UI, we can help keep developers in flow if you're working inside of get lab throughout your day, we can- and you have to use your for project management. We can keep some of that information in there. So that's really awesome. That's exciting! We've got a lot of work. To do.

A

We've got more things to add, which brings me to my first point for 13-3. We need to do solution, validation, so, let's take the work that is minimal and we know it's minimal. Let's take that to some users, let's talk to them understand if they like the, where this is headed, what they want to see next, what confusion it may be causing right. So this is. This is JIRA issues inside of what kind of looks to be a native gitlab interface right. How can we improve this? How can we make this more clear?

A

We also have some improvement to be done around the JIRA, get lab for JIRA connect application. It's really basic today and specifically there's some kind of UX improvements, we'd like to add a drop-down for selecting namespaces, to make it easier to configure. Now we found that's a really confusing point. We also have another related issue. If you want there's a the error message that pops up is really vague.

A

So when you type in your namespace, you hit link, it just says invalid namespace make sure you have sufficient permissions like let's beam clear, let's add better user experience to that, so make it more successful for people to install correctly.

A

We also need to improve the listing page on the Alaskan marketplace, so our design, tech, writing and product marketing team is going to work on improving this it right now. It's really minimal listing it doesn't tell you a lot. It doesn't make it explicitly clear who this is for and how to use it. So we need to improve that and then we can move back to working on our instance. Level integrations as well, so we almost completed it in thirteen two. We still had a couple of things on the UI left over.

A

There's still lots to do in this initiative, but as far as getting the first iteration of this out, we need to complete the project level setting selector. So what that means is, if you have instance, level integrations enabled- and you have a specific project that wants to override that. We need to be able to select use custom settings so adding an option inside that integration that allows you to override, what's at the instance level.

A

So that's the first step towards overrides and being able to do more complex inheritance and that needs to get done in the first integral iteration, so that in a situation where a project does need a specific settings, which is gonna be most of them for today, because we're not doing other more complex overrides, it's really just instance or project right like you can I have have the parent settings have whatever specific ones you want.

A

So we need that be able to ship it, so that is gonna get done and then we're also adding telemetry, for instance, level integrations and the reason for this- and this is adding to the the usage ping data that we already collect about other integrate. What we want to be able to see is who how are people using this and who is migrating things over successfully from this.

A

So if you have 300 integrations that are individual today, we want to be able to see if you're able to successfully migrated that to an instance, level integration that also gives us a really good insight as to which services we should start focusing on being able to see how people are using integrations is really key to how we prioritize. So it's important on the foundation side. We are looking at finishing up deprecating proc file.

A

The reason for this there is some some work to be done on continuing that that deprecation as we move to run it so that we can start experimenting with docker, so that deprecated file issue is a blocker to be able to allow services to be run in inside. Of docker in the GDK, and the reason for that is we want to experiment with the gck as well.

A

That's one of the things that we have another team who's working on a project where you can run individual get lab services, the part of the get lab application inside of docker containers, which makes it more flexible and easier to maintain locally, but there's also this GDK project that we run and we'd like to see if we can have those to work in harmony, but we can't play with it until we can actually allow services to be run inside of docker. That's the first step to even experimenting with it.

A

So we want to play with that and then on the UX foundation, side of things I have talked in the past about individual components that we're getting done. I really want to bring up. This is a proposal. This is not the final state, but for prop the product organization, there is a q3, okay arm that is being proposed to make it lab faster than github by migrating eight of 38 components to fully use pyjamas. This is so cool. So this is a vote of importance from our product organization, engineering and UX are getting on board.

A

This is a really important push. I, don't know what the final OKR is. Gonna look like I, don't know what we're actually going to commit to, but it's really exciting to see support from the organization just migrating to this, these new components. So we've identified in this proposal there's an eye.the identified, pagination buttons alerts, tooltips tabs, dropdowns, modal's, popovers icons. We want to swarm on this and get as many people as we can inside of our organization. Working on this I know there are designers and managers, and even our VP of UX are personally migrating.

A

These things over. Let's get our engineering teams involved. We've also got on the engineering side. There's a big push to get. Hamel templates moved, so this is really exciting to see such a big push of effort to get this stuff done. So if you have, if you have time, if you have an engineering team, if you are just interested in pyjamas, please feel free to contribute. We would love to have your help. This is a huge effort and it's gonna take everybody to get it done. So with that that is our 13-3.

A

It's gonna be the best release ever we're super excited. I can't wait to see more things happening in JIRA. I can't wait to see our instance level. Integration, ship and I'm super excited to see pyjamas getting adopted by the organization, and that's it best release ever I'll see you in 13 4.