 Hi, everybody. Come on in. We're just getting started. I'm in mirror mode today because I'm going to be doing some demonstration. My intention is to, instead of talking about things, actually show stuff. Sorry, one second. Yeah, go ahead. I was just going to make sure we're live. Yeah, let's make sure we're live. I know. I wasn't actually starting. I was just talking over the people sitting down. It's like that thing with the DJ starts, you know. Do you want me to shut up while you go? You're good. Thanks. Now you can start. Thanks. My favorite thing is to go live while I'm in the middle of a sentence. So it's obvious that everyone's missing out on something if you're not there. OK, we've got a couple of spaces up front on the side. So this is stop reinventing the wheel. And this is not an angry old guy standing on his porch shouting at you. This is somebody who is with his hand over his heart saying, please, can we all figure out how to, we all are doing such a good job doing this all by ourselves, figuring it out by ourselves. Let's get together a little bit more. So that's what this is about. But there is going to be three easy steps when just some demonstrations and a few things. And I'm hoping folks have some projects that you want to take a look at with the process. So because I just couldn't think of any. I was like, I'll have some ready just in case. Well, that didn't happen. So just a quick overview of what we're doing. The zero with thing, this is the link to the resources of this whole presentation. There's a worksheet that's going on, like everything you need. I'm going to make sure that link is present. It's at the footer as well and other stuff. That's actually a sim link that points to an HTML file. Either way, it's there and we'll have chances to look at it. And I'll leave this up here for a few minutes. In fact, this will stay here for a few minutes. And then I'll introduce myself high. And I'll say why we're here. And then we'll see what we can get out of this and then we'll get into demonstration. So just briefly, my name is Karsten Wade. I'm also known as Quaid in any short online media. That's my persona internet, what do you say? Numde internet. And I've been involved in the open source way writing the guidebook and talking about it for dozen, 13, bakers dozen years I think now. And I'm a principal community architect at Red Hat in our open source program office. I know community architect is, I mean, honestly it's a lot like a physical architect in building and construction. I walk around projects all the time. I have talking with people. When somebody needs a hand with something, I help them do what they're doing and help connect other parts of the project together, lay out a plan to make all that happen so that communities can be successful and work hand in hand with the other people like you would with a construction manager or a scheduler or anybody else like that to help make sure the projects are successful. And generally I work on strategic projects. We'll probably, I'll use one as an, just a simple and short example later on. And yeah, and we've just released the guidebook, the open source way, version 2.0 came out early last year. And this is, for a long time, my whole point was trying to, I was wanting to get everybody to help write more. Let's get together, talk practices. I'd like, it was sort of a huge Apple big bite concept. And that's not what this talk is. I've sort of switched my mode. I started last year when I was at open source summit in Seattle. I started to just talk to people and feel differently about some things. And then I saw some talks at open source summit in Austin that confirm those things. Actually, I think after I did this proposal, but we'll get into those two. And there's a call to action out of this, which is just that we really, we really need to talk one-to-one more across projects. Talk to people who care about community stewardship. You don't have to have a community manager in your title. You just have to care about the stewarding of communities and to reach out to people beyond and just have coffee, tea, some kind of average virtual life and make relationships and then let's work on it from there. There's resources and things to do when you're ready to like do stuff, but talking is a good place to go. And then we'll try to get to the demonstration. Yeah, so let's go. But I just want to spend a couple of minutes talking about the why part of this because I think this is important. I want to drive back home about that thing about creating community amongst all of us. I do think it's the right idea to dig into this book to show you how it works. So that's good. But I do think that I might have been doing this sort of field of dreams technique for too long. So I'm gonna be showing some pictures that are notes that I captured and at these open source summits, for example. They were done in Remarkable and they have this terrible grid so I did redo them without the grid. So that's what's going on with this. And this was from Ava Black's talk. They were talking about codes. If you just went to the talk yesterday, very much the same as the talk, same one. And stewardship, caring about people, being this most important thing. I'm making sure that that was something that was at the center of all that we were doing. And that was just resonated with what, like I came to that talk with that in my heart and then that's when the words were said, I'm like, yeah, that was it. And then I wanna share with you about these three talks as well for a moment, just to show you my notes from these three talks that I attended an open source summit, Austin. So one of them was, I pardon my, doing my best to remember the name presentations of everybody, but I believe Anna Filippova did scaling your communities. I'm forgetting the full title. My brain's on that today. But the thing, it was a, what I, the key of what I experienced was people who were newer than I am at doing community management stuff, they were doing everything right, but more, they were teaching me things. I was, oh, I'm part of it that way, like over and over again. And so this was one of the ones where, where Anna was talking about scaling and had a marketing perspective on scaling that was just phenomenal and was applying it into open source collaborations and it was making, it was extending the art, expanding what we could be doing with it. And when I asked, and I said, you know, afterwards, where did you, you know, I didn't say, hey, I've got a book, but I just asked simply, where'd you learn all this stuff? I had to figure it all out. We trial and error, wow. You know, look to have coffee with you some time because it's like, yeah, I'm done with that. So, and then Karen Woolock had a great talk on turning users into advocates. And one of the, one of the ideas I love was this, was I've always talked about lowering the barriers to participation and she, she pictured them as solo. It's almost like a rap. It's like barely little bumps along the way. Something where it's this one more, one more little thing to do step. And then she used an example from a, like a Google review process where it just said, hey, did you use this place? And you just like one question, one answer. And by the time you were done, you created an entire review as opposed to just be given a review out in front of you, right? So it was, you know, it was more powerful. And a way to just kind of walk people into it and make them sort of sneakily with gamification, you know, caught up in it. And then Amy June Highline, I think I've got, if I said that right, I had talking when finding your niche and open source contributions. And you can see I'm like, I wrote help. I mean, this was like a big point to me. I'm like, I'd never thought, remove the fucking barriers. Remove them, right? Like, can we do that? Yeah, we can. We have software, we can automate things. We can start removing things that we just always take it for granted. Pardon my swearing. I'm just, you know, it's like a passionate thing. I get it. And it's just, and what she said here, being invited and being included are really different. Being invited and being included are really different things. So with all those things in mind, I'm gonna get into doing some demos, just analyzing some projects, diving into them, showing you what I would do as a community architect to look and say, here's what's working, what's not, what we would flag to want to be taken care of to help the project. First, attract users. And because users are contributors, they're contributing their time and attention to your project just to even read your webpage, right? So let's give them something backing from the very beginning. So this process, it's not that complicated. I mean, it is, but it isn't. It's kind of an analyzing and action process. You want to read through the book, read through the parts that ring with you. Think about your own organization and what you know and don't know about open source. So sort of do your own mental gap analysis. You can do written one too, but don't show it to anybody until you're ready to put it because it could be kind of a, anyway, gap analysis like this can be a little bit dark. You suddenly discover like, oh, we're not doing that, are we? And then when it comes to the project you just want to work on, do a full assessment of it, going through the worksheet and then write a report. I'm going to flip over an example of what I mean by this report in a moment. And then just act on your recommendations, which is the kind of thing I've been doing in a project since I wrote a report on it, like a year and a half ago. What's here? Yeah, okay. So now I'm going to actually flip over to, look, what do I have open? I have, that's what the one I was looking for. I'm looking for this one. So this isn't, I didn't do a full check through on this to make sure that there wasn't, I think I've got this released somewhere and it's vetted and it's all cool. I just didn't know for sure. So I didn't put this on the resources page yet because this was my internal copy, but I believe it's all there. But this is the, this is the end, the example of what the end report is like from the different, from the worksheet that I'm going to be doing in a moment. So, and then at the top and it's got, at the top it's got key recommendations for everything, executive summaries, and then all these different areas to go through. And at the end there's a, oh, I've paged all the way down, that's what happened. At the end there's a, I just basically have a massive list of all the things to do. And that's just kind of like the punch list. Like consider and create a meetup calendar for tracking users, or create a lightweight style guide for blog posts to make writing and reviewing easier. Create a tracking process and metrics tooling to track contributors to the operate first project itself, et cetera. So that's the basic idea of, oh, see I'm not, didn't mean to be jumping ahead. So let me get, let me get the worksheet over and show you what this looks like. Oh, that's what happens, this was on the wrong, okay. There we go. Hi, yes, let's do some questions. I like that part. Yeah, we'll make some room for folks to sit down as we're, let's get comfortable for a couple of minutes. Yeah, thank you. Appreciate that. Yeah. And also if I'm, I try to be mindful about speaking slowly and speaking up, but if I, you know, talk to everyone like, you know, anything just, somebody throw a rock at me, I'm sorry, I don't mean to make you do the work of me, but I'll try to pay notice, but if somebody needs to flag me too on the way. Thank you. Appreciate that. Awesome. Wow, cool. Okay. So let's, so basically what we have is this overview of the work, so this worksheet is in our GitHub repo, which is the link should be on that resources page. So we can look at that sometime, but this won't matter, this is the main point. And this overview basically has the high level questions in each of the subsections. So it's going to have for structure, which is, we used to say infrastructure, but like what's the, what's from the, from this is, this is a, this is an analysis done from the viewpoint of a person who's coming to a project, either having never seen it for the first time or pretending like you haven't seen it for the first time. And you know, like I don't go and ask anybody to find something for me. My whole job is to find what's visible that should be there. And it doesn't matter if it's there somewhere. You're like, oh, but we got it. Oh, it's fine, but can I find it when I come to your website, right? So this is going to be a whole list of all the things that the structure of what your project looks like to the people coming in from the outside. And so then, and some of these terminology, this process has been developed over a dozen years. And so things like release management, we like the first time, like taking this out every time I take it out into a new language or a new programming language or a new part of the open source world. They'll be like, oh, we don't do that. That's not how we do releases or we don't do releases is always something. So this is the kind of area that does need to be always reconsidered. These are the kinds of practices that as we talk amongst ourselves, we'll discover the differences and that kind of thing. And if we ever want to write them down, we can come back and fix all this stuff. Activity, what's the idea? What are the activity of the project like? What is it? Here we go. What is it actually doing on the day-to-day, month-to-month, year-over-year basis? Documentation. One thing, we've always said documentation is important. I was a docs lead in Fedora project for a number of years. That was my biggest first run in doing open source work. Excuse me. But Demetris Cheatham has been doing work for all in opensource.org, which is a project working on opening and open sourcing diversity equity inclusion. And part of that effort has been doing a massive demographic survey. Some of you may have heard of it, as well as talking to hundreds of maintainers. And consistently, everything that blocks people who are marginalized or underrepresented in their communities is the quality of documentation. So, super important column. And this gets in there to that. Code quality is often just the best attempt depending on, if you can get an expert to take a look. Sometimes that's worth it. Sometimes people don't really need that. Outreach, basically what's the community doing to try to get word out about what it's doing? How is it outreach to other people in the world? And then making sure that the license considerations are covered and that's clear, that has an open source license and that stuff is clear as well. So, in these areas are gonna be things like, does it have a code of conduct, by the way? So, even though that's not a high level thing, that kind of stuff is in here. Oh, and so, I think that must be it. What is that one? It must be down here. So, okay, so basically the idea is then, each one of these, let me find, now I'm gonna try to do the mapping back for you here of what I'm talking about, right? Is that a web browser? How do I get in without a web browser? So, if all of the major sections of this guidebook correlate to two things that you're doing that's coming out of that audit. So, if you find something that's lacking, there's gonna be something in this book that's gonna help you give you some guidance on what to be doing about that. Oh, there's no governance for this project. Well, the entire chapter on how to do governance, right? But in particular, if you go under measuring success, this defining healthy communities, if I pick the right chapter, yeah, you'll see a correlation structure, release management, essentially the fields from that worksheet are here in this book. So, there's a direct connection across the thing, right? So, you have to do the mental work of finding the relationship between what you're discovering in a project and what you're looking for in the book from having read it. We don't have a better index than that, but it's a reasonable thing to do to the point where when we do an audit of a project, it's usually, I try to lock it into two to four hours total time of looking at all the stuff I'm filling in the worksheet because it shouldn't take much longer than that to find all the things. And now that I know what I'm trying to look for, I've got the whole process down, I can do it. The first time you do it, it might take a little longer, a couple of days, that kind of thing. But, didn't know just be able to make the relationship. So, let's talk about a project. So, let me have a project in mind that you would like to take a look. And while you do that, I'm gonna show you what I mean by what, this project is the operate first project. If you go back using the Wayback Machine, you can see it's a very different project thing in the past, but it, this front page hits all of the points that we're trying to make. So, there's a call to action in here, there's information that's going, the call to action could be something like download or install or whatever, but it's something that people can do. And then it goes into it and explains what the project is about, and then it gives people information about what they're interested in doing, how to get involved, what are the drivers, and then going down. So, this is an example of something. If I did this, I think, hopefully I would pass my own audit. So, I'm not gonna do this project. But, do you have a project? Yes? Can you, what's the domain? Okay, and then let's think of, so we saw all of the different categories, the different columns in the worksheet. Excellent, thank you. I love it. What would be, because we can't do everything here today, right? Is there anything in particular that you might be interested in offhand to dive into? I said documentation before, so that's one that I could go at. Sure, okay, let's take a look at documentation. Okay. I'm not a little bit interested. Yeah, yeah, well, use quite a bit. So, the idea when you're in here is that there's sort of a main question you're trying to roll up to for the report, and then these detailed questions are, this is where you go from the general concepts to something maybe a little more detailed, if it needs to be. That might be where the nuance around a programming language or on a different type of open. You might be dealing with open design content instead of open source, so you may have different with places of thinking inside there. So, there's some presumptions in here that I'll point out that one of the presumptions is that you want something that's like a quick start guide that, no, that dark's not that great. I could make this bigger. Can I make this bigger? I don't know how do I do that, but I go to View, Zoom. I thought I knew the quick keys for it. 150%, a little bit better. Let's do that again. Go up to 200. Okay, there we go. Thank you. At least that part's a little bit more legible. So, and then the core being quick start for people that are getting started with whatever your thing is. Is there documentation for new users, installation, or some way to get it going in an environment? You could see all the source compilation. You can see how far back this checklist goes, right? Change log, right? This would, I would expand this out to talk about things like, well, references back to things like get repos and what's going on with that would be an interesting one and a two as we go back to release management. Okay, so let's go over and take a look at the Green Software Foundation. So, off the top, and I mean just noticing off the top, so we've got a great call to action. The thing I'm being asked to just sign up for the newsletter, and let's find out how that flows. Okay, I'll go back over to that in a few minutes. Okay, and then we got a link to the GitHub repo. That's good, it's like, oh, I can see, but it's not up in my face the way the stuff was. So, let's find what's in the Subman News app. I don't know, I'm going to show you my cross code to connect projects, links off, resources. And then articles, okay, resources and articles seem the most likely to be what I would equate to documentation. So, one's going to tell me about, oh, okay, cool. So, I'm dropped into a GitHub repo, which has a readme, which is a form of documentation. It's a slightly more jarring experience. I would note this in an important, that you might consider, if you're thinking about who the users are, you want to be going to this, is dropping them into GitHub repo without a warning, a thing you want to do, right? So, this is, I guess I would be putting my coffee down and going back over to the worksheet and be making a note to this over here. So, it might be jarring or scary to be dropped there without warning. And I'm going to say scary because, you know, people, it's regardless of what you personally might feel about a GitHub experience as a, oh, it's so great compared to other things, but it's just compared to the other things, so. And no, I'm no expense. I mean, this is a great website. I'm only, I'm supposed to be picking and finding problems, right? This is awesome. Okay, what's the next one we got? Principles of green software engineering. Whoa, cool. And then we got a whole new world. I like this, okay. Endorse the principles and join the news. Okay, wow, cool, bam. I think it's my principles. Okay, I got my call to action. I know what I'm up to. Okay, I can get back to this in a minute or later. I'm going to leave my tabs open to go do, I won't do all the expression. And then articles takes us up, too. Okay, so what I've got so far, cool articles about that, cool, is that I am, of course now I'm warning part of what the things you're doing. I'm thinking what are the, so with all of the areas that are called out and they're working groups, let's go see what the documentation parts would be there, too. I can make this a little bigger so we can all probably get a little bit of view of what we got down, if I can get. Okay, so I'm looking at what is, what are the projects? And this is going to take me into, I'm going to drop into one and see what's going on inside this working group. I mean, basically it's kind of like I picking one at random. If I was spending more time with this, I'd probably go, I would try to figure out what was a reasonable sampling and see if I get it, if there was any trends. Like if you go into 10 of them and they're all like absolutely perfect and things like, okay, somebody's curated all of this content, it doesn't necessarily have to go through every single page. So I'm at the point where I'm going, now I'm not surprised, right? I've actually dove into a working group, I'm talking about software, I look into tooling on purpose, I'm expecting to go to GitHub, right? And then I come here and then I've got lots of tool, lots of documentation stuff. So that looks pretty good. That seems like a clear pathway. I think the one thing that I would say in general, and I don't know, everybody's got their own feeling about this thing, but when we did the last refresh stuff of the operate first site, we went through this thing about putting the word docs up there. Like people do sometimes expect to see that. So I don't know if that matters as much or not. That may again be an example of where some of the 10 year old worksheet thinking. So let's take a look at another project. Someone's got another, another one in mind. Yes, by my home keys again. UNIK. I think A, T, A, F, T. At least that has the doc's item there. Yeah, okay, I see. Got it. Okay, great, Unicolonial Development Kit. Sam, bam, perfect. Okay, so what we did documentation, we could do that one again. Is there another, would there, I mean, I'm an Unicolonial Development Kit. If I'm at this point, I'm, by turning up, I mean, this definitely is right off the bat, is, you know, I mean, it's positive compatible. If you don't, you know, like, either you know what positive compatible and it matters to you or it doesn't, right? Like, so this is, but at that point too, I wouldn't necessarily, I wouldn't, I would say that the, my first instinct just catching the page here is that it's doing a good job of reaching out to the people who's trying to reach out to it is, and there are people who it's not trying to reach out to it. If they get here and feel a little scared, maybe that's okay, I don't know. And it's the curious they can dig on. We want them to feel welcome no matter who they are, but at least to be a little bit more cautious, right? So that's okay. But it's still friendly and I like that, you know, it's look, we've got the, you know, we've got a koa like on doing things, so it's not, I mean, you're all good, okay. And there's a quick start, I love this part. I mean, you know, not to be, I'm a doc's person, right, I love quick starts. And, and my brain just went sideways. What did you suggest that we look into? By even looking, everyone's gonna make you. That was my thought was to think a little bit about, yeah, to look into, actually, maybe how about releases? Because, I mean, so let's do, let's take a look at docs really quick in releases as well. Just a quick overview of what's going on in the release page and how that is, okay. So you can see all those things, you got that, and that features, bug improvements, okay, so release notes. They've wrangled many of release notes. I want a big fan, okay, cool. Good. And it's, and does this do these happen to, oh, okay, they go off to the end of it, awesome, okay, great. So, yeah, very detailed, and we're getting right into there. So, yeah, cool, okay. And so getting into, am I getting started, okay. Oh, just, I'm gonna, I mean, this is my, this is one of my favorite things in the whole world to catch, and I'm just gonna do it because you use the word simply. So, I would literally, I would be throwing in, just simply with this right here, because of that, I would go over to my worksheet and I would say, you know, be careful of words and terms that might make a reader feel less than. I think it's a simple way where I put it, to feel less, I'm like, oh, I'm not the person this is for, because it's simply something, and I've, I simply, I don't even know what this means with a pip, isn't that, that's that little, when you're playing cribbage, is that what the little thing is, like the pip? I don't know, so, and I'm only, you know, but yeah, I'm a documentation person, so I get to like, yeah. And I tell everyone to get to the one from me, so I, you know, and just is another one, I will, when I'm done with a document or when I'm getting someone, sometimes the first thing I'll do is I'll just do a word search for just, simply, easy, any words that kind of catch that, usually just can take them out or restructure it. But yeah, again, that's the kind of thing that if you're, and if you're, sometimes when we're doing project reviews, we'll have a documentation person who's doing the documentation reviews, so you get a deeper review in an area, you get somebody's particular, you know, businesses. So I think I might be coming up with close to the end of my time. So was there, what is the end time on this 45 after? I've got two minutes to go here. Probably do my wrap up. Thank you. Thank you, sir. As always, thank you, sir. I know you're a sir, that's why I can, I can, I'm not presuming it. Okay, so, and then the lat, and then back over to the document in particular. Would you get familiar with the core concept? Cool, okay, oh, awesome, yeah. Oh, this looks really nice. Yeah, cool. I mean, very, very, very friendly to developers is my feel, very friendly to technical people. And yeah, cool. Oh, oh, interesting. Okay, yeah, cool, good. All right, I think we might, let me look at my agenda here really quick. I've got the call to action part to come still. I've got the, we're open to questions here in the middle too, I guess, because that's part of the live process of it. Is this working okay? Do we wanna try, we can try one more project? Yes, thank you, ohhe.org, like that. Yeah, so thank you. I had some, I had a little PTS responses when the first day I got here and my nervous system has been a little off, and it's probably like the whole sweating dynamic and stuff too, but so I'm still kitchen, like getting all the parts of the brain to connect together, but I'm doing pretty well today. Oh, thank you. Okay, so, where are we? Let's see. So do we have a, let's look over at the worksheet and see the different areas. License, health, outreach, code quality, activity. We haven't looked at outreach. What is there an area in particular that, so there's definitely a call to action right now. It's very, very, very, I don't like to use, I'm sorry, sorry to say targeted, right? Which is, it's a little, just, you know, it's related to shooting things, right? I don't want to build on that. I mean, I'm not trying to shoot the users, right? Who are we trying to attract, right? It's gonna be attractive people who know what's going on here already. Premier with this, with what this is, right? And maybe that's okay. But that's just, you know, that would be in my note about, first note about the call to action and the first outreach piece. And that can tickle the register now. Cool. And it's easy enough, of course, me to scroll down and here's the thing, right? So, I don't feel totally lost with that. Dude, this is good, because right here, I get directly into what we do. It's not assuming anything else, okay? I think the one thing that strikes me in here is that just as totally, maybe it's because I'm an open whatever nerd, but like this looks to me like we have, like the story here is an open data conversation, right? That's what's, you know, there's a, the underlying, whatever the open source might be, but there's an open data conversation. I do see the word data somewhere down in the middle of it, but data needs to be shared. I know there may be other things, but open health information, key part of that, you know, there's a lot of stuff around privacy and stuff. Like that might be, I'm not sure if that's all, not all, that might, you know, I might be just plucking that one out as being more quarter of the mission as opposed to an effect of it. But it might be, it's the kind of thing that I would like a code of conduct or something that if I was coming into somewhere that was going to be talking about health information, I'd want to know that they were right away approaching, giving me conversations about my privacy and about data, especially in an open data world, because I want some version of sharing some of my health data so that it can help science, but it doesn't harm my privacy. Okay, so let's take a look at what under the framework. Getting started takes me to the beginning, started the register, now separate from that. So we've got two calls to action, which is cool. The both, they're definitely different things. Now I'm a little, I'm not sure what the Getting Started's gonna do, okay? Ah, okay, cool. See, so it's reaching out, it's more, it's a gated end. So this is interesting, like I'm gonna get, my sort of like, yeah, this is another one of those, like I've got a different, I'm a person, if I'm in healthcare or I'm in a particular area that's something I'm interested in, I'm gonna either, this is for me or it's not, right? And that's okay, it's like you want, I mean another thing too is like, you're not wasting your life, it's not for me, I'm gonna go away, right? We're not wasting each other's time. So there's no harm about trying to make sense, it's not something that doesn't have to be for everybody. And it's okay to make that clear, I think. I'm not a web design professional, I'm just thinking from this, an open human systems perspective of people feeling welcome enough, they might, they go, oh, well this isn't quite for me, but interesting, and they file it away in their brain and they share it with somebody later who's into this stuff, right? I mean, this seems like, this is a really, you know, information seems like a really good, I'm having an easy time absorbing all the stuff right here and getting what's going on, I think. Principles, cool, awesome, open as an open, cool. And then this is my other impact stories and I was going to the getting started. Okay, that's what, this is the quality, okay, cool. I think that, I mean it looks like it's a, it's so far too many looks like, just on the face of it looks like a really good outreach approach. I would want to look at a little bit, I'm curious about things like the other bits that would go into would be things like what's going on, like looking at blog posts, how frequently are they going? Are they hitting a regular rhythm? Are they sporadic? It's better to have one every month than to try to make one a week and then not quite make it or something. That sort of theory, or one a quarter even, like just so that people know, oh, I'll come by a couple of times a year, there'll be a new blog. That's what you're thinking about. And the, and also social media feeds, like what's going on, you know, if you're using it, if you're using a strategy, is it clear that you're, that this is a curated feeders or something that is sporadically taken care of and that kind of thing. So those were the other things that were being flagged on that. And a lot of times things really, the footer is when they really, ultimately everything that's not in the top menu is going to be in the footer, right? So if I can't find something, like I still haven't found a code of conduct, for example, by doing my license. So it'll all be, I'd start, you know, if I can't find it there, you can be down here as the next place to look. Okay, so let's jump back over to, where was my presentation, here we go. Cool, let's jump back over here and finish out. So in the past I would walk people through that book and show them the chapters and tell them how to go use it, right? So today I took a different approach, showed you the worksheet that we'd use, how I'd go through and take it. I saw, you know, anybody who's been in the open source program office would think we've actually all learned how to do this process and it's really straightforward. So there's a lot that can be done out of this. You can do it with your own projects, you can do it for other ones. But really to me the most important thing is not that we write another version of the book. There's actually, we have chapters, parts of what we've written for the 2.1 version. If anybody wants to become a wrangler of writing an open source book, come on down. I've done it a couple of times, it's really great. One thing I keep doing in life is giving people the massive vision, like here is Middle Earth, all right everybody? And you're like, oh, we're gonna do something big. It's like, are you ready for that level of conversation or could it just be like, hey, back your pack, you're gonna go on an adventure, you wanna pack it back, back, let's go. Let's just take it like a chunk at a time. So I'm asking everybody to think about community stewardship, reach out to people who are in other communities, have conversations, have virtual tea, coffee, whatever, your favorite beverage, and let's just start to build some commonality and understanding from each other of what's going on. And reach out to people that are comfortable, that you feel similar to, reach out to people you feel different from, people, projects that are similar to you, different than you, people's life experiences and their identities seem different or similar. Just like, try three, something like that, not, I don't know, something. Give yourself a reasonable amount to do. So somebody you meet here at this event, I'm always available. I personally also really appreciate the triad if you have never thought about the versus two people, but three people, the dynamic of a three-way conversation works also really nicely over Zoom. I take my face out and just put two faces on the screen and I feel pretty okay with that. So and then just, if those conversations start to turn to anything, you want to be doing any stuff with it, we have a website at the opensourceway.org. We've got the forums, we can do more things with it if there's, you know, we can add stuff, if there's stuff we want to do to build practices and gather things as a community of practice, great, but let's be a community first and then get to the practice stuff second. And oh look, there's a meeting I'm not going to. I knew that already. And yeah, and yeah, I think that was it. So, and then go ahead and try out these processes. You know, this one, two, three, study and analyze, assess and report, then act on those recommendations. All of the resources for this presentation are at this link where they should be and if they aren't, let me know. I will give you my contact information on my cards and stuff. And are there any questions or we've got a couple minutes for, I think we have a couple minutes for a couple of questions? Yes. I will be doing some, I'm going down to the Red Hat booth on the Expo hall floor down there to be doing office errors. I have a bunch of cool open source way stickers on the smaller size that fit places. I can give some out now, but I'll be bringing the rest of them down there. So, a couple of minutes here after here, but then I'll be starting to push out to get down there. So if you are looking to connect or talk more, I totally get that and all that sort of thing. Of course, my image attribution is because we have, you know, open source, you know, and this, my favorite image of all of these is the Creative Commons image, the attribution image for this purpose that is itself a Creative Commons attribution image. And it requires me to mention the person's name. And so I've got it in here in the links of stuff. So all of the, all of those are in here. Sometimes it's a little longer. And I think that is all of my proper links. And that's it. So thanks for coming on this walk with me here today. I really appreciate it, everybody. Thank you.