GitLab Digital Experience, 1 Dec 2022

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Digital Experience Team Retro - Dec 1, 2022

Description

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

A

Yeah, okay, hi. Everyone welcome to digital experience. uh Retro meeting uh today is Thursday December 1st and we're going to go over uh retrospective of the last iteration and things to things that went well and things to bring up and things to improve. On uh first thing for things to bring up is John.

B

Thank you Laura. um Well, uh for this iteration, we are happy to announce that we run our first change. Look job. It went really good right now we have some results. I have I want to. Thank you all the team for for uh competing with the conventional commits. That was great because we had results.

B

Let me show you so this is our first change look file uh with some experimentation that we did on this iteration um and we found some things that can be improved if we want to keep up with the experimentation before uh deciding if we want to make it work on various experience or slippers or navigation or the tree of them. um So the first thing that that I found is that um when you do a measure request- and you merge that measure request into main, there are two commits two different comments.

B

One is the squashing commit that, let's say is this one? Let me highlight this one and the mesh um the merge commit. That is this other one. So what happened here is that we use conventional commit in both messages and the analyzer detected, both and and thought that were two different commits, but they are the same. It's just a thing from GitHub.

B

uh One recommended solution is that we can use um these conventional commit messages only in the merge commit message: I think that can be um confusing, but when you are reviewing a merged in a page, you can see two different uh text boxes, uh one for the commit message and one for this question only apply a conventional Community to one of them. That would be. That is the solution for this problem.

B

Another thing that um that I detected is um this: all these um commits are marked as features, but if you go and see, let's see this this one.

B

So if you want to see it's only a Content change, so this is more like a document type or core short type. So this is because our feature is a big thing that maybe a new page or a new component or a big functionality, and in this case it's not relevant for the for the change log file. So, in this case it it can be document or refactor or or sure sorry for whatever I cannot pronunciate it or or short.

B

um So that's why um how you mentioned why this commit didn't get through the change log file so and and it's because it was a short commit so for the for the job it it is not relevant for the job is only relevant, bug, fixes, features or breaking changes, and we have. We are right now on version 1.0.0 and because the biggest change was a feature, it increased the major version and not the patch version.

B

If there aren't any feature, it will increase the past version, the last one and that's it that's it for the explanation. Thank you very much again for foreign.

B

This one is uh if there are no questions, Laura.

A

Thank you uh yeah, uh and thanks for showing that um uh for things that uh went well, uh yes, so um we're finishing up, I guess the major league hacking, Fellowship cohort um I, think next week um and Megan mentioned this in a meeting earlier.

A

um All the great work that's been done, a lot of improvements to slippers um I can let someone else you know discuss all of that, because I I haven't been involved, but thank you so much to everyone who was involved. I know there was a lot of design, lift I, think Barker was heavily involved, but especially Megan was uh I saw her everywhere and all those commits. So thank you so much Megan for doing that.

A

um I have uh the next one as well, which is Miguel's mustache. It's extremely good um and has brought me a lot of Joy today. uh If you look at this picture from our Sprint meeting, you literally can't tell which one is Miguel. We are all the same. This is all.

C

A

It is incredible, we don't know if it's a movember thing, um but we hope it stays.

A

It's permanent, oh man, it's so good, okay, uh very good, wow! It's a really big mustache! um Thank you, Nathan, for all your help with the slippers um I've never published an npm package before I. Don't know how I made it this long as a developer, but thanks for your guidance through that um it was not as scary as I thought. Even though I broke it all right. You have the next one.

C

You didn't break it, I, don't know what happened. I've, never seen that before it was like everything.

C

I, don't know, just anomaly pretend it never happened, but uh yeah no problem and thanks for all the I wanted to mention earlier, but I didn't want to interrupt the all the mlh I can't really appreciate mlhf, that's what it is: a lot of work and organizing all the issues and everything so much appreciated um and thank you Lauren uh for fastly access and manually deleting the whatever that one key or two keys I guess it was in the vastly redirect dictionary because going through the API was a nightmare. So thank you.

C

Thanks for having the keys and doing it, Yeah.

D

Couple double thanks uh also to you Nathan, for helping us work through that it's scary longing into fastly and having the ability to just blow up her whole site and just make it disappear, um and so that is a double thanks to David Smith, who hopped on the call all soon you know able to ask him some questions of like. Can we just set a whole new fastly configuration and can we purge the cash like I'm, not really sure so that was cool.

C

That's a good learning experience for us too, and not to be as scared as fastly or we still will be. But it's nice to know. We can do like a couple things I think I have the next one. Oh yeah.

B

C

Like something that we're doing poorly on I, just thought with December, there's, probably gonna, be a lot of PTO. We're, probably not gonna, have a lot of like these lightning strike. Pages, it's probably gonna, be quieter. So I thought it might be a good opportunity for us to work on like I.

D

C

Know the projects that we want to work on or the dev tools we wanted to create, and so just like a I, don't know like an open, invite a kind of thing to let's build some cool stuff, that'll help us yeah, Lauren I, don't know if you want to vocalize that.

D

Idol, if you're working on stuff, maybe you've crushed all your your stuff, you're assigned for the iteration, and um you don't have anything to work on please by all means work on our repository help.

D

um You are the experts. You are working with the code base in and out. Y'all have great ideas of like what's gonna make it run better, so um feel free to just spin up an issue and get an MR started. um You should be able to contact shift away from that work quickly if needed. So let's say something comes in and we have to to pull you back.

D

um You know that's priority, but um we just wanna. Let you all know that you know you can do that.

D

And then I have the second one, um let's start organizing a way to um give our feedback on the changelog process. I mean that that's a huge change for us and how we make our commits um and I see that John put a link in the chat that'll drop in on there um yeah. Let's run our feedback on this current on this first one, let's you know, drop it in there, um I think there's you know, there's things we still need to improve on.

D

It's not perfect, um we're all learning so by all means, think about it. Organize your thoughts and please drop your your threads in there.

A

All right and with that I think we're all done. uh Thank you so much and we will see you next time.