GitLab Digital Experience, 13 Jan 2022

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Digital Experience Retro Video - Jan 13, 2022

Description

Digital Experience Handbook Page: https://about.gitlab.com/handbook/marketing/inbound-marketing/digital-experience/

A

Hi everyone uh welcome to the digital experience team retrospective. I will go over things that went well and things to improve on the last two weeks. Sprint today is thursday january 13th and first for things that went well. uh Tyler has the first point.

A

And tyler is muted.

B

I clicked it. I swear um now that we landed all of the google tag manager, stuff or like now that we have landed a substantial amount of gtm work in gitlab.com.

B

um Iterations are a lot easier because there was a h. There was a big upfront, lift where, like a bunch of stuff, had to shift at once to make things happen, um and now we're sort of like integrated in the workflow and also like there's no more conversation about like. Should there be google tag manager because hello, it is here, um and the iterations can also be smaller, where it's like, oh, like we already do it this way.

B

So, like we're doing it the same way over here, because we like need to grab a page or whatever so um yeah.

C

It's just been.

D

B

Nice, so this last, like all of the gtm stuff that I landed, this iteration was like way smoother because they were like smaller changes that were more isolated and, like I just didn't, have to get into a whole thing about, like you know, should we even do this because, like it's already been done, so you know that's uh yeah, just great so uh barker you are up next.

E

Yeah this um this iteration cycle, I started blocking my time out almost like the day before I'll block it all out and I'm really diligent about if I'm working on product code, it's like a three hour block and I close all my other ides and I close down slack and like I just work on that and um same for, like mr reviews and lunch, and all that- and it's really helped me do all that context shifting.

E

um So it was a lot more productive, just cool. um I have the next one: um the migration to the buyer experience repos, going awesome kind of an fyi I for the next cycle. I want to switch over to migrating some key pages like the free trial sales demo and install, are y'all ready for that yeah all right uh next nathan.

F

Okay, just a quick one, just wanna say thanks to tyler.

F

I know we talked about this in like the two-day off-site about these, like random calls and missing kind of like whiteboard or blackboardian when you're in the office, and I think I called them like four or five times so I don't even know how many times it was, but even like five minutes is so helpful because sometimes you're so far down a hole, and you just need somebody to look at it from like the top level view and uh yeah thanks a lot um and then yeah.

F

I guess I'll shout out to megan as well for probably the quickest, mr or code to production since joining. I think it was like four days or something I don't even know what it was, but it was quick, so uh yeah shout out shout out to that, but I think that's it for things that went well. We want to move on to things from pre one.

E

All right, I got the first one um I'd like to improve on our get commit message: guidelines there's a couple, mrs that came through with you know, over 30 commits um I do it. It happens, we're moving fast, but um I don't want to merge 30 commits into our commit history. I want to want it to be like one or two.

E

We don't have a process yet for it product does so. um I think that's something we can work on together.

B

I think we just grab whatever danger job. They have is what I wrote here. So that's all, and we can also use that for reviewer roulette.

E

Oh yeah and I put a action item from that. um I've had this discussion with michael and he's 100 supportive of it, so I'm going to create an issue for it and we'll get it triaged so that we can build it in there.

B

um The next point on this is just like: I don't think we should do this. I don't think we should target www.getlab.com, I'm having I started talking there like it would be such a mess to enforce. So many people contribute to that who are not like get people like who don't you know what a commit message means um and javi. I good thought on squash emerge, but I think we'd still have to educate a lot of people about, like writing. Good titles for their.

B

Mrs, because that's what ends up in there like I just like, I think we just gotta. Let that thing stay a mess because there's you have to corral everybody into that and like you're, just going to slow things down for something that, like folks, like will not think, is important.

A

I didn't make a point about this, but to add on there's a lot of the when people edit with the ide it automatically makes a commit message. That's like edited file, slash slide, slash record whatever, like the file path or whatever, and that's also what the mr title might be. I can't recall, but yeah policing that is impossible.

E

Yeah, you know we might have to consider that when implementing danger bot into the buyer experience repo, because all our content is very nicely organized into yaml file- and I first see our partners using the the ide to edit that.

B

I think it'll be a lot easier, it'll be there will be less content, and if we do this sooner than later, when people learn about the new place to edit stuff, they will start with the understanding that that, like restriction, is in place. I my fear, for the existing www repository is that there are many people who have years of bad habits and, like I don't want to fight people's years of bad habits on an existing code base right so like.

B

