GitLab Package Group, 4 Jun 2019

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Weekly Package Meeting 06-04-19

Description

Weekly Package team meeting.

A

Okay, we are recording this is our weekly team package meeting, where we talk about upcoming deliverables, blockers and anything else that, as a team as a product and engineering team that we need to be aware of so I'm gonna share my screen now and.

A

I have a the agenda for today, June 4th John I. Think you had the first item.

B

Thanks Tim yep I just wanted to welcome Nick Kipling who's, not in attendance today is our first front-end engineer to the package team, so welcome Nick and then my next point is Nick. Isn't at this meeting, because it's even 8 o'clock for him. So I was wondering if we should move this up in the day or if we can adjust things I'm sure, there's other times I was to consider, but if we could adjust that possibly said that Nick can attend.

B

I don't want to ask him to attend at 8 o'clock and then I know some folks do like an AIPAC meeting but I'm not sure if that's with our smaller team size, not sure if it's beneficial, so I just wanted to bring that up for debate. I. Think wasn't me: what's the APEC meeting.

C

There's a big yeah.

B

Thank you, wow that was like round took my tongue, Thank You, Daniel, hey.

A

Think earnest yeah.

B

I was thinking a secretive process and change for some reason: I, don't know why that's not right! That's not right at all yep way off engineering mindset.

A

All day, if we moved it up to 9 a.m. or or it would allow us to, it would be like 5 o'clock, it's time then or yeah 5 o'clock. It's time, I think we can accommodate him, but if we need to change it in the future to be asynchronous I'm. Ok with that as well.

A

Ok, I'll move I'll find a time that works and make sure that aligns with everyone's schedule. Yeah.

D

And you might want to do the weekly retro as well and well.

A

A

Cool cool Thanks, so next up just to go quickly through twelve point, oh and I think there's only one thing that we have to talk about here, which is this issue assigned to Jason of changing updating the permissions for the container registry. Api is any any blockers or concerns about launching this one yeah that one that one's probably gonna slip. We talked about that in our release meeting this week. I guess this morning, and this is he he said he hasn't started on it. Yet. Okay, so he's been kind of swamped with feature flag work.

A

So this is you know, as we go into 12 one I'm.

A

Maintaining the priorities is the same so like this is the next thing that he'll work on before the other things that he's got four twelve on, so it's kinda, it's just gonna slip, I'm, not sure how big of a task it is I, don't know that he's dug into it enough to just say: if it's you know a day or a week, kind of a thing: okay, he's not the one that would work on the conan integration right. Looking at looking at 12:1, this is right. That's crass! That's gonna work on that!

A

Okay and I I do think. That's a pretty big big one. I put a comment in there on that issue about like the first step, is just defining the API, and that is an investigation itself so, depending on what what that turns up like once that is done, I think the implementation will be fairly straightforward, most likely, but we just don't even have an idea of what the API looks like yet: okay, okay yeah.

A

Let me know if I can help I know: we've been going back and forth in the issue with with the users a little bit on what metadata they would like to track and see, and so it seems like it's good conversation happening there. I just want to make sure we keep having it and we.

C

A

Okay, if there's delays but I just want to make sure we're talking about them and communicating them. Okay, yep jumping back to 12 point. Oh, this feature is being worked on by the delivery team. This is a part of the process to add, storage, tracking and optimization for package features they're working on first, because some of the costs related to the container registry. So this is in progress and I believe on on time.

D

Steve, that's a probably a good one for you to keep track of as well as far as updating for metrics that we're going to be looking at later. So you might want to just sort of add a watch on that and go check what those Emma's look like, as you get a little bit of time to look around cool thanks. Yeah.

A

And I could send you the epic I'll flock you the epic for this as well. It has a lot of details in there.

A

This one is in progress is actually one of our support. Engineers is took an interest in contributing to our NPM project and so she's been working on this NPM template with me. I have a meeting later with her today to review the work that she's done. Daniel. We were in that meeting as well I think just so I can get someone who actually has NPM up and running to offer feedback, but I think we can hopefully get this done and merge for for twelve-point. Oh and selfishly I would just announce that I.

