GitLab Simplify Groups & Projects Working Group, 29 Aug 2020

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: WG: Simplify Groups and Projects - early solution validation wireframes

Description

Early brainstorming session on what would a new organizational structure look like. Rough wireframe prototype video for solution exploration.

See related info: https://about.gitlab.com/company/team/structure/working-groups/simplify-groups-and-projects/

A

Hi, my name is daniel mora, I'm a senior product designer in the manage stage with gitlab, and today I wanted to kind of go over a task that we've been working on regarding simplifying groups and projects.

A

This is a working group to see if we can try and find a more simple organizational model within gitlab in addressing the problem between groups and projects and some of the inconsistencies between those and limitations that we currently have around that.

A

So this will be a simple wireframe demo, the idea being that we want to think of a new way to organize information or organize your business within gitlab. So the idea we wanted to create an object or an organizational container, that's separate from groups or projects.

A

This would be a more or less a blank screen or a blank page where you would start you'd want to create a new object, so here an admin would select a type of object for the container they want to work with so say I want to start building my team structure out or I want to create a code repo, the objects we need to deter, determine how to group them or build them, for example, epics and issues. This sort of object should live cohesively.

A

Project management, objects, wiki objects, analytic objects. What are the building blocks for these sorts of conceptual or functional features?

A

So in this case we're going to go ahead and make a repo- and this feature is more or less the same. For now,.

A

So now we have our project or our code code repo.

A

Now let's go ahead and define a dev squad that we can attach to that, so that they can begin working so we'll make a new object and from here we're going to go ahead and select uh team, and this is functionally the same again, we'll create a team name and then invite people.

A

Currently we need to have more investigation what this will look like or how this works, but I want to just kind of use this as a quick walkthrough.

A

So let's assume we've added some people, so next, we'll save and from here we have the two objects and now we'll need to connect them.

A

So in this case, what we'll imagine is we've built our organization out, we'll select the team and then we'll attach an object or the repo to that team so that they can begin working.

A

So here we'll say I want to attach my repo and my epics and issues that way they can track the data or track issues associated with the project.

A

So now we have our repo and our epics and issues associated to the team. uh Next, let's go back to the home as if we were to backtrack, that's what it would look like for. um Oh, we want to look at the screen next, what it would see from a non-admin perspective, so seeing a user experience like a dev and functionally. You would just see the dev screen of a repo uh on the left.

A

We would have much less stuff, that's not associated to the dev things that they don't have interactions with, would not show up here.

A

So now, let's take a look at nesting and sharing objects. The idea of how things would live in an actual in-depth hierarchy versus a flat architecture.

A

So we'll look at a team working with a project so we'll select the project, and here we have our dev team underneath it and they have the code package and registry associated to that project.

A

So here the admin view would be very similar. However, we'd have the additional features of allowing creation of sub-object or attaching objects to additional objects, so we'll connect some features. So in this case, we want to connect analytics and the epics and issues features, and now we have analytics and epics connected to this project.

A

Now this is all kind of work in progress.

A

I don't really have a future plan for this, apart from just a problem, investigation or solution investigation, and so we would really like your feedback right now to see what sort of solution we could come up with around this project, I'll attach the related issue and any sort of documentation that would support this we'd love to hear your feedback and provide more insight.

A