GitLab Manage Stage, 12 Aug 2021

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Manage:Import 14.3 planning

Description

This is the sync planning session for the 14.3 milestone for the Manage:Import group.

Planning issue shown:
https://gitlab.com/gitlab-org/manage/general-discussion/-/issues/17369

Notable issue mentioned:
Migrate Empty Projects - https://gitlab.com/gitlab-org/gitlab/-/issues/267948

A

Hello and welcome to the planning call for import for 14.3.

A

I'm going to be sharing my view, so we can all take a look at the agenda and the planning issue.

A

So, for 14.3, the team is the same as last month,, but that does mean that we still don't have a.

A

Replacement for the ux designer.

A

Or an identified stable counterpart for security, so those are a couple things to note. on ux,.

A

Illya and I are trying to kind of cover as much as we can,, but we do have the ability to ping nick,.

A

So if there's any kind of ux questions that we have, we can ping nick with just pointed questions,.

A

We can't give him like larger research to work on,, but he's offered to answer questions and provide.

A

Guidance on ux. on security,, I think we're supposed to ping the entire team but,. I think I've been.

A

Pinging dominic recently because he's been commenting on a lot of our issues and.

A

He seems very responsive, so I feel like we do have maybe not a fully stable, but a counterpart.

A

Who helps with security,? So just keep that in mind as you look at issues.

A

So,, as far as the capacity goes,, we have kassio gone at the end of the month for the remainder of.

A

14.3 so we plan to have him for about two weeks and other than that on the backend. It will be.

A

George fully and on the frontend we'll have illya.

A

Andrey,, I see you have a few days at the end of august, but you know whether it's the end of august or.

A

Beginning of september,, it's still going to be the same impact to 14.3,, which we'll just keep in mind.

A

So, on capacity, a couple of other things, there has been an engineering allocation that.

A

Has happened for the backend. if you're not familiar with that,, you can read up on it.

A

On this, on the url that I linked over in the planning issue,, but you know,.

A

Long story: short,, we are dedicating half of our backend bandwidth to improving the infradev issues and.

A

Security, so there's been, we haven't been able to really you know, draw down the security.

A

Backlog, we've been staying on top of it,. Some other groups have really been, you know,.

A

Even adding more to their backlog,, we've been kind of staying on top of things, especially the p1s and.

A

P2S, but we are really not able to make a large dent in the p3s and s3s and s4s. And that's.

A

Also important, so we need to get to the bottom of that. So that's one area and the other one.

A

Which is a lot smaller. Backlog is infradev,, but those have huge visibility and any kind of outage.

A

You know would have repercussions,, so we do need to get on top of that. So to do that, we are.

A

Going to really focus on infradev and security until we get until we feel we're on top of it.

A

So,, when we later review the uh kanban board I'll kind of show around where those issues are.

A

And how we're going to try to accomplish that? I just want to keep in mind that that is part of the.

A

Capacity discussion as well that some capacity is just allocated for certain issues and it's on our.

A

Team to make sure that we respect that and enforce that and kind of do what we're supposed to do here.

A

um So I do expect so just I think I've kind of said it, but I want to say it.

A

Explicitly I do expect these issues to go through our regular process, so we will plan for that.

A

We will use our kanban board to work on those issues, so this is not going to be a separate.

A

Outside process that we all have to manage, we will manage this part of our current process.

A

Next up, looking at team velocity.

A

Clearly, we've been distracted by a lot of things and it really got bad last month with the.

A

Customer escalation that you know uh the back-end team spent a lot of time on.

A

So our velocity has dropped. We, you know we didn't really close as many issues or as much weight as.

A

We normally would, um and you can tell that you know if you look at the uh back end average.

A

Velocity for the last three months, which was 30 and it used to be in the 40s. But now it's in the.

A

30S, but just the last 30 days is 13, so it just tells you that that has significantly slowed down.

A

And the front end keeps moving at kind of a similar pace.

A

As it has over the last three months, so that's kind of where we are on that any thoughts.

A

Questions comments about this: how does this sound as far as capacity discussion, velocity and stuff.

B

I mean from my side uh yeah I spend a lot of time. You know on the github importer.

B

um Well, at least two weeks or two and a half weeks at this point, um it's like more than.

B

