 So, about a year ago, actually it was a little bit over a year ago, we had some activity on an ambassador ticket, so an ambassador-related ticket, right? So there's kind of been this question of how's the ambassador program doing, right? So over the years, the ambassador program has had many successes and trials. And I would say over the last three to four years, there was some kind of disjointedness in a variety of ways that created a decline in activity, a decline in cohesion, understanding how to go about doing outreach as ambassadors. Yes, absolutely, Justin, take your time, coffee is essential, so make sure you got that. Awesome, Justin, I can't wait. Right, so we had some disjointed, we weren't sure about processes and a lot of different things going on. So it was like, what's going on with ambassadors? We don't know. And even things like financial responsibilities were moved from ambassadors to mine shares. So it was like, people weren't even sure what they were empowered to do anymore. So I think we had to take more, like a lot of those things were out of our control. And then I think something is naturally evolved without stewardship to ensure that sustainability. So maybe we didn't, like the program grew, but didn't, we had more people, but it didn't grow, like the processes and how we needed to do things, right? So that's kind of how we got in the situation that we're in. We also had a restriction on how we were doing the budget. You know, previously we had card holders across the world for our contributors that we trusted very much to do that, but then how things in Red Hat operate changed, right? So we had to actually meet that function to a central kind of person, right? So some things were out of our change, but it also just threw things off balance. So about a year ago, there was some activity on this ticket, and I said, you know what, I'm going to take a stab at this. I had read a book change, or switch how to change when change is hard, and I had looked at how to improve the ambassador program, and it was like an example. So I did it in a book club, and at the end we're like, you know, let's put this, what's the right word, the system of change and let's like put something through it as an example with see what we can figure out by doing that. So I said, hey, can we use the ambassador's program with Fedora? And we're like, yes, yes. So we kind of, I had these analysis from a couple people, and I just sat down and wrote it. So I don't like, I was like a 15 page proposal, got it out, and we worked with the Mindshare Committee, the ambassadors who were interested in participating, the council, we had discussions on that proposal, and we made changes to it based on that. And after we kind of finalized it, Mindshare approved it, Mariana, Sumantro, and myself, we just started to kind of execute on the plan. So it's been a lot of work, a lot of different pieces, and we wanted to make sure that the community felt heard in how we redo the program, right? So we did a survey, we had rounds of feedback with people, we bring other folks in when we're wondering like, you know, how does this work? So we're conversing with stakeholders often to make sure that this has been evolving properly. We've shared the word at events about the work that we're doing, and we've also had plenty of volunteers helping us. We were kind of envisioning a whole big team, but it's very, it's thought heavy work, right? So we have to do like some strategic thinking and like how is this actually going to work? How can we evolve this? How can we modernize things? So it was kind of tough to bring like a large group of people into thinking about all those things at the level that they might need to, right? So instead we've kind of reached out to folks as needed, like, hey, at the beginning you said you were willing to work on docs like Justin, but you know, we knew that docs weren't going to happen like right away, but here we are a year later and Justin is with us. So that's just one example of, you know, we were including the community as much and as often as we can, though the team effort has me, Sumatra, and Mariano, like week by week making sure that things are still progressing. And for the folks who are in the chat, if you're comfortable, you're welcome to come up on the camera with us. There's going to be a lot of conversation to have. We can do it through chat too, but you're welcome to join us. So for those who have joined us in just the last few minutes, I've pinned a link to a wiki page and that's where we're going to start today. So I'm going to share mine just so that everyone can see it and it's on the presentation as well. So we've made this outline to kind of make sense of what we're doing today. And there's a couple different tasks that we have in mind. And basically we're going to say like who is here and what are y'all interested in working on and try to fit with some of those tasks. So I'm going to describe the different things that we're looking to do today. And then I'd like folks to kind of jump in in the chat with maybe where they feel like they would be a good fit for them. So what is the Community Outreach Knowledge Base? So we want to make a new, not a new, actually an updated ComOps Docs page. So Maryanna, could you grab the link for that and get it into our chat here? So this knowledge base. The HackMD? Nope. I'm looking for the ComOps Doc page. So right, that is going to land. So Community Operations is going to be the overarching umbrella organization over all these other Community Outreach teams, right? Like Community Operations is our internal thing, improving how we work together. That's the idea behind it, right? So we have this above the Community Outreach teams. It's very loosely structured that way, but we want to make a centralized place for people to find things. This is where, so Justin asked a question, I'm not sure if we, I'm going to wait a minute to get to that question, Justin. So right, what is this wiki page? This is so that we can keep track of who's doing what and make sure that we're not duplicating efforts, et cetera. So what are we, what are we doing today? There's going to be four main tasks and I have like the kind of our range in commitment and brain skill, like brain level energies. So here we go. So we have writing and updating documentation. Justin asked, how much do we have done? So we have some of the roles done. We're working on the roles, mainly I think is where we started. Some things can kind of just come over as is or need to be moved into a document so that we can rewrite it, right? The next thing is reviewing drafts as a documentation. Now I do think that review for grammar and all that and even like, does this make anyone to participate in that? I do think that Mariana, Sumantra, or myself should be like the review, the last review kind of thing. I think we should take a look at it before it gets pushed. Then we need someone to actually take that and push it to the new docs page. So we actually have to keep one thing in mind for that part, which is, I'm going to potentially get this wrong. HackMD, which we're working in, is in markdown. Docs is in ASCII. I think I did that right. I was going around. No, I think I did that right. So there's a little bit of a difference and there's a process that needs to be done to bring the documentation we have written in HackMD and putting it into the format of ASCII for docs. I did it right, just nice. Okay, so we do have some docs experts here. So that's awesome. So we need people to do that kind of translation. And then we also have, and this is probably the lowest investment, wiki pages that need to be marked as retired. So the important part about that is that we keep track of all of the pages we've retired. And this is so that we can make sure that we're not missing anything. As much as Mariana, Sumantra, and I have worked on this, it's kind of massive. And there's a lot of the wiki's structure around ambassadors is grew and grew and grew, right? So we need to make sure that when people look there, it's retired and we're sending them to the com ops page. We just want to, we want to make sure that we reduce confusion on ambassador documentations. That was the big pain point for people. So there is one extra piece, which is part of number three. It's like 3.8, which is we have a set of assets, design assets that our intern Darya has created. Darya worked at, are still working as an intern. I'm mentoring her on creating various pieces of resources for community outreach. So this is everything from team logos. So like updated team logos with the new logo, you can put wherever you need it. To which badges correspond to the work that gets done for community outreach. That's everything from like join sig to com ops to membership badges, etc. And then we have a whole set of documents called how to join Fedora. So those are three different versions and they're in like five languages each. So all of that needs to be put up onto the docs page as well. And those are done. They're right now in a Google Drive doc or Google Drive folder. So whoever is going to work on that piece just needs to drop a link in request access or you can give me your email and we'll do it that way. So keep scrolling down. You'll see that I've organized it by module, right? So these ones should probably each say module. So the way that the docs works, as far as I understand it from Justin, is that each page is a module and from there, am I saying this right? I don't know, maybe Justin should come up here. But basically, I think we're trying to do it in an ideal way in our hack and ease so that people who are converting it over to the documentation know what it is. So here we go, we'll hand books to someone I don't know how to get into. Right. So I guess for the folks who are doing the documentation part basically would just need to know like, does this work for you? As is, do you need it to be formatted a different way or etc, etc. Is this, does this make sense as it is? So you'll see I have made, sorry, tables for each one of them for people to go in and say, you know, this is what I've been doing. I think you would just like put your initials or your Fedora account thing here. And this is an overview of like all the different things we're trying to get up here. And then we did gather a lot of existing links already. So we tried our best to make sure that we could get as many as possible. But there's probably still ones out there as I mentioned earlier. So these are all related docs and wiki pages, etc, etc that we can pull information from. So that was my spiel. Any questions to start? I don't have a question, but I can explain a little bit how we prepare the content we have for the commops roll handbook. So as you saw on the wiki page, there is a list of links that we have gathered for each roll handbook. We gathered all these links or what I did was just by googling Fedora commops member or something like that. And we tried to collect everything and any type of information we had about commops members. And then we reviewed all of these texts and we came up with a new content or just copied and pasted and updated some of the original documentation. So this is what we did practically. It's not that we reinvented commops documentation or anything like that. We focused a little bit also on the tone of voice for the roll handbook. We wanted to be a little more friendly instead of just a superficial documentation because if this is meant to be for somebody who just started contributing, we didn't want to have terms that they're not aware or something like that. Go ahead, Mariana. I was talking about the HackMD. So beneath the commops roll, there are the other sections. We have created subcategories or subsections that fitted the commops roll but may not be fit for the other ones. So if you think that you have to split it based on something else or either remove something, feel free to do so. Hi, Justin. So I actually just noticed that we have some documentation that didn't come from our docs page, Mariana. I see that there's some missing here. So I'm going to actually move that over. But based on the different things, I'm open for commentary right now and questions on how we're going to go about this, as well as, you know, if you have an idea of one of those tasks that I mentioned, that seems like a good fit for you. Feel free to drop that in the channel, et cetera, et cetera. And we'll start getting people kind of assigned and working on one thing or another. I know Justin has a comment. I guess for me, I was wondering at least one area that I could help out with is looking at the modules as they're written out on the on the wiki page. I can put, while people are working in the HackMDs and working on content, I can start setting up those modules in the ConMops docs repository. So it's that way. If you have it written, there's a file, we just have to go and update. It's already there, just an empty placeholder. Does that make sense? It makes a lot of sense. I'm wondering folks are interested in doing documentation. Like, maybe it would make sense for Justin to share his screen as he did that. I don't know, Justin. Are you comfortable with that? If it helps, I can go through, like, what the modules look like. But there's also some docs in the Fedora. Yeah, go ahead. Oh, no, I was actually letting you go ahead. So there's some docs in the Fedora docs. And I'm trying to look up here that explains what the modules are and how you can create those. Actually, no, we don't. We have just the reasonable. OK, so I don't have a different page. I'll still link that in the chat. That is helpful for people, right? But I think we have to figure out how to create a module and what I'm doing. Oh, that's a lot of timeline. Yeah, Justin, your audio is doing a little thing right now. Yeah, your audio is really garbled. I don't know if it would help to maybe turn off your video, but it was like a no sound. And then a boom, boom, boom, boom, boom, boom, boom. Hey, everyone. Hey, Adam, how are you doing? The video is weird, but the sound should be fine. Sound is spot on. OK, cool. Glad to have you here. So, Adam, what are the different things I was describing sound like a good fit? Like, what would you be interested in working on today? I can help with, like, the heavy lifting. We're setting up the dog's side of things. I don't know if people know the. Templates that we have on Packer. I need to find it. Awesome. So we have two people on Docs. We'll have Adam and Justin on Docs. Jack, how are you feeling? I'm feeling good. Glad to hear that. Tell me, tell me what you what you think I can best take care of. OK, I think since we got two people on Docs right now, how would you feel about retiring wiki pages? Yeah, that's fine. OK, cool. So basically you want to go to the wiki pages that are here existing wiki pages. I think what we need to have in there is a link to the new Docs site. So that's the ComHops. And I think we might have actually have, like, an example of a retired thing on the wiki. I'm just not sure where it is. So we can actually do a redirect. Oh, Justin, there's a high pitched sound coming from you, I guess, and it's painful. Now it's gone. Oh, sorry. It's technology is not on your side today. I thought my neighbor turned on their television. OK, Adam, I like your idea even better. Like the redirect sounds even better. But will people ever get to that page and we still haven't marked as retired? The question is with the redirect. If you redirect, then you basically no one's going to ever see the page that was there before. So it's a matter of figuring out whether there's any value in leaving that page, even though it's retired as up, or whether it's just more practical to have it forward to the ComHops page or wherever. So I think it's probably more beneficial to have the redirect in my opinion, although I do understand the desire to have that historical knowledge accessible. So I don't know. What are other folks' thoughts on this? I'm curious to know what you think. So Justin said that the redirects are super important and they're tuned for SEO. So I guess that's probably the best way to go then. The redirects will make it hard to access the wiki, like even if you want to then edit it and maybe take it back or something like it'll make it tricky because it'll keep redirecting you to the docs. So like you will never get back to the wiki page again. But we might have an example for some of the quick docs, but I don't have the wiki links. Yeah, Justin just sent the link. Oh, cool. Thanks. So basically you can view the source is what you're saying, Justin. OK. Well, that's how he, yeah, that's how they did the redirect. Right. And if you click view on the top right, it'll basically take you right to the docs. Yeah. Got it. OK. I didn't actually, we didn't incorporate this into our thing earlier, but I'm absolutely happy to adapt. Yeah, so if you want, I can run through those wiki pages and then just redirect, put in the redirect. So only should be done once the docs page is wiki. Gotcha. OK, so that's going to be kind of a last step moment. All right. Then I think we're going to pause on that. And how are you on pushing content, PNGs, SVGs, and stuff like that to the pages? Does that sound like a section you could tackle, Jack? Yeah. Yeah. OK, cool. I'm going to share that folder with you right now. Here we go. Thanks for that to your Amelonics, you know. Yeah, either that or just that. But Daria was prepared. Actually, Marie, just send it to Jack at Fedora Project. OK, you got it. This way it's compartmentalized. All right, so basically what you're going to work on then, Jack, is moving these onto its own module of docs. So you'll have an over. Hey, Semantro made it. You got power back, huh? Yeah. Fine. Nice. You're a little windy right now. All right. Right. So you'll see in that folder, there's subfolders. So you see Badge Artwork, T-Cubes, how to join Fedora. And each one of those will have assets. And then each one underneath will be each one of those folders. And then those files go underneath. So is that something you can work on, Justin? Yeah. I'm so sorry, Justin. OK, cool. So we have Jack on something. We have Adam and Justin both saying they can do heavy lifting, setting up the docs pages. So who else do we have who would like to pitch in? And I can help find something to work on. If y'all just want to watch for now and pitch in when you're ready. Oh, awesome. There he is here. OK. So I think what we can have you do, Daria, is to grab this first one here, the team overviews. And this is actually not going to change too much. So what needs to happen here is we need to just take the current team overviews that exist and bring them into this document. So that's really just an overall description of the team. Then once that's done, Daria, you would let us know in the chat. And then me, Mary Honors, Sumancho, we'll take a look at it. And once you're done with that part, we can move on to the next thing. All right, so Daria, does that sound good? Cool. And I will give you this team overviews length directly. You just have that right in front of you. So write anybody else here in the chat with us ready to work on some docs. So it looks like Adam and Justin are figuring out who's doing what as far as docs pushing for the outline there. So I guess we just kind of get into it. And then I'll try to leave the screen up and look at the chat every few minutes to see if anyone's jumping in. Mary Honors, Sumancho are here too to help. What I'm going to start doing is finishing up moving the stuff from our docs that we had written up as the co-leads and make sure that they're on to our hack and deez. And then kind of check back in with the team. How's that sound? All right, does anyone confuse about what they're doing or need any more assistance to get going? No, but if I have any questions, I'm sure that I'll ask. OK, OK, great. OK, we're going to get to it. I'm just going to put myself on mute and feel free to jump in with any questions. All right, I have a question. Is there a current process to become a ComOps team member? Like besides like introduce yourself, go to meetings, et cetera, et cetera, is there like some people open a ticket? Or is it just like they ask and then someone says yes or no? Anyone know the answer to this before I dig deeper? I believe there is nothing like that. I believe it is introductions. And then if you want to go for a join, then join might help you to get into ComOps. For all I know that's the process. OK. Justin might make it better. Thank you, Justin. OK, drop something. I'm going to take a look at that real quick. And Jack, I'm sharing that with you. I think we're just being fussy because like you're outside of the organization. Just ping me again if you need any more access. Thanks. So this link that you provide, Justin, is like a how to join ComOps, right? So we're rethinking it a little bit to be these role handbooks. My question for the group here is, do we think we need a how to join as a separate section? How to join each of the teams? Or should that be in the role handbook? So ComOps team, like role ComOps team member and then like how to join underneath that. Does that make more sense? I see Mariana. So OK, so what is there currently needs to be? I put it in the team overviews model, not the handbook. So you put the how to join in the team overviews module. OK. Yeah, I think that makes sense. Anybody else have thoughts on this? I guess the role handbook is like after you've joined, but I think you would need to read that to know if you wanted to join. For me, it would make a lot of sense after a short paragraph describing the role, telling you how to join that, or how to leave that group. So with the team overview, do you think it makes sense? Or the role, is the role or the overview as a role? So we have a role for role, a role for overview. Sumantra, I'm curious. And Daria, I'm here right with you. What's your opinion on this? I would go for the role, because it is supposed to be description of the role, exactly the part, and then if you're not interested, how can you just tell a role so that they don't read? Sumantra, can you speak a little louder? So yeah. All right. So I would basically go for the role, because I basically want to know what's in it for me to do, as in actionables. And then more importantly, if I don't want to do them, or I want to leave the group, I should be able to explicitly mention other people that I'm not blocking their way, and basically just role. It would be from the role side. OK, so I think I've just thought of a good compromise. What if we have under the team interview a link that says, and here's how to join, kind of a thing. And then it just brings you right to the role. Would that make sense? Because then you have it kind of linked right there, and if people are reading the overview, and they're like, oh, I want to join, if someone else keeps it a little bit segmented, but we have it done in both places. Does that sound good? Yeah, OK. Justin, what do you think? My idea was to keep the overview brief, because it's an overview. Sure, it will be brief. It's just going to say, and here's how to join, right? But it's just like it'll link us over to the other thing. Justin, what do you think about that? We got a plus one from Daria. OK, the main question was what you had already answered. We had some back and forth on where the how to join section should land, right? We had a couple of votes for under the role handbooks, a couple of votes for the overviews. So we're saying to really go into depth on how to join and how to leave, we think it should be with the role handbooks, but we can link to that in the team overview. So team overview, and here's how to join, and it is a link to that role handbook. Are you on board with that? What do you think? Right. OK, right. So but I think like, well, it would also tell you like how to retire or leave the group. And it would also tell you like how to come back. So those are also things we're putting in there. So maybe that's why we're thinking of the role handbook. OK, OK, I'm going to continue on. I'm pressing on any. OK, so Daria, you're ready to do something new, right? OK, cool. So you have the team overviews. Awesome. So how are we going to do that? OK. So someone needs to review that team overview section. We're going to leave that as is. The next thing you can work on is this community outreach batches turn. So some of them are going to have, some of them are going to be pushed already. Some of them are not going to be pushed already. But we need don't worry about the art. Jack's worrying about that part. So we're actually going to have just a little bit of text that needs to go with this, right? So what we need is what the badges name, like the title and how to earn it. And that has to be for each one of these. So I'm pretty sure you were the creator of these badges. So you and we reviewed them many times. I think there might also be like a list overall in our meeting notes, our weekly meeting notes area. So how does that sound? Can you pull that one up? OK. Awesome. Question. Has anyone ever retired from the comm ops team before? They might not. But since we are making a road handle, it's important that they give them a way out. Absolutely. Oh, absolutely. I just wanted to know if something that had happened before, if it referenced, or if we kind of want to think about how exactly someone might go about this. Would it be a conversation with someone on the team that they trust? Would it be something on the discourse, like, hey, folks, I'm taking a break, or moving the team for the time being? And one of their experiences, people had on other teams, other places, not even Fedora. I know people here working all over the open source community, like how do other people handle that retirement thing if people want to leave? Or do people just quietly back away and we just let our group membership grow and grow and grow? Thoughts on that? So in this case, we should create a role on how to survive. Yeah, I'm asking what how. What is that? So what we used to do in Ambassadors way back is basically after a period of inactivity, we would basically reach out and just ask the person, are you still active? Or do you want us to remove your, you know, retire you from the group or whatever it is? And if we, depending on what the response we got back was, or whether we didn't receive a response, then, you know, we would remove them unless they came back and has to be added back. Right, right. So that's exactly what we did for Ambassadors. I want to say like eight months back at this point. So I think we can just take that over and we need to just build it into the comm ops kind of like this is part of the responsibilities of the team is to do like kind of an annual check in like who's been active, who hasn't maybe send out and have that moment. Yeah, what we did with the Ambassadors was for folks who had not been active in the Fedora account system for a year plus, I think, we sent them an email directly and we said, hey, this is what's going on. Do you want to be a part of it? So is that year like a yearly cleanup or cleanup seem like the right cadence? Yeah. And then if folks want to do it on their own, they can maybe. So as far as I'm going to remember when Ambassadors wanted to retire, they would just send an email on the Ambassadors mailing list saying that, hey, I'm just stepping down and might come back or whatever just life goes on. And I remember that I have read some emails from people. When I first joined InfoNC, the people were stepping down with simply an email. OK, so comm ops does not use the mailing list. There's discourse. And actually, I think that's kind of a nice way for people to leave their remarks like, hey, we'll miss you or thanks for all your work, kind of a thing. So I'm going to write that process out to be a discourse thing. Otherwise, it's a yearly group cleanup. Cool. So does something that wants to voice out that Alicia mentioned that the process for the joint saving actually is some of the points as you go by the joints, they got already listed on thought by Alicia, which is interesting. Sure. So Sumantro, your audio is not free. I don't know what's going on with that. But I think that we had talked, Mariana Sumantro, we had talked about simply linking to the joint page because it was already in existence. And they've kind of expressed the desire to be a somewhat separate entity. So I feel like although it's connected to the community outreach teams and should be listed here, we don't actually need to go in depth there because they have done a great job managing that team. And I don't think we need to try to make changes where don't try to fix it if it's not broken kind of thing, right? Exactly, Justin. That's my point too. How does that sound, Alessia? If we just link to the join docs, see in a few, gotcha. OK, so we need to know exactly where that's going to be. So I think we can actually kind of, let me see. This is probably me in. I think we should have them both in the team inner overviews and the modules just to make sure that we're covering all our bases there. So let me see these join docs real quick because we could send it to two different places, I think. So I think the team overview page could be this linked to that specifically. And then let's see. Then there's membership, I think that's fine. OK. And then if we could directly link to membership for the team overview. Oh, man, I want to get these. There's some graphics on here we should redesign. OK, so what do folks think about those ones? Using those links there. Does that work? I'm going to take that as a yes. I agree. The join six page is very well structured and the content is very well. I like it. Yeah. So I think we just have to link to that one. Hey, Maria, I have a question. Sure, what's up? Hi, so I finally managed to get that file. OK. So basically, was it supposed to have any of the other stuff in there, or is it solely that how to join Fedora stuff? So there are supposed to be more than that. Let's see if I didn't share the right one here. There's supposed to be. I'll try this link. I'm going to send it via hop in. And then how are those usually linked on that page? Are they hosted anywhere that I can use to include the link on that on the like in the HackMD doc? Or how does that work? Right. So I think part of what we need to do is have them visible, so that people can actually see it and say, oh, wow, that looks cool, and I want to use that. So OK, I just sent you another file link. Try to ask for sharing on that one. So we want to be able to see them. So there's a chance that we might need to generate some smaller PNGs, which is fine, because we have Dario here with us. Or we can do it a little bit of a later date. But I also think that we should have the full resolution and the source files available there, too, as links. So I think we should have full resolution, a source file, as links, and then just a small PNG or something if we can use the one that's generated already. Great. If not, we can make new ones. How does that sound? Yeah, that sounds fine. So am I uploading the original file there, like the PNG or whatever it is, onto the actual hackMD doc? OK, so yeah, we don't need to. We can skip the hackMD part, I think. Actually, let me ask my docs people. Docs people, what is the easiest way to get a set of graphics up onto a docs page? What we're looking to do is have a thumbnail so that people can see what it is and say, hey, I want to use that. And here it is in French, German, Spanish, Hindi, et cetera, et cetera. And then we want to have links to the source file and a full resolution like PDF. So basically, I'm wondering, what is the best way to do that? What should our process be to get those up there? I guess we got to commit them to this assets folder in the repository. OK, does that sound right, Adam and Justin? OK, cool. So I guess my. And if I unmute, you will even hear me. Yes, I'll do that. We can hear. Yeah, OK, so that sounds good. I guess my one question is, I guess we could test to see if you can make it a thumbnail there, but we might need to generate more files. So if that's the case, let me know. How's that? Good. OK, folks. So I'm in so many different presentations. There was bound to be a little bit of overlap. I have to leave just a couple minutes early here to go do a Mindshare Committee presentation. So Sumatra and Mariana will help wrap up. My only thing is I just hope that we can document what everyone's been working on somewhere. Would that make sense if we just had like a hack empty or do people want to update the wiki a little bit? I just want to make sure we know what progress we made during during that. So Mariana and Sumatra, if you want to organize making that happen so that we can see where we left off, what needs to be done, what we did get done, et cetera, et cetera. OK, cool. Thank you, everyone, so much for helping out. And this is like a great start to stuff. And I think we're going to have like a solid base for this for the knowledge base. I used the base twice, but here we are. And I will talk to you all soon. Peace. Bye. So anyone have any idea why when I try to log into Pagar? It's Tom, the open ID request is canceled. So Jack, it happened sometime that Pugya looked at you that it's not going to work out. However, can you verify going do you have a CLA plus one by chance? What was that, Sumatra? So you need a permission for CLA plus one. If you don't have a CLA plus one, then it will eventually just tell you to do it. Basically, not authorize it. So what I can do quickly for you is, if you can give me a phrase in the name, I can add you to the Docs group. Yeah, it's just Jack. So Peter, I have 2SA on, but I know that my 2SA weren't. Does anybody know when Nick is? He is kind of the admin for the Docs. I can add you to QA if you want. I have access for QA. I mean, for the time being, that should suffice. Because you are not on the Docs group. So hey folks, you're on the top of the hour. So great work by all of you guys. Significant amount of help the organizers through giving more importantly, finally pushing things to wherever they needed to be and the explanations you're going to find out. So this is a continuous process. Two hours. That's my problem. But yeah. That's a great start. So in the last minute comments or something. Yeah, just in that area, if you can update. That would be awesome. I don't have a comment. I just wanted to thank you all for helping today in anything that you worked. It's really amazing to see the whole revamped process actually come into an end, because the goal was to end it in a few months. And having documentation in place is one of the most important points of the entire event. So thanks everybody for joining. See you around the nest. Bye.