 Hi, welcome to our presentation for the Chaos Diversity and Inclusion badging program. With me on this project are Matt G, actually I'm Matt S, and then there's also Sala, my commenter, and Asta and Tola, who are my, me and Sala's mentees on this project. So you may be asking, how does a diversity and inclusion badging program come about? So there are two big components to this. The first one is the diversity and inclusion part of it. So we have an organization called Chaos, or Community Health Analytics Open Source Software, that we have put together at the University of Nebraska, Omaha, and now it's spread to a lot of other places. That diversity and inclusion aspect is one of the working groups, other working groups being things like risk or evolution. And that diversity and inclusion is something that's kind of hard to visualize while you can have a risk metric in a kind of built out way. You can put evolution metrics in software and make graphs about them. Diversity and inclusion is not as easy to put into action. And that is a very important part of why we wanted to build this badging program for diversity and inclusion, so that we could have some way that we could foster community health in the open source domain. The software badging section of the DNI badging is because we had a lot of inspiration from groups like the Journal of Open Source Software or the Core Infrastructure Initiative Best Practices Program, which is also a badging program. And these were very helpful in getting us off the ground. Their documentation was very stellar. So let's talk about how we did get it off the ground. So shaping the concept was one of the more difficult parts. We started with a repository that I created on my GitHub account. And it was just for documentation in the early stages of our work. It was a lot of writing. We rewrote most of what we wrote in the first place. And as you can see, we have a mind map that one of our mentees, Asta, had made for us. This is too much detail to show in one slide, but it was an example of how quickly this got to be very complicated. And our goal was still the same as it was before, to foster healthy DNI practices in the open source community. Let me talk a little bit about how this program, this application, submission, all that kind of stuff works. So let me talk about how we initially put that workflow together. So Chaos has a series of metrics that you can use to measure the health of an open source project. Those metrics are very useful in measuring, but they don't provide any objective reasoning of, this is where the green is, this is where the yellow is, this is where the red is. So it's really up to your interpretation on how to measure those. That's why in the badging program we really didn't decide to put that together in a way that we ask what their measurements are or judge how they measure things, our question is to ask is really are these things measured and how are you working on them? Like are you committing yourself to the measurement and the conformance of these metrics? So the initial idea was that both projects and events can apply. So a project would have to be open source. This was actually not a recommendation at this time. It was just any project or event. And I'll talk about their refinement later, but you would submit an issue on our repository to ask for a software badge. As you can see on the right, on the picture on the right, this was our initial table for the different types of software badges and the requirements that you would have to meet. These requirements were the metrics. So if you followed, if you kind of like followed and measured at least three metrics out of the five that we had presented, we actually would, we would put together a passing badge for you, put you on the list of passing projects, and you would have that badge to display wherever you wanted to. Our view system at this point was still under construction. So to find a place to host this information, we claimed the badging organization on GitHub. We actually, we actually ended up getting the organization slash badging. And there are repositories. I'm going to highlight the three numbers two through four. I'm going to talk about these ones. So diversity and inclusion was our main repository for diversity and inclusion badging. Under the badging organization, this repository was to provide documentation and information on how to apply for a badge, how the badging program works, kind of the things I'm giving you in this presentation. So there are also some repositories project and event diversity and inclusion. And these were useful in the submission process. This is where the actual workflow of the diversity and inclusion badging program occurs. So this, these are the, these are the important repositories right now because that's where a lot of the work is happening. And we also, I also want to mention that we got this far on our own, Saul and I, and then once we got our Google Summer of Code and our WG internships approved and we got those started, the project just exploded. It's been going a lot like faster the process has been since then. Let me talk about those mentorships. So we have Asta with Google Summer of Code and she is working on specifically the workflow process for the diversity and inclusion badging. These are the official names for the mentorships by the way. So that workflow process is moved forward a lot more now. I'll get to that in just a moment. And Tola is working with Outreachy and working with us. And he is developing a framework for internationalization, which starts in the DNI badging program and kind of expand, we're planning to expand it out to the rest of chaos as an organization. They've really pushed us forward in good ways and we have plenty of time left with them. And I just want to mention how much I appreciate Asta and Tola for their work with our organization. I really mean it like that. You guys have been great. Let me talk more about Asta's work first. So the revised workflow, the current version that we have now is that most projects and events can apply. Like I had mentioned before, we narrowed it down to that we need a code of conduct to work with. They need to be an open source project. Just some basic requirements, but it's pretty similar there. Instead of an issue, we have a pull request system where they answer questions in a document about, this is a good time to mention also that all of our workflow happens on GitHub right now. While we have some Google Docs, some HackMD, but a lot of that workflow is, especially the submission and review process are going to be on GitHub completely. So that's kind of like, if someone submits a pull request and they want to get a badge, they answer a series of questions with the template, and that template is going to provide them with the questions that, like, do you present family friendliness at your event, and are you committed to it, or do you measure speaker demographics for events, for example? So those badge statuses haven't changed much. They're at Pending, Passing, Silver, and Gold, as was before. But we also have the under review state, which is used for when a project is being reviewed by the reviewers of the project or event, and we want them to know that their badge is being worked on. And the review system with us is really taking shape. It's really getting, like, moving forward really fast. So the other one is for Tola's internationalization project, which I haven't talked much about yet. So this is for markdown-based translation that we eventually want to move to all of chaos. We've considered many platforms, mostly crowdsourced platforms, for translation, internationalization. We ended up choosing WebLate, specifically because WebLate has an open-source toolkit available, and they have worked with Chaos, a Chaos project before. They've worked with GrimoireLab, which is an evolution metrics visualization. It's kind of gotten pretty big. So building with Docker was kind of related to that open-source toolkit. We built this with Docker. Tola was able to get it working before we did. And we did a developer installation, too, in which we got an instance of WebLate running for crowdsourced translation. And we have more to report on that in the future. It's a work in progress right now, but it looks like we've gotten a lot done so far. So to make some remarks about the future of the project, we are having our mentees come around until August, at which point we really hope they stick around. And we are also working on improving Chaos metrics as we're working with Chaos on the project. So we have this set of metrics that I mentioned before, but we have this set of Chaos metrics that we follow, and we work with, and as you work with certain documentation, you know you'll find a kink in the hose every once in a while. So we have been improving the Chaos metrics as we go, especially for event and project diversity and inclusion. And we're hoping to be accepting submissions for this badging program by the end of the summer, which is really exciting. We've made a lot of moving forward to get that done. And I believe we will be making an impact in the future, and I'm really looking forward to seeing what impact we make. We are hoping to get a slot for Google Season of Docs. And we're waiting on that, but we are really excited to see if we are able to improve our documentation with that, otherwise we have people that are always willing to do it, too. And using the organization to... So this is an interesting point. We have a lot of potential for other badges that we could also run through Chaos. We have software badges for things like risk or value or evolution or even common metrics that we can make sure that people know that these are important things to follow. And using this organization badging for more badges is something that we want to plan on in the future. That's what I have for today. I want to thank all of you from everyone on the team, Matt G, Sala, Asta, Tola, and myself. And thank you for viewing our presentation. Oh, I apologize. I am so sorry. Hi, Georg. And Jason says thank you, and I appreciate your appreciation of the project. And thank you for letting us know you couldn't hear anything. So I am willing to take any questions about the project and answer any questions you may have and to provide any insight on the project that you have questions about. I guess it's all the same thing, but please feel free to give recommendations or insight as well on the project. I can talk about it for a little bit as well, too, if you'd like. So can people still hear me just to make sure that you can still hear me? I've got another. OK, just to make sure. So our project kind of grew out of the beginning of this year, and I'm just so happy to see that it's gotten so big since then. We've got so much, so many people interested in being part of the project is really what I see. And we're in the process right now, since the presentation, we've been in the process of working on getting reviewers to test out the process. And we're always interested in having more of those. So and someone else said thank you for a good presentation. Thank you so much. Matt, if someone did want to participate as a reviewer, how would they do that? Yes, that's a good question. So I think my email is listed on this account, or I also have a GitHub page that you can go to. It's under github.com slash badging. And if you want to participate on any of that, any of the badging process, feel free to drop an issue on any of the repositories. Our preferred is meta, M-E-T-A, and also sending an email works as well, whichever one is most preferable. I don't know if I can send a message to everybody here. Okay. So I am going to leave my email, someone asked about participating, so I'm going to leave my email as an answer to that question. And then we have another question from Georg, who says, can you maybe elaborate on the overall chaos mission and how badging fits in? Okay. Do you want to talk about that one, Elizabeth, or would you like me to talk about it? Sure. In case also, hi, everyone, I'm Elizabeth. I'm not Matt G. I'm Elizabeth. Matt G couldn't be here today, so I'm just filling in. And I'm relatively new to the chaos project as the community manager, so hi. It's great to see you all. I have a long history of open source. So I'm very excited to be part of this project. So chaos, what chaos aims to do is provide metrics so that you can measure and track your overall community health in open source. That's really the main goal. And there are different sections of that. So for instance, DNI is just one of those areas that we look at. And we do have a whole working group that works on developing metrics, peer reviewed metrics to answer some questions about diversity and inclusion in open source projects. The badging part of this kind of takes that a step further and lets people really show that these are something, these metrics are things that are important to them and things that they're working on and thinking about and actively measuring and tracking. And so Matt said earlier that we might expand that into other areas. So the other areas being things like evolution. So how is the project growing? Is it growing well? Are we active? Are we healthy? Things like that. So that's kind of how this badging program fits in. And it is for events and projects as well. There are some separate issues. Some of it overlaps, but there are separate kind of issues. For instance, like in events, as Matt mentioned before, we would look at things like event speaker attendance, like how diverse are your speakers? How diverse are your attendees? Like he mentioned before too, is it family friendly? So do you have things like a nursing area? Now granted, things are different with COVID. So that's kind of thrown a little wrench in the overall plans that we had before. But we're talking about how we would apply some of these metrics to virtual events, for instance, like this one. So these are all ongoing conversations and again, it's pretty new in the process. So we would really appreciate participation from whoever is interested in this stuff and wants to be a part of it and help us grow and evolve this badging program into something that's great and that people can really take and run with and apply for. I agree with that, yes. I talk a lot, sorry. I agree with all of it, don't worry. OK, good. Well, if you'd like to participate at any time, just feel free to send me an email. I'm sure some contact information is around here. Or on the question, I'd like to participate. I believe you have the answer available that has the information on how to get started participating. And Jason, you can also go to, so the main chaos website is chaos.community. And so if you go to that website, you'll see all about all of the metrics that chaos works on. And under the top nav bar, there's a little participate chaos.community slash participate. And that shows you, because we have open meetings all the time. It has, you can find where all the GitHub repos are for all of the metrics and all of the working groups. The diversity inclusion working group specifically is the one that does touch, obviously, does touch on the DNI badging. So take a look at that. We're always glad to give updates in the middle of the working group meeting for diversity and inclusion. And I think we do that almost every week now, because we just got so much going on. Someone says they're doing a badging project at Nome. Would you like to get in touch and talk a little more about that on email or, because there isn't much of a chat here, but I'm glad to learn more about that. I'm going to send you a quick message about that. Oh, you missed some of the, that's okay. Well, it seems like you got the interesting parts of it if you're interested. Hey, Matt, do you mind if I talk a little bit more about, like, why it would be important to show that badge on your project or your event? Yeah, and you can, yeah, I think I've been so sorry. No, no, I was just going to say you can completely jump in if I get anything wrong because I'm still pretty new to this project. I'm only like three weeks in. So I think I've been doing work with badging projects since I started working with chaos. So it's just, it's I'm so into it that I always forget that some people don't, don't, aren't, aren't very into it, you know. So go ahead. Yeah, I was just going to say. So I think it's important to signal to potential contributors or attendees or whoever you're trying to reach, users even, that, you know, kind of like what the values around the project are. So like if, if you can display this, this little sign that says, hey, diversity and inclusion is very important to us, that we, we track everything, we look at everything, we care about this stuff. And we've gone through this long application process, not long, but pretty intensive, you know, like we, it's not just like you fill out a form and you get a badge. Like there are humans that review this stuff and they, you know, the requirements are pretty strict, you know, that you really do. Like we, we look at everything and make sure that you really do can demonstrate your, your commitment to diversity and inclusion. So it's not just like an automated thing, automated thing. And so I think that that really signifies to, to, as I said before, to potential contributors or users that, you know, this is something you care about. And if they care, if they care about it too, then I think that's a really good way to show that, that this might be a good fit. You know, people are looking for projects all the time to contribute to. And I think that that can, can kind of enhance your attractiveness if you're trying to recruit people to come participate in your project or come to be a part of your event. Like that's just a little signal that can, can really show that you care about this stuff. So that's why I think it's important. Well, thank you for that. I think I started out thinking you have a badge because people look at it and say, well, that project has a bunch of badges, you know, like I'd see a project with a bunch of badges and I'd say they're, they're certified for everything, but I think it really matters like that you, that you care about the badges that you're getting and that you put the work in time to get the ones that matter to you. So I think, and we're always, we're looking to take candidates in like the next few months. So I'm always excited to hear about if people are interested in getting their project or event badge as well. So once the D-19 is really doing awesome work with this project, well done. Well, thank you. That might be someone that works on our project, but thank you very much for, for providing that, that positivity. And both of our mentees are here, which is nice to see. I appreciate you both, Austin and Tola. I may be telling everybody that you're here, but I think we all really appreciate that you are here. Someone says, have you had any concerns from a social perspective? I apologize. Could you elaborate on your question just a bit? I also look and I see so many people here that I have, there we go. Sometimes when people get upgraded, it could be used as gatekeeping. Ooh, that's a, that's a good point. So let me think about that one for a second and get right back to you. So I think what you mean, if you can correct me if I'm wrong, is that like when a project gets a certain badge or something, then they can kind of use that and say kind of like, we've got this badge. Yeah, human relationships are definitely complex. That's what they just said. And when you have, I understand what you mean by gatekeeping, I think, where there's a project that has a lot of very high level badging and they've kind of like worked their way to get that by just measuring the metrics. I think a lot of this, there's some subjectivity in getting the badge as far as to make sure that you're genuinely interested in measuring these metrics and that when you, if you have a gold badge, it's going to be really important to us that you are, that you have DNI as a priority in your project or event. And I understand that there's some, like, especially some self-report programs that where the system can be not necessarily gamed, but if you self-report and you're wrong and you get the best badge and then you come back and it's not right, then there's got to be checks and balances in place for that as well, which is something we're also working on in the workflow process. I appreciate that we've had so many inquiries as well. So if there's anything anyone wants to say too, it doesn't have to be a question. Comments and advice are always welcome as well, because this is a newer project. And I can say that I'm a newer person and this has been very interesting to watch the evolution of it and it's really exciting. You know, I'm really glad to kind of watch from the sidelines and see the progress that's being made. It's really a great time to join if you're looking for something to work on that. And if you care about this stuff too, I think it's a really good time. We got another inquiry saying that it means the standards of behavior need to be upgraded. EG with great influence comes greater responsibility. I think that using the chaos metrics was a big step towards, like, making sure that we have the right ideas in place, that we have the metrics we're asking people to measure are solid and established metrics. And we've been working on even improving them from that as we go. Because we found some, like I said, kinks in the hose that I said in the presentation itself. We have a lot of things that we have difficulty with with the metrics themselves. And then we make a pull request. It gets, you know, we kind of meet in the middle and it becomes a change metric. Someone says, Jonah Bacon just recently published some good content about making an award badging system that degrades over time to reduce power distance. What might your opinion be? Yeah, we don't have any, like, we have a degradation system of which after we're thinking a certain amount of time that the badge, I can't say what time yet because we haven't solidified that yet. But we have a certain period of time with which you have to renew your badge. I kind of use it to lose it as far as, or renew or to lose it is a better way to put it. And I appreciate all the literature I can get when it comes to badging. Because just like everything in software development, it's not as old as a lot of other systems for things like this. So I'd like to know a little more about that published content. So I'll have to look at that after this presentation. The badging system we were working most closely with was CII, or Core Infrastructure Initiative. We actually have their badging program integrated into one of our frontends, which is Augur, that we display metrics with. So we can look at a project and say there's a CII badge and what level, what percentage and things like that, that you can measure certain things about the project and get a high level overview of how the project is doing as far as Core Infrastructure Initiative best practices. So that was a big inspiration for us in starting the badging program and also just wanting to have a way to foster good DNI practices and to thank the people and the groups and the subgroups that put together these processes that foster good DNI practices in open source. That's a little long-winded, but it's hard to go to my head. When can we start to have badges? That is a good question. So as we're working on the review system, well, the review review right now in which we take temp reviewers and we are working on making the bots better, making the review system documentation better and improving the review system before we make it live, but we're planning to start putting out badges as soon as we have our review system in check, our documentation in check. And we have some hopes to improve our documentation over the next seasons. I'm not trying to hint at season of docs, but that's just coming up in my head. But we're trying to work on a documentation as soon as we start putting out at a refined level as soon as we start putting out badges because we have the documentation we need, but we also have some documentation we want to make it easier for people to use. So we're looking at the short answer. We're looking at probably the end of August, a little bit after that maybe, but around that timeframe. I have to keep myself from sharing all the documentation on both internationalization and the workflow process that we've been working on with our summer of code and outreach mentors, mentees. But that's very important to me. And I want to show all the latest developments, but it's still under development. And that's what development's about. So I have to wait on that until we start making more badges. Looks like the questions started to slow down. I'd like to encourage people to ask the questions they have. And I'm really excited to hear what people have to say as well. Sorry, Elizabeth, were you saying something as well? I was just going to say the same thing. So it's good. Yeah, I think with the 15 minute presentation, even though we had a lot of questions, it looks like it might be toward the end of the session here. I'm going to do. Do you think it's time for a last call for questions? That sounds good. OK. Just if you have anything else to say at the end here, if we have nothing else, I think that is the end of the session. I really appreciate this is this is a great opportunity to speak at the Open Source Summit North America specifically. I really appreciate everybody that came and I appreciate Elizabeth for showing up and helping out. Yeah, I just appreciate you all. We appreciate you too, Matt. OK, I think that's it then.