Half a milestone um yeah. Hopefully it's gonna get better, although I'm pessimistic.

A

Well, at least we should so it may not get better as far as.

A

Like what we're working on, but how we're doing it, it hopefully should be more planned and more.

A

You know more kind of more thought put in it ahead of time.

A

As opposed to being reactive, as opposed to just you know, managing a lot of this through slack and.

A

People being pinned by different people yeah, so uh you know that's the one thing that we we should be.

A

In control of- and we hopefully can get on top of- is sort of how we're managing that. So we may.

A

Still work on, you know certain type of issues, but it shouldn't feel like it's a free-for-all: cool.

A

Okay, uh so to talk about that a little bit, I want to step back and talk about a roadmap. You.

A

All may have seen the roadmap issue that had weeks worth of different discussions and a lot of people.

A

Involved to try to get everybody on the same page as far as sort of what should this group work on.

A

Should we work on customer escalations, should we work on delivering some of these long-term goals.

A

And you know just about a week ago, we have arrived at a conclusion that our group should.

A

Be mainly focused on uh directional items on delivering the long-term solutions for.

A

Gitlab migration and scaling the github importer, and then, of course we have this last minute change.

A

With the engineering allocation, we need to kind of weave that into this discussion, but I do want.

A

To share with you the uh the roadmap view that we currently are gonna. You know that we're gonna.

A

Try to follow so this is the roadmap discussion that we've had in that issue. uh Tran uh kind of.

A

Moved into gitlab, so you know identifying those epics. These epics have issues in them.

A

That will you know kind of solve that will will use to deliver uh these features.

A

And uh I have laid them out in a way that they were laid out in the proposed roadmap to sort of.

A

For everybody to see sort of where each one of these starts and where each one of them ends.

A

um Of course, this is not a fixed view, so this is a view that will change as things change.

A

So um if we, for whatever reason, spend another month doing something other than what's on the.

A

Roadmap then, the entire roadmap should, in theory, shift to the right there's another way to manage.

A

This and that is also through scope, so, for example, what is included in the scale github? I have.

A

Control over that, so I can also just say that you know when we get to that. If all I want to do is.

A

Spend two months on it and then that's it. That's another way to sort of control the scope of it. So.

A

It doesn't necessarily contain all of the issues and all of the features that are discussed.

A

In this epic, but it could be that no we're just really going to spend three months on this.

A

Then three months on that and then two months on this and to whatever depth we can get there.

A

uh We'll keep it that way, so I'm just wanna bring up that. There's really two ways to manage the road.

A

My point is to keep extending until we uh fully do the feature. The other one is for me to sort of.

A

Decide where the 80 20 point is and say you know this is enough. Now we're going to switch over to.

A

This other thing, because we need to really get to the end of that by whatever the time promise so.

A

You know uh none of you, or none of us really should be uh expected to do miracles. We will.

A

Do what we can each one of these, and um if the amount of work is bigger than what's on this.

A

Timeline then either the timeline extends or the work gets less. So you know don't feel like.

A

This is exactly how things are going to run, but this is sort of how our.

A

View is of what's going to happen over the next year. Is from this point.

A

I do want to try and dog food this. I want to give this a whirl and see if this is still useful. A.

A

Month from now three months from now, or does this gantt chart like a lot of others, I've used before.

A

uh Sort of fall apart, so this will be a good test of our road mapping feature and I'll. Try to also.

A

Know provide feedback to the to the group that works on this.

A

uh Sort of one, what kind of things they can improve so uh bear with me here, as I'm doing.

A

This uh use it as much as it's uh useful to you, but I just wanna kind of bring up the fact that.

A

I'm going to try and do this, and this is kind of review that you can go refer to.

A

To see sort of where we are so, where are we right now? The red line uh tells us that we are actually.

A

Done with the parity with group export imports, so this is accurate.

A

uh At the end of this release, so that's that that that far you know if I were accurate, the github.

A

Imported by reliability improvements, um I feel, like we've done a lot. A few are getting wrapped up.

A

This is one of those where we're not going to get to the end of all of the issues in here before we.

A

Call it done for now, so you know I will you know we will split the epic into what needs to be done.

A

Right now, to sort of have us be stable enough to be able to execute on the rest of the roadmap and.

A

