GitLab Digital Experience, 16 Jun 2022

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Digital Experience Retro - June 16, 2022

Description

https://about.gitlab.com/handbook/marketing/digital-experience/

A

Hello, this is digital experience team, it's our retro for iteration cycle june 6 through june 17th, and uh I'm gonna. Kick it off with some things that went really well for this one. um I just want to say great job dennis carey and laura for analyzing swift type. We've got some great things to action as a result um like more analytics across the domains about and gitlab.com bounce rate reduction and some um cool a b test ideas, uh so just awesome job and another great job, entire team.

A

uh We're making really significant progress on one of our okrs to continue depreciating old pages, and that was a whole um team effort across the groups just loved, seeing that I'll pass it over with justin.

B

Yep I'm saying great work gabby on that scroll animation. For why gitlab looks amazing, um I know more people than tyler helped her out. I don't. I know jess tina, a bunch of people helped her out but, like it looks amazing, so awesome um and then I was gonna, say lv started on monday, which is the very last minute like I had to because of some issues with uh contracts. I didn't get the it issue in until actual monday.

B

So I t I want to say they're not on this, but they rocked it out to get him on there. He will be.

C

B

Showing up in our sprint planning starting next week, oh and he's on the conversion.

A

C

A

B

A

Okay I'll go. I have uh one thing um to work on, and this was uh kind of is my fault.

A

um I I took on an uh issue to update the open graph images um for the site and kind of touch them up, but that ended up um requiring our uh product designers to to do some work tina, so that ended up with work on her iteration that wasn't planned, and that um is something that, like I need to be cognizant of when picking up issues in the future, and I think the whole team as well, that you know we all work in planned iterations and if issues we're taking on is requiring our other team members to take on additional work to check in on that.

A

uh Tyler action item.

D

Yeah I just wanted to flag this um so megan and I we we don't, have a lot of call uh for like unit testing in the buyer, experience repository usually um but uh meg, and I stumbled on a good use case for it with the calculator uh it's you know just screaming, for unit tests, um and so we need to get those set up.

D

uh Megan has written some, but the um I didn't want to block on this, because the um uh just enforces uh like minimum node versions that meet like the most up-to-date like minor and patch versions, which we don't have so um megan, put together an issue to add uh jest into the buyer experience repository. uh We will have to upgrade node just to latest 16. Basically, and so I wanted to flag this here. um Embarker. Thank you for asking for the links. There's issue links there.

D

um If you, if there's any reason that you don't want us to move to the um most current node version, uh let us know in there, uh but if we don't hear by the start of next week, then we'll move forward with it, uh and so just as a heads up like folks will probably see at some point.

D

uh You'll probably get a little yarn error and it'll say like hey like you know, your node version is incorrect or well, or things will break silently and it'll, be weird, uh so we'll just yeah, we'll slack folks and and point people to the mr and stuff. So um just a heads up or you know, tell us if there's a blocker, I can't imagine that there is anything blocking. um But if you know just soliciting feedback on that, so uh that'll get started next week.

E

Sorry, I'm trying to write this in two places and I typed it wrong. uh We should bump then slippers and nav just so. We don't have to deal with different note versions.

D

Yeah for sure I will probably defer to the people who, like uh maintain those repositories to do that at their leisure, because it won't matte like if we bump uh buyer experience it like it won't matter between them, because both of those get compiled anyways and like node doesn't, you know, come along for the ride, um but if you want to do it sort of in tandem, uh you know if you want to subscribe to the issue or uh keep an eye out for the mr and sort of do the same thing yeah, but I'm not going to let that block this so yeah.

D

Let's do that in parallel. Please.

E

Yeah, I can even do it after it's fine. I just don't want to have to change node versions. Whatever I switch well, I guess I have containers, but I would.

D

Just say: do you well yeah one you're, mr container over here and two you should have a uh version manager do that, for you, yeah still still work.

E

But you're right, I'm gonna touch container life recommend everyone join the container like.

A

I just put one on there: we can work on in the issue comes up with that uh right. Anything else for this retro team.

D

uh Lauren, I don't wanna upgrade node on www, because we'll have to upgrade the images and the pipeline and that's a let's. So so not there yeah yeah.

C

A

But just not that one just.

D

Not that one, that's fine, we don't that's. That's not. This is not really.

C

Us anymore, I just like.

D

Just like that's not no, no one bark up that tree. It's it's not.

C

Okay, barker will lay that one down and.

D

We're not we're not upgrading, I don't know who wrote the ruby version there, we're not doing it. No, it's it's.

C

It's where it is.

D

C

Oh man, cool good, sounds great uh all right. Let's.