A

This has been merged a maven template. So this is my first contribution to the community edition got approved. Thank you, I'm, officially a contributor, so nice. It feels good. You know, even if it wasn't a very tiny change, I'm proud to have it in their speech and the authentication. This is in progress. I have to sync with Dimitri and see if this is going out in 1200 or 12:00 1:00 I'll reach out to him. In check the next item on the agenda item was that just got a quick review of 12:1.

A

Just thank you, everyone for adding the deliverable tags and assigning them appropriately. That was super helpful and able to update the kickoff document for our meeting on Monday. So we have Conan. We mentioned this being maybe a little bit bigger we're following up on that Steve. This is your first official issue. They publish NPM package from subgroup and project, not sure if you had a chance to look at it yet or if you had any questions or concerns just.

E

Started I've read through it and then I've started to peek through the project to see you know where all that code lives and starts to digest, yeah how everything works. Okay,.

A

Yeah, let me let me know, I know it's I just want to make sure the issue is clear and if you have any questions, just I'm happy to dive in or clarify something in the issue as well sure.

A

Next are is a front-end issue. The docker registry date not accurate, so this is picked up by Nick um seems straightforward. Note, no concerns.

B

Yeah none so far, but if we run into anything okay.

A

It's another Demetri tag. We have him for twelve one he's still working on the dependency proxy, so this he'll be setting it to enable it by default, for, for a group, they'll still be limited to users that are using Puma, not unicorn, but at least it'll be enabled for those users by default.

A

This issues been worked on by the secured team. It's a front-end change and actually no, this one's being worked on by Nick. Sorry good run one. So this is changing the error page for if you have special characters- and this is the first step in addressing this issue- and next next release will address it with a JavaScript error during those key moments. I.

A

Mentioned the documentation, there's some inconsistency that was pointed out by one of our customers and Axel is gonna work on this and for 12-1 and clarifying that.

A

This is the issue that's being worked on by the security team, so adding in a modal four-four when you delete an image or a tag. It looks like this is oscillated 4, 4, 12 1 and no problems that I know of, and then this last issue I don't see anyone assigned to it. But I think this is a supposed to be assigned to Steve. Yep. Ok should I do that now. Yes,.

D

A

There you are, and it has a deliverable tag- ok cool, alright. That was it for the the review of thinking that don't make sense than any questions or anything else worth talking about on the upcoming milestones.

D

Yeah I think just to just want to be a hundred percent clear with with everyone and Steve's just to set some expectations that these we know. These are your first issues is a lot to learn and there's that'll take care of the long it takes. So you know, if you have any questions you need support or whatever, then you know just know that everyone's here to help, if you need help.

E

Cool I was kind of curious if I wanted to reach out to any other, like back-end engineers, so, like just ask questions about how things work or, if I'm, not necessarily following various parts of the projects, is there a good group or you know, developer in particular, that would be worth work or even slack channel that's worth reaching out. Oh yeah,.

D

You've got Jason, who should be first point of call because you're sort of onboarding buddy if Jason's not available the backend channel, is something you're already in, because I tried that that you had you to that twice so I know you're in there for sure, and that might be worth asking and then, depending on which area the code base. There's the sort of domain expert for that area that we can make sure you're in touch with Darby. Did you have other thoughts.

A

Nothing nothing comes to mind right now. I think there is there's a slack channel called questions which is like pretty active and people. People tend to jump in there, pretty quick, so like setup questions or things like that. There's also like a development channel but I'm, not I, haven't, haven't watched that one in a while. So I'm not sure how active that one is relevant.

D

Channels active, but it's full of like this thing, got done: merged Emma's.

A

It's more like yeah, that's pretty noisy, okay, yeah, that's probably not a good one! Then um I mean you could probably, if you're, not in the G release channel. You can jump on that one too, and that, like that I'll get out. There's.

C

A

Pretty decent group in there, and at least like some of the other back end engineers from release, can can help with things.

E

Allowed you to do that now: cool yeah. That gives me plenty of avenues when I start running into anything. Oh.