Then come back to github later so this is kind of a you know: stabilizing github importer for now.

A

We are starting in this in this milestone on the project migration. So we'll talk I'll talk about.

A

That in more detail, when we get back to the uh objectives of this milestone, but I expect this to.

A

Run at least three months and we'll see at the end of three months, if we need to extend it further.

A

Or if maybe we have enough to be able to move on onto the next thing, which is then switching over.

A

uh Really these two epics go together and they together form the project export import.

A

Replacement uh I've split them into two just to sort of have a more manageable.

A

Chunk, so it's not just like one huge chunk that is like this gets delivered in six months, um so.

A

This may not be exactly accurate, but I I'm gonna, try to sort of you know split these.

A

A little bit so that we have more control over the details, but uh in theory by uh you know, 14-6.

A

We should have the project migration happening in as far as as part of the gitlab migration.

A

And we should have already started the work by then on the users I mean some of that was.

A

Done with the spike, but we'll as we wind down the project, uh migration, we'll then take a look at the.

A

uh You know like the research for users and maybe do a few uh proof concepts and.

A

Just kind of start getting things uh done, you know as far as discovery goes as well.

A

Probably some solution, validation, it's gonna, be some work. That's gonna happen here in november.

A

Potentially in preparation for us to really just hit the ground running in december, on that.

A

And I think all along we'll be paying attention to the ux. uh There will be.

A

Some features that will be left in here that we need to wrap up. But you know some of this stuff.

A

Will get delivered along the way, as you can tell, that's actually already been happening.

A

And hopefully by you know the end of the year or by january. At this point, because I actually.

A

Have moved everything by month already because of how long the discussion took to talk about that.

A

So this was going to be the end of the year, but now it's end of january that we wrap up.

A

The gitlab migration, hopefully and uh switch over to the github importer for the um for the next.

A

Five months or so to um to get that completed, so that is the roadmap. From this viewpoint,.

A

um This is also provided that the team is kind of stable in uh in throughput or in capacity.

A

um So thoughts about this, does it sound like crazy, unrealistic? Maybe.

B

um I just wanted to point out a few things, um so just something just an observation, not.

B

About how realistic or not it is, but the gitlab migration repositories, that's probably should be.

B

Done before the gitlab migration projects, because repository is like the fundamental thing of.

B

A project without which um I mean there's, uh there's no merge requests, there's no.

B

um I don't know a repository is like a fundamental part uh that actually.

B

Blocks the import of everything else, so uh I feel like this should be done prior to that.

B

Prior to the projects, you know like issues, merge, requests, etc um and just just another.

B

Observation that I I noticed like the github importer, reliability improvement, um epic.

B

Like um it, it says they're, zero percent. Does that mean like none of the issues that are in there.

B

Were completed, this is by weight, they probably haven't been waited if they haven't completed.

A

So I'm guessing these three that have been completed did not have uh weights on them.

B

Okay, well, I don't know if all the other issues in this epic should be done uh or not right, we'll.

A

Have to probably figure out how much of this epic is needed now versus when we come back to.

A

Github importer uh in january right, so this is sort of to get a stable at this point as.

B

Far, as I know, the only issue that is well not the only one, no, that that's not wrong. That's not true.

B

Like uh well, the big change that I'm working on is regarding the customer migration. Then there's.

B

A number of things that casio is doing um to show um like some bug, fixes and grafana. um I'm just.

B

Wondering if they should all be kind of, oh they they all are. They all are in there. Okay, never mind.

A

And these have way so when they get when these are closed, we're going to get the percentage.

A

Going up in the meantime, we could probably take a look at these and just assign some weights or get.

A

An idea, and maybe even pre-assign, some weights on these and just don't, don't even tag it as.

A

Estimation completed but just assign some, uh you know temporary weights to maybe give us an idea of.

A

Where we are, but really I do want to manage this by uh time boxing, because you can always improve.

A

Reliability so by saying: okay, we're gonna, spend you know about two milestones or two months on.

A

This is uh all we wanna do um and that kind of is gonna force us to really draw a line at some point.

A

And say: okay: well, these are the important things these things can wait until we come back to it.

A

uh And and then we'll manage that by by time boxing it um but yeah, I do want to wrap this.

A

Up this month, so the things are in progress right now. I expect those to be wrapped up by fourteen.

