 OK, I think we'll get started. There aren't many of us, but we may as well get things going. So this is recorded as well. So if anybody wants to watch that couldn't make it, I will be posting this in the GitLabbers or NewLabbers channel tomorrow. So hello everyone and welcome to day two of get going at GitLab. I am Abby and I'm part of the people operations team at GitLab. And I'd like to run through mainly I'll be talking running through some parts of the handbook and also looking at Expensify and how to submit expenses and also what to do if you're a contractor and you need to submit an invoice so we can play you, which of course is very, very important. And then Ashton's going to cover how to add yourself to the team page and also some other bits and pieces with Google. And of course, if anybody has any questions, anything they want to ask either myself or Ashton, please go ahead. This is not meant to be a big formal scary orientation call. This is meant to be for you to help you. So if we can answer any questions that you have, just wave at me or unmute yourself and ask away. So I will actually ask if anybody does have any questions because you've been at GitLab for a whole 24 hours. So maybe a few things that have come up that we can help you with at this point. If not, I will just jump straight into it. Silence means no. Silence means go. Okay, cool. So let me just share my screen. Okay, so everybody can see this. Yeah, cool. So I wanted to start off by talking about the GitLab values before we go too much into the handbook. I think everybody will be familiar with the GitLab values. I know they're asked, people are asked about the values as part of the hiring process. And I thought it would be good to just mention them as part of this call. So we have six values currently. And together, they make up the word credit. And I think you can read there. I won't go through this in too much detail, but these are really, really, really important. And they underpin everything at GitLab. No matter what job you're in, no matter what you're working on, it's always important to have the values in your mind when you're thinking about talking to a customer or talking to a GitVabber or talking to someone externally. They really, really are absolutely crucial. And there's a couple of things I wanted to point out. One thing is this hierarchy, which is something that was added fairly recently. Because sometimes when we talk about values, there are some of the values like transparency, for example, that can be difficult to do in terms of if we have a security issue and we need to be transparent about that and tell everybody what's happened and what the problem was. But then we might run into other things that might jeopardize our users and things like that. And it's important to bear that in mind. I think things that I'm always conscious of whenever I'm doing anything is to iterate. Iteration is a huge one for me personally, and also being transparent in the job that I do. Traditionally, people operations is very closed and not open at all. And I can absolutely guarantee that that's not the case here. We are very open and very transparent about how we work. And also very, very iterative. And this whole get going at GitLab is very, very much an iterative approach. But it can take some time to get used to that. And I think this page really deserves your attention, certainly in the first week. We don't expect everybody to memorise this page to know the values inside and out. But it is a good place to start with. If you want to understand the lifeblood of GitLab, it would be good to start with this page. And then I want to show you the handbook. We have over a thousand pages of text, which is a lot. And it can be quite overwhelming, particularly if you're new and you start reading it and you think, oh, there's no way I'm going to remember any of this. That is absolutely fine. I don't know it. No one at the company knows the handbook inside and out. That's fine. Don't worry about it. It is designed to be a living, breathing document. And that means it can be changed. And everybody can contribute to this, not just people at GitLab. And I have an example of this. Actually, somebody has done a merge request, which I've got it open here. They're actually going through and making changes to it. And this person isn't somebody who works at GitLab. This is somebody who's just seen something and thought, I'm going to make change. And that's exactly what we want. That's the kind of thing that the handbook is based on. It is everybody can contribute. It's not meant to be a set of rules and regulations and things like that. It's up to every single person to make it better, to change it, to enhance it. So please, please, please, if you see something that you think that doesn't look right, you can create an issue or you can just go straight ahead, make a merge request, assign it to anybody, me, Ashton, CID, CEO, and, you know, we'll merge it. It's as simple as that. So I just wanted to make that clear because sometimes when people think of handbook, they might think of the traditional handbook that can't be touched. That is certainly not the case at GitLab. So I won't go through all of this, but just I've picked out a couple of key things. You can actually read a bit more about how to use the handbook on this page. And it talks about how it's everybody's job to keep it updated, to communicate it, why we do it this way, because reading is much faster. It's asynchronous. You can easily point people to links in the handbook as well. That doesn't mean that if you ask me a question and I say to you, oh, that's in the handbook, here's the link. It doesn't mean you've got it wrong or that I think you're stupid. It's just I'm trying to help you by sharing that knowledge. So don't worry if you do make a change and you think, well, I don't know if it's in the handbook already. Just do it. Just do it. Don't be scared. And we want everybody to keep making changes to it because it is part of how we work at GitLab. So everybody who is at GitLab is always thinking, is this in the handbook? Handbook first. That's absolutely key. If you want to make any changes or you've got something you want to communicate, put it in the handbook first. Don't put it in a Google Doc. Get it in the handbook. And then you can announce it on the team call. And you've already been to a team call. So you've seen what that's like. It's very, very easy to do. So I would encourage you to also take a look at this page if you haven't already. Any questions on that so far? Cool. Next page I thought would be really useful is the tools and tips page. And I should also mention, if you want to look for anything in the handbook, you can just type it in the search bar here and it should come up. And this page, I think, is so, so useful. It gives you a quick overview of all the different tools that we use and how to use them. And you can just have a quick look through and pick anything. You've probably got most things set up already, but if you haven't, this is the place to come. And I'll just do a search for people operations. Look at that. There's a whole page on people operations. So this is another area that I think certainly in your first week, most teams usually have a handbook page about their team, who the people are in the team, what they do, any kind of workflows or processes that they have for the team that they're in. And people operations is no different. And certainly during onboarding, you may want to come to this page to look for specific things or just to find out who to speak to or who to ask if you have a question on benefits or the hiring process or anything to do with compensation. And if you can't find it on here, then there are multiple ways of contacting people operations. We have a Slack channel. We also have an issue tracker on GitLab where you can go in and create an issue and assign it to myself or anybody else in the team. You can also email us. We have a people ops at GitLab email address, which I think most of you have probably seen or used. They've been replying to a few people already. But I guess for the most part, the other area that I wanted to point out was spending company money. Now, GitLab is I think fairly unique in that we really do say spend company money like it's your own. And we mean it. You don't have to ask for permission. There aren't any caps on expenditure to a certain degree. But if you want to go on a conference or something like that, there is a limit of I think it's $5,000. If I'm wrong, you can find it in the handbook. But you don't need to ask for permission. As long as it's in the interest of the company, if you're really not sure, because sometimes it can take a while for people to get used to that. You can just check it with your manager or email people operations before you go ahead and make the purchase. And I think most of you probably got a laptop already, a company laptop. But if you haven't, you can find the specs listed here, depending on if you're a developer or non developer. And we can people operations can order the laptop for you, or you can order it yourself and expensive. But there's some other equipment listed here as well. If you haven't had a chance to look at it. These are just suggestions, by the way, things that you might want to order. Obviously, some headphones are more expensive than others. But again, if you're not sure, just check with your manager on people ops for you before you order it. And the other area I wanted to point out was finance page. And if you're a contractor, obviously, you won't be put on any payroll, but you will need to submit an invoice to be paid. And the template is here. And this is a Google sheet. And you will need to make a copy of it, which you can do here. And then you just fill in all of the details. And then to submit it, you just send it to the finance email address, which is on that page. And it's AP at GitLab.com. And finally, I wanted to show you very quickly the Expensify page. I think everybody's got a logging. If you're a contractor, you won't have access to this, you'll have to add your expenses to that invoice template that I just showed you. So once you've logged in, this is really, really easy. You should see the inbox page. This might look a bit different for you because I'm an admin, so I have access to everything. I have so much power. There are kind of two ways that you can do this. So if you're somebody who is submitting a lot of expenses, all you really need to do is you can add them here by just doing the expense. And we'll put one here, and you type in your name, date, the amount. You have categories down here as well. And then you just attach the invoice or receipt or whatever, and you can do this from your desktop. I don't have one available, unfortunately. And then once you've done that, then you can save it. Yes, yes. I haven't done anything. So, and then that's that. But if you have a bunch of things that you want to do, like at the end of the month, say, then you can click on reports. And then as you can see, I haven't added anything to this yet, but you can do. And you see, there's my test from earlier, it's already in there. And then you can even add more to it if you want to. And then once you click save, it will pop up with this up here, when it's a comm and Wilson is the financial controller and he handles all of the expenses and his turnaround time is pretty legendary. I think as soon as I click submit in the past, it's taken here about five minutes and he approves it. And we don't have a cut off time for expenses either. But if you are on a payroll, I would suggest that you do your expenses by the middle of the month if you want to get them in that month's pay. So that is everything. And I realize I've spoken so fast, I do apologize. But if anybody has any questions, just shout. So you touched on it with expenses a little bit, but speaking of payroll, is there like a one one pay period deferral before pay starts? Or does it start immediately? Yeah, it starts immediately. Okay, cool. Good question. Okay, in the interest of time, because I was going to cover Google Drive in addition to getting on the team pages. Is anybody unfamiliar with Google Drive? Has everybody used it? Alright, awesome. I'm not going to worry about that so much. But if you're watching the recording of this, this orientation, and you have some questions, because it's just one of those things that if you haven't worked in an office or in a scholastic environment, where you make use of Google Drive, you may just be unfamiliar with it. And I'd be happy to walk anybody through it one on one. But I'm going to jump straight to the team page. Has anybody already added themselves to the team page? No, okay, awesome. So pretty, we've got a pretty tech savvy group. So this this may be redundant, but bear with me. What I'm going to be doing is I'm going to be referring to this this page in the handbook out of this website locally. You can see it's just a handbook slash get page update. Section 11 is add yourself to the team page. This is the action item on your onboarding issue. We want everybody to basically get get some experience making their first merge requests by by merging themselves onto sorry onto the team page. So so I'm just I'm just going to walk you through one of the ways that you can do that. There are a few different ways that you can you can make edits to kitlabs website. You can use it just directly through the web interface. You can use a stand alone IDE and terminal. But we also have a web ID IDE. And I'm going to walk us through that method because I think it's pretty cool. It's actually pretty new. So the first thing we're gonna want to do is head over to get lab.com and make sure that we're logged in. You're probably gonna have a whole bunch of projects. So of course, I've started to get into regularly. And this is the one we're looking at. This is this is our primary website, the about kill lab.com URL. So I'm going to open up that project. And then once I'm here, there's actually a web IDE button that I'm going to click. And that will pull if you're familiar with using something like Adam, it looks similar to any other kind of like desktop IDE only it's built into the web browser. And so in if we're following the steps about adding ourselves to the team page, the first thing we need is to get a picture of ourselves to upload. Ashton, sorry, sorry to interrupt. Are you meant to be sharing your screen? Oh, my goodness. Yes. We'll do that now. Thanks. Thanks, Abby. The team page I'm talking about, of course, is about get lab.com slash team. And you can see that everybody should be on here in the entire company. So it's a pretty large page and growing every day. So we're going to get ourselves onto that page. I'm just going to walk you through the process. And then I'll let I'll let you actually take care of the adding yourself. And if you need some some help with that, I can help you on one also. So let's go back to the web ID. I'm actually going to take you back since I went through all of that before I had shared the screen. So here I am, our www dash get lab dash com project. Get into the web ID by clicking this button here. Pull that up. Now we need a picture of ourselves. So I just happened to have one saved of myself here. And the picture has to be 400 by 400. So you can actually even just do this within max built in tools, but you're going to want to prop your picture. And then from there, resize it so that it's a 400 by 400 size. So let me make some quickly, just make a copy of this. And I don't know that I want to go too far into all of this. But if I make it relatively square, I can sorry, let's do this again. I can then just resize it to 400 by 400. I'm going to skip over that part. But if if anybody needs help editing an image, I'm also happy to help with that. Once you have the picture that you want to upload, you first have to put that in the proper folder, which is under source. And then images. Right over it. And team right here. So when you when you're ready to upload your picture in the web ID, there's this little plus sign next to the folder. Click that and upload a file. You'll find the picture that you want to upload. So from here, for example, and go ahead and just open that. So it's going to do a few things, you'll see that it now says we have one unstaged commit. So we're going to get to that a little bit later. Now we want to actually find ourselves on the team page, and we're going to to type in our name and all that that information. So that's that's in a completely different folder. It's under data. And it's a file called team.yml. So it's this one here. And this file is massive, because it's got everybody on it. You should already have an entry in this file for yourself. Just using your initials. So for example, Nikolai, if we were to look for you type in n dot seven dot there. And that's that's you right our database engineers. So you've already got an entry in the page. And at this point, you want to update your information. Something I skipped over with that picture is we need to make sure that the name on the file is your first and last name all lowercase. And then it could be either a jpeg or ping. But you have to remember what the file extension you use. So in this case, it's dot jpeg all lowercase. I found that this page is case sensitive for file extensions. So we're then going to type in our information here, for example, sorry, locality. And I'm not actually going to say this. I'm just giving you an example, type of where you're at, your role should already be in there along with the slug and who you're reporting to your picture, you want to make sure that the the name of your picture is in here and you cover the dot dot slash right there at the beginning. So have for example, in this case, it was ashtonherman.jpeg. Your Twitter handle you type in you don't need to use the at so in this case, it would just be like ashtonherman, your Git lab profile. Also, you don't need any at it's just going to be like a Herman, whatever your Git lab profile might be, you can actually find that if you're not sure by going to your profile here. Oh, that's displayed right there. And then we asked that you you type in a story about yourself and it can be kind of as long or as short as you want it to be. You can actually just refer to somebody else's entry if you'd like to see what other people are writing. So for example, here we've got under Tina, you can see that Tina has written just a short file about herself. You do want to make sure that spacing in your entry remains consistent with what other people are doing this this data file is very sensitive to to that spacing on it formatting. So we type in our story, we can leave it as is. Once you've you've updated everything and it looks right. We can go ahead and we'll see we've got two unstage changes, click commit. It's you can review the changes that you've made here. I will give you side by side what you have edited within the file. So here's the old one, right is whatever you've you've changed removed grain is what you've put in. You then need to stage these changes. You can do that by clicking the checkmarks. And then before you can commit, you type in a message. So something like add Nikolai to team page. And we'll actually want to commit directly to master branch, you're going to either create a new branch. Typically, you'll do that create a new branch and merge, you can type in the name of the branch like add apply to page and commit that will open up a merge request who you can assign to your manager or to me or to Abby. And we can we can go ahead and improve that and get it merged in that's assuming you don't have merge access already. So that was sort of the short and sweet version any any questions about that. I'm going to disregard everything we've done. I do do discard discard. Okay, well, again, I mean, like I said, we've got got a pretty tech savvy group in here right now as is. So I figured that that might be somewhat redundant. But if if somebody is watching this in the new or if any of you have any questions, please feel free to reach out to me. I'm happy to walk walk you through one on one. And that's it. We're just about out of time. So I'm going to open the floor up to just general questions or feedback. Awesome. Well, thank you very much for being our guinea pig group for our two part general orientation. Hopefully you got something out of this. We would love to hear whatever feedback you might have how we could improve it. Even even if it's specific to somebody in your role, what's something that that's general about the company that should be part of this orientation. Please just get with Abby or me about it. We definitely want to make this a better experience for people and just to make sure we're setting the right foot for for all of our new team members. But yeah, thanks again. Thanks, everyone. I don't think I didn't mention I just realized is that all of you have been invited to or will be invited to what's called GitLab 101. And that's where it's said and CEO and I would certainly make sure that you've read about the values because he does like questions. And he's obviously very, very keen to hear what your thoughts are about the values and any questions that you might have for him. So one thing I didn't mention. But yes, please don't think this is it. If there's anything that you need from either myself or Ashton or anybody else across the company, please ask and put your questions in the questions channel or in an issue, make a measure request, anything, anything that we can help you with just just that is done. And welcome again. And thank you for coming. Thanks, everybody.