I think that, if we, I think, if we do this soon, we can like handle the web ide stuff, and we can like do a better job, educating a smaller amount of people who want to edit a smaller amount of content in the buyer. Experience repository.

E

I'm going to move on in the next one I am going to boot and mr for creating a handbook page about our buyer experience repository. I've had a couple couple: people reach out and they're like whoa where'd, my content go well. How do I update it, and so it's time we gotta get that if you have any thoughts on like what should be on there before. I start, please add it to the issue and then I will tag y'all for collaborating on that. Mr absolutely.

E

A

uh Yeah, we spoke about this briefly before uh recording, but um going over retrospectives in a formal manner like reporting um and going over some of the points, because we have a few retro retrospectives open for slippers, one for okr planning and I don't know if that's a value or if those should be async um yeah see. Parker has a point. There.

E

Yeah, I'm I'm for it. Let's do it and let's record it.

A

Yeah cool, so that's made its way into the action item. So I'll do that uh and then matteo is the next point.

G

Okay, um so I was working a bunch of pages that had similar templates so with the intention of saving time, I created a chain of merge requests with which depended on one another and that ended up being just a mess to to handle and to review. I can imagine um so yeah lost some time with that. I was thinking, maybe for the next time. Something like this happens. I could create just one merch quest for all the pages that share the same template.

G

It would take more time to go out to that merchandise, because all pages would need to be complete, but it would be much easier to handle. I believe.

E

um Okay, I will click I've run into this in the past before it was a result of just moving too fast. um Sometimes it works sometimes didn't it learn to get a little bit more. um For some of these, I kind of like having the like one page. Migration. That's already has a sister, mr together.

E

If we want to start combining those to more than one page at a time, I might want to set some guidelines around there, like no more than four, because it will make reviewing it a little harder, but it's up to us we can. We can set that. However, we want.

C

There are some times when um it depends on someone else's, mr, so there are, there are some required changes and someone else is already working on that, so it doesn't work to to create both uh uh two two similar uh components: different components, so it's better to wait for for for another one, um but in the end it's still dependent on on some other pages. Someone else, mr.

A

I think, if we're good I'll move on um in our actually I'm going to let tyler vocalize his next, because it's the same point- and I think he put it more eloquently. But I'm pleased.

B

You beat me to it, though, but um uh I was gonna say uh we heard this a bunch in the red, yellow green check-ins, before the recording um a lot of people shared that having the off-site right after a long break was more challenging than it needed to be.

B

um I think this is really just a risk for like this, like the whatever we do right after the holiday breaks, and perhaps like next year, like let's take a couple days to get back up to speed from the break um or, if there's another, like big planning meeting that's coming up after I know some larger holiday weekend or something uh maybe we just like like no cold starts on the big planning meetings, I think, is the big thing, because um it sounds like a lot of folks struggled with that, so I'm just something to improve on like long term and yeah whenever it comes up.

A

Yeah, I I agree, I think, you're right. It's probably a rare occasion. um The.

B

Next one will be in, like you know, march or something you know like I don't know. Maybe people are recovering from mardi gras and we you know, don't do it right afterwards, but.

E

Oh man, that's right spring break. We gotta go wild.

A

Cool, uh so we have some action items there. I don't know if we want to go over those. um I know that mine has been mentioned, but uh yeah parker. Do you want to say.

E

Yeah, I'm going to create an issue for um building the reviewer roulette and danger bot and the buyer experience repository so scope that out and get it triaged.

A

Laura yeah, I have uh scheduling those um sync meetings. I might leave the slippers one to hobby to do uh the lead on on that one, and I could schedule a meeting for okr planning. um There isn't a lot of chatter in that issue, yet I think just made some some points but feel free to add to that. Okay, our planning issue as well um and then next tyler.

B

Who is mike, the action item is who is the dri on the p1 plus p2 analytics recommendations? Epic, oh yeah is.

E

B

You are okay, yeah,.

E

B

You I I wanted to mention michael, had posted in slack, and I thought we should give him an answer since we're all talking here about um what the status is either. If it's ready to be closed, I don't think so and if not um what's outstanding and what's the plan on it.

E

Yeah I'll have to look get up today. We're almost almost done.

B

Cool, I will slack him just so. He knows in that thread.

A

And then javi's adding one now.

D

Yeah also, I have I have the linter tech that working group exploration and then add items to slippers, retro agenda.

A

So cool and I think that's it unless anyone has any closing thoughts, otherwise I'll stop the recording all right. Thank you so much everyone.