A

Three, if there's any spill up for 42., there's a spillover on the issues that currently in progress.

A

It's spilling to 143 we'll take those, but I don't think we should take any. uh We should add any.

A

New issues from this epic into 14 14-3, because you'll see that 14-3 is busy with other things.

B

B

Just one more thing, I guess um in terms of unexpected engineering allocation, should.

B

That be reflected on the roadmap too. I mean, I know it's not product roadmap, but.

B

You know if you're looking just on this, you are missing out on other important information right.

B

There right so, you can look at this two ways. One is a comprehensive everything. We're working.

A

On which I believe for us, the kanban board is that this is the directional roadmap. So I think.

A

This actually gets impacted, so the fact that we're like you know we are zero here in october.

A

Is a call out that we've been doing something else, uh so those would be the flags as opposed to.

A

Actually, putting something in there and saying you know this, is this was sort of planned or.

A

After the fact putting it in there, I think we sort of let the impact be on this, and then I.

A

Can you know we can show this as now? This was the roadmap we agreed to because of these other things.

A

You know the impact was such that we're now way behind. Like you know, look the red line is.

A

Here and our percentage field is over there like two months behind. Therefore, everything is behind.

A

By two months, uh which d we can then manage by maybe adding more people to the team to sort.

A

Of catch up to that, but I feel like this is a good um radiator of what's happening. Directionally, okay,.

B

Thank you sure, any other thoughts. Good thoughts, though I mean.

A

This is really the good discussion that I thought we're gonna have.

A

um The proposed objectives, so I'm going to list them all and we're going to talk about how we're.

A

Going to attack them, but uh for now just kind of listing the things that we are going to be working.

A

On or thinking about in 143, the directional item, like really the only directional item that.

A

We're gonna try to make any progress on is going to be the gitlab migration.

A

And really, my hope is to start the project migration by migrating empty projects. I mean.

A

We had some discussion on this issue, so this is, they just moved the project, along with attributes.

A

That are part of the object, but none of the relationships that come with the project. So that's.

A

That would be like the the first step there, and if we do that in this in 143, then that's uh it.

A

Feels like we've accomplished things. I've listed some things that are still in progress that are in.

A

14 2 here because they had a possibility of spilling over so I've listed those there. So.

A

That we know that there are some things that we're kind of committing in this area. uh And if.

A

They're not completed, then uh you know- and I know that um ilya you mentioned- that both of these are.

A

In review and expect them to be done in 14-2, so that's great so we'll take into account the fact.

A

That you know this has been checked off and it's 14-2 and it's not really spillover. um The other.

A

Thing related to gitlab migration is testing in quality in end-to-end tests, so I know that there.

A

Is an issue already inside the e2e test coverage for gitlab migration to test epic migrations.

A

So that may be a good one to uh mark for 14.3 and actually get delivered in 143, because epics.

A

Were delay are being delivered in or actually we're delivering 14 1, so it's probably good for.

A

Us to just automate that testing and make sure that we don't break any of that moving forward.

A

So it'd be a good one that I suggest we take on uh the other thing, that's still in progress.

A

Is the uh github importer testing with large uh data samples so that one is in verification in.

A

14.2, but I understand that if it does build into 1430, it may have effect on, like our bandwidth.

A

So just want to list it. There is something that maybe a spill over um andres any other thoughts.

A

On things that would be important to pick up in 143. That may be more important to some of this.

C

uh Not more important, but I do think that the epic migration won't be the only one.

C

It's just I haven't yet created the issues for other objects that we would like to test.

C

For migrations, so I'm fairly certain that epics won't take like the whole 14.3.

A

Perfect, I was hoping that we would be able to add more things in here and.

A

Yeah, so this will be the stand-in for that. Well, we're going to commit to this one thing.

A

We can get other things done at the same time, then that's really the right thing to do.

A

Because this is where we should be spending time for this particular milestone.

C

Yeah and regarding the github importer, so I'm not sure if there's much to do like from the testing.

C

Testing perspective there's one last thing that is missing uh for our automated solution is that.

C

We are currently limited by our, uh like runners set up on like gitlab.com, because the longest.

C

The pipeline can run with four hours and like for truly large imports, it's like not enough uh so.

C

