GitLab Create Editor Group, 16 Oct 2019

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Editor Weekly Sync - 10-16-2019

Description

Editor Weekly Sync - 10-16-2019

A

Hello, hello, were you just speaking German when I walked in yeah, as you should? Are you doing?

A

How would you cool the summer is kind of gone, but I mean still here, but it's okay talking about autumn and Lisbon, we got rain for two one day this week, I'm like what is this yet one day without way in the last two weeks, so keep them back. Yeah.

B

We're good to go yeah all right. First up, let me into the 12th is planning okay and if it's really Eppley I'm sorry, the 12th I've planning up to me like, where are we in terms of weights and capacity well, probably needs to be like locked in today right because the milestone starts Friday.

C

Yeah so so I mean I like updating that issue, so I updated the issue. This front planning issue some clean it up now. So.

D

The capacity that we have is.

C

I think 19 I say think because mark isn't here we I just got back and I haven't, had a chance to talk to mark and I won't be able to get anything from him until tonight.

C

So that's the capacity the issues we might need to move some issues, I'd lose some issues to 12:5 and kind of assuming that's okay, cuz they're, not gonna, make twelve four or should I kept me and twelve for and just let them slip. I wasn't sure.

B

If we didn't start them, it's okay to move them to twelve five.

C

B

Mean either way, it's probably finally moving with tofu, okay.

C

So I would say that I updated the issue board with the weights for twelve five for the new items and the items that are definitely slipping from twelve four.

B

So if I'm looking at just.

B

So the back end column for the twelve five release. Has everything in it? Yes,.

C

As of now, there's a few items that are in review and twelve for that I'm not sure about, but they're gonna be finishing to a four and then there's one item that I'm still not sure about. So if I wasn't sure about it, I left it in 12 for the things that I know are gonna slip like move to 12 I've already and there's a total of five item that might have to go to 12 six mystery.

B

I saw your comment on that yeah.

C

But so far it means everything that I know is gonna slip. Okay,.

B

So we're not over by that much at least on the back inside them just a couple and there's one: that's not we did it alone is.

C

That, technically me see which one it is yeah.

B

Oh, it's a community contribution. That's not! Oh.

C

Yeah that one and it's in the view, okay,.

B

Cool okay, so we're not actually that bad and it's step three moves, then we're a little bit under I.

C

Don't know it marks capacity, yet those I think my capacities, correct. Okay,.

D

Okay, something.

C

Is that everything in 12, for that's in review and verification limit, God personally right.

B

Okay, what about on the front end side, 100, yeah,.

A

So I'm I'm, currently going through the planning stage I'm a little behind, but I'll should have some news later today from what I took a look briefly on the board and I saw what's in there, it doesn't seem if we are over capacity. It doesn't seem like we're a lot, but I need to dive in to give you a proper feedback on that.

A

So I will update the issue later today at most tomorrow morning from my side, which will be your dawn so bye-bye tomorrow morning, when you wake up, we should have a concrete list of things that might not make it I don't have to move, but uh oh yeah, so by tomorrow morning, I should have that I only do I will only do the assignments on Friday I'm wondering how how's the kickoff being done. This milestone.

A

B

Like my kick-off, yes,.

A

B

Well, that started trying to figure out. What's gonna make it so it doesn't look like we have any like editor, because most of this is locked up and like that admin UI doesn't have anything, that's going to make it and to kick off.

A

hmm I'm so I'm talking about the call that you do the videos that sort of thing for 12/5 yeah I mean talking about typically start shipping yeah.

B

Typically, for that, we only talked about like direction items right. So that's like major.

E

B

That drive direction forward and because all of that is.

E

B

Admin UI there's nothing else. Okay, that is happening. The owner, yeah I mean there's, nothing else, that's happening.

B

There is a direction item. Okay,.

A

Okay, yeah I missed that part about the direction label. um Then then, yes, I'll, be I'll, be sending some feedback later today by tomorrow, I'm still in source goal and I'll be moving to editor after in then knowledge. So by tomorrow morning, I hope to have both three concluded. So, okay, just.

B

A

All I'll post through the issue.

B

Yeah and ping me and slack I'm off I was doing Friday.

A

B