A

That's great the next item we have I think Daniel. Did you end this monthly or other cadence for larger the larger team yeah.

D

I guess I'd sort of briefly mentioned this to Dobby, but I was thinking about the idea of having a sort of a brought a meeting with QA and UX front-end, and obviously yourself I've.

D

Something I'd like to do is just sort of make sure all in sync. We could do this around the releases, the monthly releases, but my main reasoning for that is, but at least the intent is there. You know to have the team sort of be in regular communication as necessary. Just because we're not going to always have people in these meetings. People can't necessarily attend every single one.

D

So having a conversation somewhat regularly about where we're going and what's going on, might be helpful, I think the reason I'm I'm personally interested is because I'm interested to see what QA is thinking about and what UX is thinking about, whether we have a person who's actually assigned to a team or not. You know we won't always have someone in, although the rest of the regular meetings so happy to give it a shot or not. People don't think it'll be helpful.

C

What do you guys think.

A

Are you John or Darby? Are you guys doing something like that for release.

B

Yeah we have the unreleased same verify the meetings. Our weekly meetings include everybody. That's involved, there's at least one UX person there typically and then yeah so.

A

Maybe it's just making sure, because we right now we have engineering, we don't. We have Valerie added to this meeting, um but it sounds like we're just missing QA, so we need to figure out who our QA engineer is and then add them to this meeting and I I, don't think for a release. We have on okay because everything is perfect. Yeah.

C

And there's no reason to kill any omissions. Yeah.

A

C

That was implied.

C

B

Look at her said that should have said that to our.

A

A

Okay, I'll see if I could track down who are. If we have someone for QA and if at least we can have a solid answer and if that's the case or not yeah,.

D

It might be a perotta, they might just be a someone who, like oversees the whole CIC, you know, but okay and I said sort of I was thinking monthly I. Look you know by weekly or bimonthly. I should sign up bi-weekly, um depending on how you look at it just because I know that a lot of people a lot of these people, like John, for example, has a lot of teams that he's supporting and then, if he's in meetings for each of those teams once a week, then it's just gonna be a lot of overload.

D

So I'm like just trying to be thoughtful about when that would be useful more than some particular you know, regular cadence.

A

Personally, I like the idea of having this weekly meeting, even though sometimes it sounds like we're repeating stuff but I do like the idea of having some cadence, where everyone sort of has the opportunity to give a demo and talk about what they're working on and what they're excited about, and maybe there's a maybe that's the there's like a monthly retro retro or a post release retro, where we could talk about that stuff, because I'm anxious to hear about that from from you guys and from our eventual UX and QA team as well.

A

Maybe that's how we can incorporate something like that.

D

Yeah, okay! Well, let's, let's have a think about. We have a sort of a an async retro process that we have for engineering already and I. Think let me have a think about what it is that I'm trying to achieve whether a retro sort of meets that need cool, okay,.

A

C

A

Next, two items are Darby.

A

Yeah, so I just wanted to call out. This is a change in the release process. I think everyone probably got emails about this, but just making sure to like and I over communicate this the deploys to Caleb comm are starting I.

A

Guess like this week next week, pretty soon they're just going to start happening on a weekly basis and there's like this doc describes the flow and essentially like, what's going to happen, is we're going to do more continuous deployment to calm and then we're still going to basically cut a release around the 20th for a release on the 22nd. So this is.

A

This is kind of a change of the process like the feature free is date on the seventh is going to go away, so we won't have quite the the mad rush to merge everything by the seventh that we that we have had.

A

So this is good to read through there's two issues. One is this one that describes the process and the other one is a bit more about the implementation and then, like some, some frequently asked questions so be sure to read. Through these, there they're worth takin ten minutes to to go over, and if you have questions you can ask me, I might not know the answer, but I can probably point you in the right direction. If I, don't.

A

Okay, that's really helpful. I'll read through these all right anything else on our agenda. No welcome, welcome, Nick, far far away and we'll change the timing of these meetings. So we can hopefully all tend next time all right thanks. Everyone talk.

E

To you later, thank you. Fine.

A