uh I would need to kind of create our specialized runner and I'm still kind of.

C

Asking around what is the procedure where, where I could get like a resource to host it.

A

Is that the same limitation? We have on gitlab.com.

C

It's like it's the limitation for like where we can run a pipeline yeah on gitlab.com, so that.

C

All the runners by default are limited to timeout in like an hour and a half.

C

And there are some specialized runners that can leave for four hours, but like not more than that.

C

And if you want to like continuously test import, even like with like not super large.

C

Project like, for example, something like with the 6 000 issues and 6 000.

C

Pull requests, it does usually still take more than four hours.

C

So because there's there was an idea to use this pipeline, because you can also run it manually.

C

You can kind of use it to just to like validate some specific projects. So if a client would like.

C

To try and do an import that that could be used as well. But right now like we need to address.

C

The issue that you can't run anything that will take more than four hours. So is there an issue to.

A

Discuss that, because I feel like that's something that we should uh escalate back up and also, if.

A

This is something that just happens with our uh you know: customers using on gitlab.com. uh You know.

A

Then that may be something that we need to extend. I know we've had issues with our github importer.

A

So if runners are being filled after four hours and we're just not done, then that's a problem.

C

Yeah I want to just clarify by runners I mean like pipeline, like the the ci okay.

C

Yeah yeah so like in order to run this test and validation, we need to run it on the pipeline and.

D

The test itself times out because of that, like it gets killed by the ci runner. Okay. So let's.

A

uh I mean you can see me on it or the engineering managers, uh because we're probably gonna need some.

A

uh We're going to find like who the right persons are, and maybe even uh the quality.

A

Leadership is the right people to be involved, but I definitely think we need to make this happen.

A

Yeah yeah, I had a chat with the engineering productivity team. uh I asked on the slack I think.

C

uh Kyle should answer answer like something in nearest.

C

Future and if not, I might create an issue or something so it's not lost in its life.

A

B

Can you just an idea, random food for thought? Maybe um what if, after the timeout, you know the.

B

The pipeline, you, you restart it or whatever, let's say like an automatic restart that just.

B

Keeps going you know off, maybe like end the pipeline on the three hour mark or whatever.

B

Because it's still in progress and restart it and kind of carry on from there, you know to re.

B

To as a way of resetting the timeout, um I don't know just something to think about, it would be a.

C

Little bit harder than just finding a runner that can live longer, because I would need to persist.

C

All the like github data and then also save all the objects somewhere to read, write properly like.

C

It wouldn't need to remember which, which group, what which project it started importing.

C

And it also kind of keeps in memory all the github issues and requests to compare after the import.

C

Finished yeah. That means I would need to persist them somewhere, but that could be an option. Yeah.

A

Okay, um so now we're going to talk about the engineering allocation.

A

So the engineering allocation concerns and infradev and security items.

A

uh I have listed the two infrared items that we actually have open against uh group import here.

A

As well as a few security items that I feel that we could or issues that I feel like we could.

A

Pick up here so before we go into the detail here, I do want to kind of take a look at the.

A

uh Kanban board and just make sure that um you know we're on the same page as far as.

A

Like how that's represented here and uh I have uh combined the uh engineering allocation items,.

A

Onto the kanban board, so they're all here, if you search for engineering allocation, you should.

A

You should be able to find those items on the board so.

A

If you're trying to pick up one of those items, if you're trying to split the time.

A

And it's time for us to pick up an engineering allocation issue. This is the filter to apply you.

A

Will see that we actually have two in review one in dev, four, in ready for dev, one in refinement.

A

Two in planning breakdown and the rest of them kind of can start, which means not really started.

A

Yet um I've also pinged the engineers on the planning issue for security items to sort of.

A

To to see, if there's anything that they would like to cherry pick, so I'm okay with.

A

Things being picked out of kind of out of order in a way if it's an easy win and if it's. If it's.

A

Something we could take off the board, make the board more manageable. I think we identified a few.

A

That I've put a little cherry on, so um those are the ones that you know like it's. Okay to just go.

A

Well, actually, any one of those is okay to take out of order, but these are prioritizing order. They are.

A

Kind of listed in the order of priority in the order of severity in the order of the impact.

A

To to to security, um the one thing that's maybe slightly out of order when you look at this.

