GitLab Plan Stage, 6 Nov 2019

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Plan | Team Weekly Meeting

Description

Short and sweet Stage level team meeting on 2019-11-06

A

A

Okay, this is the Tron stage weekly meeting for the 6th of November 2019 I've got an announcement. First of all in the team update section on the 1st of January 2020 I'm gonna be switching roles and team, so I'll still be at github, but it won't be. An engineering manager and I would be working on plan, so I'll be joining the scalability team. As a back-end engineer, I did some stuff there, basically nothing personal, like I'm, very happy working on plan.

A

It was just that I've been talking to Tim for a little while about switching to an individual contributor role, and you know, haven't necessarily had a particularly close timeline on that. But then, when the scalability team was announced, afore that seemed like a something that I'd be really interested in so I applied for that got the position there. As far as I'm aware, we are trying to open the position to replace me.

A

We just haven't done it yet, and the for figuring out like how we handover stuff, exactly I, guess come on Tim and I all work on that, but yeah it's been great. Working with everybody. I will continue to work with you. Just nice, essentially.

A

B

Been a pleasure sings, it.

A

Looks like Kenan, Donald and John had an item about generating more handoffs, but it just says better: let's rush this out from last week, so I don't know yeah.

B

I think those Kenan Kenan put that and that was came from a call and cadence just here. Actually so maybe he can take a put that came from a call me and Donald thinking and hot pink, but are they last week, and it was just that yeah with with the new workflow labels and I. Think Donald in particular, is fighting that more. There are more and more hand office of work and makino. Do you want to take this yeah.

C

Sorry, for being a few minutes late guys, my Mac is updated and it's taking very long time. Yeah so I mean you know, John pretty much covered it. It seems were really just wanting to discuss how to either minimize number of handoffs like to do or make them more efficient. Just because McDonald and John and I all kind of feel like we're.

C

We get some downtime between the items when we do hand them off, they sit there for a few days, really get picked up and it's causing some kind of slow down and getting items across the board. We're just really curious if anybody else's experience that or if we can kind of get into more details. If we need to.

D

Okay, well with the next item, so as a way to try collaborating more with the rest of the engineers and trying this initiative of calling other engineers in the plan team for coffee great calls to get. You know what they have been recently working the challenges in terms of test automation and what I can do to help more.

D

Besides, what I have already been doing so since we don't have that many engineers in the call would ask especially you Sean and hole and and John to best, the best is over to to the rest of the engineers on your team. Please.

A

Can do just a point we do have in our communication guidelines that we don't really go in for like hierarchical communication. So if you just want to tell people that just go at me, I'll.

D

Just post honestly.

A

Yeah yeah, you don't need to like we're trying to avoid like a flow of information, we're like yeah sure.

D

We tell someone's.

A

Manager and then a tolay reports in the natal areas.

D

Yeah I would just post on as listen thank.

A

You, okay, I, guess that was a quick call.

E

A

E

Find that did the last minute when I started, we were talking about refactoring their shoe board and needing to refactor it, since it was like one of the older things in view that we'd written before we started using view X and for Braille and Paul and all the other stuff there I'm trying to plan out the roadmap for that and there's a lot of feature additions that are fairly like a fairly large lift, I think like swim lanes and some other things of that nature, and we also want to make real time like, is there or prefer to order that we do do the issue board in terms of like.

E

Do we want to refactor it to something? First, sly, crafty well, first and then add new features, or do we want to do it over time like? Is there any sort of strategy that I should be thinking about when trying to stage the roadmap so.

A

I think this refactor is mostly to do with the front end right.

E

Yeah but I was would assume that there's also some graphic. You all work on the back end that we would we need to do theoretically, you know if we're going to be doing anything or storing anything with issue lists and that sort of thing.

E

The reason why I'm asking is there's also features in the pipe to do things like configure boards to use local ordering on the board, instead of like the global relative, sorting number that we assign and just like a bunch of things like that, where, like I, would like to figure out how to stage the roadmap in a way that works best with highest quality engineering output that make sense.

A

Yes, I think from the back inside the way that we've done that with the sidebar has worked pretty well like a bunch of stuff for the sidebar like support in graph. Ql is already there we're, adding the things that aren't strictly blocking the front end but are like you know any mutations. Basically, any updates like Radi now as well, so I think you can probably do the same like yeah I'm. Not sure, though, does that, like answer your question, yeah.

E

I guess, like should I put together an issue for that now and start the process, because I don't want to like get to the point where, like we, we communicate that we're gonna ship some feature like swim lanes, but then it requires like a massive like lift to refactor before we can implement the new feature. Sorry.

A

Yeah I totally get you yeah like let's, let's go ahead and get started on that I think, as we've also been doing the sidebar stuff recently like we should be able to learn from that Alexandra see you're on the call and I know you did one of the issues related to add and if you had any particular thoughts on how like making that available in graphic UL went from the backend side.

F

Yeah so for the sidebar I think it was fairly well because it was broken down to very kind of small issues. Unlike some very specifics.

F

What needs to be changed in the graphical sorry, so I I, guess it makes sense to at least start an issue to look into that and just break that down into smaller parts, there's a kind of known now that can be done. I'm pretty sure, though some other stuff, as we change the UI and add stuff yeah.

F

A

A

Does that help get them yeah.

E

It does I'm I'm good. Thank you.

E

So, yes, it is the shortest meeting. Her cool.

A

Well, have a great day really I'm. Sorry I should have said if you do have any questions about like our stuff works out. I'm just gonna paste my message into the plan channel and feel free to ask me there or on strike or whatever. Obviously, a video call is not the greatest place for those but yeah cool.

E

Alright have a good day, everyone Thanks.