So I'm off after today for the rest of this week and won't be back until Monday. So if there is anything, I need to look at or move around, like it's probably gonna, be next week before I get back to it. For.

A

Me, that's not really a big big deal because I'll only assign the ones that fit on Friday and if we just have to deal with the excess on Monday. That's fine for me from my side.

A

Okay, cool thanks.

B

That works for me on that one.

B

The next one was release post so for editor and I. Think again because of the admin UI, there's, not anything like Direction item, so I, don't think I'll have anything in the features further really expose for performance items. There was a bunch of search improvements and my understanding of performance items is that engineering managers add performance, notes to the release post.

C

So I need to write something up: yeah.

B

C

B

C

B

I thought I would add it here and then we could talk about it yeah. So it's ingénue and I think that's true and I. Don't know if Andre, if you've ever had to do that on the front. I.

A

Was gonna I was gonna, mention I've done this, like in the old old, a release post format. We would just have a section that would be for performance improvements. It would just like link them the issues so I don't know how it's like in a new format, because I've seen.

B

Some changes same.

A

B

Yeah I think, like the engineering managers get pinned and then they they add it all that way. So, yeah.

A

I was pinged. I got that ping. You should have it being two Darva ping.

E

A

The backend in the yeah so um Fabian pinged us, so it should be there. I'm gonna put the link.

C

A

Go I just added the link there to the duck, at least that's the thing I got so I. Guess that's where we'll be adding those performance improvements, okay,.

C

A

Should be added by tomorrow, though, so.

C

A

C

Okay, we can repeat sytem I, think I already said this, things are gonna slip. It's all documenting this front planning issue Kai. If you have any questions about why things are slipping, you can you can ask me now you can ask me later and Kai I know you had mentioned to me. You ever stopped to me being an issue about the audit. The users fried input, issue and Fran did document a lot of items that need to be fixed. I will be talking to Tim tomorrow to see how he wants to distribute the workload.

C

And did you have any questions about that.

C

You're on mute guy, not sure if you're talking.

A

So these are, these are about search right.

C

These are I, think yeah I think it's related to search I. Just it's there's coaching is that to be made across the codebase and.

E

D

Just searches, for instance, other stuff and.

C

They don't actually have owns, they don't have a home, so we didn't know who was supposed to do them since Fran identified them. I just had him assigned to the editor group for now and I will talk to him about how to distribute the changes all right. So we can move on to Marcus and.

F

This is just an FYI about the strange workflow you're doing for the step two of the administration UI, so we are using like a temporary branch or some mass. So basically they are mulching. Autoremote requests into this one I'm, not sure I. Think we've discussed this with Carly before I'm, not sure if you knew about this, but that just complicates like some of the issues like close them until everything's released. Just so, you know, I.

C

Like the idea of adding them to 12/5 as a wave zero so that we know they're still there and they're being tracked I, don't you know I'm assuming cars, okay with it, but you can bet it's enough. Isn't that.

F

Is his still on the cold, sweat.

C

B

F

Discussion I just.

B

Came back sorry, okay,.

F

So I just mentioned this thing about the temporary branch to be there for the step, two I'm, not sure, if you're aware of this yeah yeah, okay, so yeah, just to mention that they complicate some of the like become close to issues until the food minister. I responded.

B

To that, I was wondering if it makes sense to like close the work issues and then, let's create like a follow-up verification issue, because we're gonna have like very like otherwise you're gonna have to roll step two step, three step, four, all of them and just keep rolling them through each milestone, which is gonna, make like planning.

D

B

Little bit of a nightmare and like the work look harder so I wonder if we can just do like just dude. Let's just do like follow-up issues for verification and then like just create one master one and put like a task list in the issue. Description that, like links to the other issue and is like verification of this and then like put a person's name next to it and then like people, can just check that off or something at the end. I.

F

Figured that's a good idea, especially if it makes the planning for you easier and I think it will. So will you create the follow-up issue.

B

I can or if Darva, if you wanna, if you're able to create a follow-up issue.

C

So we're gonna close the issue then I think.

B

We should close the issues that represent the engineering effort that was done and create a new issue. That is an.

E

B

Issue, because these are supposed to stay open till you can verify, but we can't verify I think otherwise. We just end up taking all these issues and just moving them like to each milestone, which just doesn't make sense.