A

Is really this item here in refinement? It is a higher priority than than what it looks like. We.

A

We had a couple of incidents related to this potentially, and the infrared team would really.

A

Like to prioritize this, so as we look at um you know this particular backlog, the engineering.

A

Allocation backlog, I'd like for you to consider refining this item and kind of putting it on top.

A

Of the ready for dev before picking up the next thing, from ready for that, and I will I.

A

Should have done that, I will indicate that by the milestone priority as kind of per hour process.

A

Yeah, so that should do that other than that they are in order and.

A

If you want to take a look at just kind of the purely directional items, you can see those as well.

A

So these are the items that advance our roadmap in a way and you'll see that.

A

You know, currently, the the only one that's being planned for 14.3 is in planning break breakdown.

A

Because that may get split into a couple of issues. So that's something to just do uh you know, as.

A

Early as possible prior to 14 30 is just make sure that we know if this is one two or more issues and.

A

Have those issues kind of move into refinement? um You know by the time we're ready to pick them up.

A

In 14 30., so this is really the only directional item. That's uh that's being planned for 14.3.

A

And that's because, uh even though the engineering allocation is 50, what that means for 14 3 with.

A

Casio being out for two weeks is that uh you know we still need to allocate one uh full engineer.

A

Toward the engineering allocation- and we only have two weeks worth of work available for.

A

Okay, so you said three weeks.

A

You mean three weeks for fourteen three that you can allocate or I'll be out totally for three.

C

Weeks, oh, you mean two weeks out for thirteen two yeah. Sorry, oh my god, yeah for for fourteen.

A

uh You will be here for two weeks so out for three, but here here for two, so you have two.

D

Weeks worth of bandwidth in 14 3., so that's really the bandwidth that we have to play with.

A

uh To make progress against direction- and I think two weeks is not going to be enough to uh to to.

A

Get all this done potentially so it may be for one of the issues, but if it gets split into a.

A

Couple of issues, uh maybe only one of those comes across and if multiple come across, that's fine too.

A

But um that's the bandwidth we have to we. We have that we can use against the directional items.

A

The other bandwidth, which is a kind of a one month worth of a back-end engineer, will need.

A

To be spent against the uh in for them security issues, which is why you know these are listed.

A

And which is why the kanban board actually lists uh you know, has all of that lined up so.

A

Those are more lined up than directional items because that's we're going to draw from more.

A

Than from directional um for this particular milestone,.

A

So there's two ways to handle this uh one would be for each one of the back end engineers to.

A

Sort of split their time, 50 50, while they're here on on any issues or.

A

We can just potentially have maybe casio work on this and george work on.

A

The security backlog for this milestone and maybe switch it next milestone, so, whatever you think is.

A

Better, whatever is uh you know, I'm thinking less overhead or less uh context, switching or whatever.

A

Makes more sense for a higher velocity, I'm open to how you want to do that. So what do you think.

B

Well, I don't mind working on infra dev insecurity. I mean I saw you propose that in the comments.

B

I mean whatever casio prefers, I'm I'm I'm here the whole milestone. So I don't really.

B

Mind, whatever is best same here actually, whatever is on the top of the priority.

C

I can pull it up yeah. Well, I'm working on uh infra dev issue already. I don't know if it makes sense.

B

um Well, I don't know like there's another infrared issue that is p1 right is per hour, milestone.

B

So, but that one that is in refinement, actually I'm not sure if there's there are any actual.

B

Actionable items because it was discussed before and I mean we we can, we can revisit it once again.

B

But I'm not sure if there's going to be any actionable code, changes that can be done in.

B

Order to address that uh I mean maybe it's worse, giving it a time box investigation once again.

B

But yeah anyway, like uh we'll figure it out, I don't think we should well. We should uh do that.

B

Now but it's a good point that you know as we're refining this uh if there isn't a clear proposed.

A

Solution, if there's any clear uh technical approach, then we just need to time box this.

A

And say: okay, we're gonna, spend whatever you feel is appropriate time to really get to the bottom.

A

Of it and then at that point we kind of stopped and say you know there isn't anything we can do.

A

For this particular scenario, because you know it it would be, it would hurt our plan a lot.

A

If somebody was just like researching this for a month um and not not got anything else done so.

A

um It's probably good to just uh put it down after a couple days and then move on with the.

A

Engineering allocation backlog with other things that are also just as important.

A

Cool so as far as the issues go, I've listed just you know the couple from here.

A

The interesting one is uh is one that I put uh sort of. It is backhand, but.

A

It's also the front-end uh engineer, who's uh volunteered to pick it up.

A

We had a discussion about that and, yes, I think it would be helpful if you help with more.

A

Than just one of this items, so I know that you identified two or three that you feel you could.

A

Make impact with- and I think that'd be good to just get.

A

um Get that initial, quick, just cherry-picking and getting the.

A

That particular backlog to a more manageable state. That would be very helpful. That said, there are.

A

You know there are other frontend issues that we can continue to refine. That may be sitting.

A

In design right now, so we'll I'll take a look at that. The reason I didn't line up anything else.

A

Is because both of these didn't look like they were going to get delivered, especially the um the.

A

The re-importing one, which was sitting in design kind of as of yesterday, so I did not expect it.

A

To be done in 142, so I really haven't lined up a lot, but there is definitely work that we can do.

A

um Kind of on the front, end and ux side, uh so I'll identify a few I'll identify a few things.

A

Once you're done with the security items that you feel you can help with that, you can then take on.

A

14-3 and some of these are potentially larger, that may require refinement and really kind of a.

A

Leadership on a particular feature to you know, break it down and make sure we have.

A

All the things lined up so there's plenty of work there. uh We can chat about that.

A

Now, finally, there is a bug. uh There is a bug, that's also in refinement.

A

That we'll need to pick up it's uh kind of mixed in with the security and other things, but.

A

It seems like something that should be working or somehow, like is a recent degradation of.

A

What we have so uh I know that, oh you have assigned it to 42.. Well, let's find them cool.

D

Yeah I'll take that wasn't much is this is literally the next thing I'm playing to work today.

A

Okay, cool so yeah, that's good and then then you can uh switch back to wrapping.

A

Up all your front-end stuff, helping with security. In the meantime, let's discuss.

A

What are the next big things for frontline that we can line up uh for you to work on.

D

Yeah sorry for late delivery of reimport, it was uh pretty unexpected for me too, because.

D

uh I was working on bulk import and suddenly realized that this is a good.

D

Opportunity to do this, while I'm focusing it was like a natural follow-up awesome.

A

No, don't don't apologize for that, like you know, please do that.

A

So um finally, how do we feel about like what's listed here? So let's say you know we have this.

A

One that's kind of in progress, but it's being led by uh someone else and I feel like it may require.

A

um You know one of our engineers really getting in there and just wrapping this up.

A

And calling this done so that's kind of this is a long story um and it could be hairy to.

A

Wrap up there have been some improvements but they're. Looking for additional improvements.

A

Then there's this thing: that's a time box and then there's uh at least two security issues.

A

That we should be able to you, know, sort of pick up from the top and they're ready for.

A

Development they're ready to go and they're both kind of in the same box, which is the dns rebin.

A

Srf and two different importers, um and then there is this directional thing that needs to happen at.

A

The same time so do do you feel like um that's too much? How can we, you know mitigate any risk there.

A

Or maybe, since this is just gonna, be like things in order, um how about this migration.

A

Of empty project is that realistic to be completed in like two weeks of casio.

C

C

I think so, but not a hundred percent sure.

A

Okay, that sounds like a good goal, that it is possible and.

A

Achievable but may not be easy to achieve so we'll set that as a goal.

A

I have final thoughts, other things when you talk about.

A

Elephants in the room- uh no, I just want to say uh thanks for um putting concrete items on the.

B

On the proposed objectives, as far as I remember, we used to have like a very broad list of things.

B

As proposed objectives, which felt a bit uh overwhelming every time you look at it.

B

And you know kind of having a sense of uh underachieving every time. um So no it's, I think.

B

It's great to to have like a a list of specific things that um we are trying to implement as part.

B

Of a milestone, yeah, it's gonna feel better. I think I don't know thanks for doing that,.

A

Okay, so all thumbs up for the plan?.

A

So,, well thanks everybody for participating.. This felt like a really good session,. I feel.

A

Like we, at least, I feel like we're on the same page, hope. Everybody else feels the same. Way.