B

It'll, look like nothing ever nothing. We didn't do anything for like four milestones right like if we don't close the.

C

Wait just goes down, but yes, it's not obvious. Yeah.

E

I asked on our agenda: is this behind a feature flag because maybe I mean, if it is, maybe it makes sense? Having that feature flag, remove will be the last verification step.

F

So unfortunately, it's not than they already start the moving stuff around and yeah I guess it would be better if we use the feature flag from the beginning and then just duplicate the code and then remove the old code again, but it's too late for that, unfortunately, and just to make sure I understood correctly, so we create Vong over all this shoe for the verification and just list. The other issues right, I think.

B

So I think yeah I think one verification issue at the end and that way it's like either one or maybe all the engineers go back and look them like verify individual components.

E

Cuz, it's gonna.

B

Take front-end, there's gonna have to do some verification. Backends gonna have to do some verification right, because no one's gonna be able to see any of these features. Actually, all working together until kind of all of the steps and branches are all merged into one mega branch that has to have a merge request open to some reviewer and maintainer you're gonna be not thrilled, maybe I'm not sure cross that bridge when we get there. Okay,.

C

All right, kinda hot chef- you uh were on the call when I was talking about the audit. You can input audit results. That friend worked on. He created several issues and assign them in the editor, and you were asking about yeah.

B

I think we should asked him I think, let's see what Tim wants to do with him, because it's not it's a it's unreasonable to like put the expectation on us to deal with him all.

C

B

Think that's like a Tim should either decide or run that back up through the rest of engineer, introducer all.

C

Right, so that's the train tomorrow, okay,.

B

C

And the next item is me: so last meeting I talked about creating playlists for our meetings and then I went to the playlist and I noticed that there weren't a lot of teams with weekly update playlists in in the YouTube and filtered so I wasn't sure if we wanted to do that or not I.

A

Would vote yes and by default? Yes, but we can exclude specific episodes that we mentioned confidential things. Sometimes we discuss client stuff, which is not the case of this one I think so. In those cases we could just like publish, but if we do mention something that is critical, we just mentioned at the end. I don't publish this, so it should be a manual process, not automated that any of us could just like take the responsibility of uploading after this is compiled and recorded. So.

C

You don't think it'll be too noisy to have. We have what happily a lot of videos over time. You don't think that it's today, no.

A

It's actually the opposite so and actually that's sort of what they mentioned on the YouTube handbook pages and that the more you publish the more it's there and you can reference it. You can link to a particular discussion and having that available, will only promote easier communication and easier attendance and then having to go to Google Drive and get that, and it's just like easier experience, but also in that up.

A

It's not about the volume because, for example, plan is sharing that and only if you're looking for a particular episode or something will you look for it, but also it increases. It increases visibility of what we're discussing here and I think there's for our transparency value. That's just benefits. Well, we have to be mindful of the risks of confidentiality being breached. There. That's the only thing, I'd be concerned, but no I, don't think the noise would be a problem. Do.

C

You think the episode should be titled, something so that you know yeah.

A

Just a week, okay yeah, it can be it's a plan, is doing just plan weekly team meeting. So as long as we keep it consistent, it should be fine. We can, we can add the date to the title, but that's on the date itself, so I wouldn't own sweat. It's just like fire-and-forget, it's available just just check if we should fire it or not before firing any other thoughts that that's just my view.

B

B

I was checking this one to actually see if the release board had any confidential issues in it.

C

Sometimes we could have confidential conversations, not necessarily issues and.

A

We should have them, we shouldn't stop having them, because it's published, we just should just stop publishing in that case yeah, so yeah on that. In that case, we can look at the recording because Kai shared the screen a little bit, and if there are any confidential issues, what we can do is just publish it private and you have to be with get lemon filter account to see it or not, publish it at all. It depends on what's exposed yeah.

B

C

Do you think we should just publish it and publish it private instead of not publishing it all just so that we have one place that we go to and so that the Google Drive yeah.

B

That's fine when they're calm when there's stuff, that's confidential, yeah there's nothing confidential in this one. So it doesn't matter.

C

B

D

B

Thanks agree: they.

A