Non-Code Contributions

AMYJUNE:
So without further ado, you are in a session to talk about non-code contributions. This is part of a larger contribution workshop that I usually give at Camps conferences. I am not gonna go through the code part today. If you do wanna see the code part, you're welcome to join us on Saturday. And let's start. Who am I? AmyJune Hineline. I work with Kanopi studios. I am the Open Source Community Ambassador and QA engineer over there. I help organize accessibility talks in the broader accessibility community. I'm a core mentor for Drupal contributions. What that means is, I help out with Drupal con, I hope help out at local and regional Drupal events like MidCamp and Florida Camp and BADCamp. I'm also a member of the community working group community health team, as a liaison between like the mentors, and contributors and accessibility and kind of focusing on community health. I work at Kanopi studios. They are an open source website strategy, design, development and support agency. We specialize in data driven intelligence solutions.

And we're hiring all different kinds of positions. So hit me up. I think I'm the only Canadian here at MidCamp. But you're welcome to reach out through slack. And I live in a very urban community. And we have lots of people who make up our community. And it's very important to think about how our communities deal with racism. So I just want to make sure that our community stand against hate and racism. Hate against Asian American Pacific Islander communities have risen during the COVID-19 pandemic. And I just want to make sure that everyone is aware of that. So why are we here today? You can see this slide is divided up into two different parts. But we gonna like during this sort of, I'm gonna do like a little bit of a slide presentation, and then we'll just talk. But we gonna talk about why we contribute the benefits of contributing and then the different types of non-code contributions. And at the bottom of the slide really talks about what I'm gonna do in the workshop on Saturday. Which is really focusing more on that code part of contributions.

We'll go over issue queue etiquette, like kind of give like a higher level, look at what the issue queue is. We'll go over the old patching and review process. And we'll chat a little bit about pull requests on Saturday. So why contribute? You know, the guilt thing, if you depend on open source, open source depends on you. But more than anything, you know, your values, your contributions are really valued, like working with the best and brightest in the Drupal community. Everyone has something to contribute whether or not you're a coder or human resources or you know, a writer, everyone looks at Drupal in a little bit different way. So everyone values everybody. And then contributing makes you feel like you're more part of the Drupal community. Say you're going to camps and cons and you're participating in the hallway track and you're participating in sessions. But once you know how to contribute, you can go to contribution day, which is another aspect, you know, when you meet different types of people.

So it really makes you feel more integrated in that Drupal community. And then say you work for an Agency or a Drupal shop, and it's not one of their highest priorities, you know, and maybe you don't have the privilege of contributing on your own time because sometimes contributing back to Drupal is a privilege that some of us don't have, you know, you work 40 hours a week and you have a family to raise. So doing it on your own time just isn't possible sometimes. So, what are some of the things that you can like say to your agency? You know, about why they should give back? Again, back to that Drupal depends on sharing our knowledge, you know, because companies are consuming Drupal, because it's that free open source, you know, so they certainly should give back, you know, they should appreciate that value of helping each other and appreciating others and helping with it. When we all help when every agency helps, it really reduces that duplicating effort and redundancy sometimes, you know, if you create a patch for something and you give it back, that's one less thing someone else has to worry about that patches already created.

And in the tech industry, using and contributing to our open source software like Drupal is seen as corporate citizenship, you know, and it's part of our agencies and our Drupal shops, really, for lack of a better word, social responsibility. And it's good for talent recruitment, you know, it's fun and rewarding to work with those smartest people in Drupal, you know, and simply put the more those agencies give, the more that they'll get back. And this is really reflected when potential employees and partners view that agency page on drupal.org. So what are some of the benefits for us? You know, not just agencies, but why do we contribute, you know, it makes us feel good, you know, it moves the Drupal project closer to perfection, it gives you Drupal street cred, you know, people can look at your Drupal profile and see that you you actually contribute back. It can help build your resume, you know, you can use that as a point on your resume, you know, pointing back to your drupal.org profile.

I have to move because the sun's in my eyes. And really, the more you contribute, the more you learn, you know, I always tell people, I'm a non-code developer. But every time I work in the issue queue, I learned something. So I learned a little bit of code each time. I learned a little bit more about testing, I learned a little bit more about accessibility, you know, all of those kinds of things. This is an example of a drupal.org profile. I just like to use juries, because why not? You know, this is that part where you can kind of help build your resume. Right? You know, you can see there's a little bit of a bio, it has a little bit of a work history, you know, if he worked for other agencies beyond Aqua that would show up there as well. You can see how long he's been on Drupal, you can see he hasn't really worked on Drupal recently, but it shows his recent contributions and different, you know, core commits and things like that it shares his social links. This picture doesn't reflect it, but it shows mentors.

So, this is that part of that Drupal resume. And like I said, we're really gonna talk about non-code contributions, so different types of contributions. And I cannot stress this enough. Anytime I talk about giving back to Drupal, you can still give back to Drupal in many ways beyond code. And you can give back everyday of the year without ever having making a patch. That's something really valuable to think about in that. And I think that the mindset of some people think that it's always about code, but it's not. So there's a link here drupal.org community slash community contributor guide, and that may be antiquated, because I know that we're working on migrating a lot of the things over. So I reserve the right that that might be wrong. But there's this thing called the contributor guide, or the getting involved guide, where you can use filters and find your role in Drupal, you know, you can find a task, you can find what contribution areas to work on. And this just recently, I'm gonna use the word finished, for lack of a better word, but it just launched and so there's a lot of valuable information on these pages on how to give back.

And contributions can take all kinds of forms, external documentation guides, translations, sharing knowledge, extending Drupal through themes and modules, promoting the platform, organizing events and the issue queue. And I'm gonna go over some of these in like really fine detail in just a minute. Documentation, when I first got started with Drupal Easy, Mike Anello tasked me with improving documentation because I could never figure out how a module work from the readme. And I thought, who am I to contribute to documentation when I don't know what I'm doing? And it turned out I was that perfect person because I was able to evaluate the readme by knowing that there were steps missing. So I was that perfect person to fill in those gaps. And when you help with that documentation, it helps that next developer out or that next new person. So documentation is super important. There's different types of documentation. There are official guides, these are governed by maintainers in the Drupal world and they're held to a more rigorous standard through an editorial process that has to be, its curated.

And these guides include the Drupal user guide, Evaluator guides and Local development guides. Those Community Guide, these do not go through that sort of editorial process. They're pretty straightforward. You go to the guide, there's an edit button on the top, you hit edit, and you're able to make small changes. And this is community documentation that can be edited by anybody who has a drupal.org account. Someone of these guides include the Drupal Guide, which is that catch all for Drupal 8, 9 and later, you can find the Drupal 765 guides. But they aren't really I don't even think you can edit them anymore think they're static pages. There's developer guides, that's documentation for developers about tools, processes and standards, not specific to any version of Drupal. And then there's API guides. And they provide that general overview of all of those core API's. Contributor guides, in this section on the drupal.org website you find information to help you figure out how to bring your unique and individual skills and perspectives and join with others in the community to improve that software translation documentation and even community pages.

So this is more along the lines of, you know, event organization, how to find a task in the issue queue, things like that. And then there's individual contribution guides for individual extensions, like for the modules. These can be found in external documentation pages or internally within the repository itself. And that, again, is for those individual modules like meta tag or responsive images. So if you find something in the readme, you know, it's a little bit of code, but mostly documentation. And then there's always a need for contributions when it comes to translations. Some versions of Drupal only have incomplete versions of text and core, you know, for all the different translations. And for the most part, you know, all of these interfaces show up in English, you know, that user interface. Those incomplete versions always need corrections and improvement on those languages. I was told and I don't know if this is true, 'cause this was about a year and a half ago that no language has a complete set of translations beyond English for all of the contributed modules.

And then some of the things that you can do is you can review a translation, you can review new and updated translations by new translators, so they can be accepted into that localization system, you can be a translation monitor, and you can review new and updated translations making them either you can mark them either approved or rejected. So there's a few different things that you can do in that localization world. Sharing your knowledge, this is an important part of Drupal that I think people there's a little bit of oversight for. There are all different ways to share your knowledge, you know, there's presentations, there's mentoring, you can lead discussions, like what we have at DrupalCon at MidCamp this week, you know, birds of a feather sessions. And they don't always have to be about tech, you know, or they can be Drupal Adjacent. And then you can like lead trainings. So there's a few different ways you can share your knowledge. One of the reasons like I can attest to what I like to share my knowledge.

It builds my confidence, they say that sometimes the best way to learn something is to teach it. And every time I give a new presentation on accessibility or accessible media, or even this presentation I learn something new with each slide deck I create. You can be seen as an authority in your field. You know, helping build that resume again, it's rewarding. It really gives you a feeling of accomplishment to share your knowledge with others. In the past, I like to share because I like to travel and go around and go all the different places. And giving presentations and mentoring and training was just sort of an excuse to get to another town and another DrupalCamp. You're at that DrupalCamp. So you're learning you know, like I said speaking teaches you more. And then if you are a member of a traditionally excluded community, you can be a role model for marginalized and underrepresented and excluded groups. Because folks will look at the speaker pages or the trainer pages or the organizer pages and see people that look like them.

So that's just something to be mindful for. Different types of presentations. They're all different types. We'll see them all through the week here at MidCamp. You know, you can lead a panel, you can lead a BoF, you can lead lightning talks. You can do discussions and roundtables you can do how to and panels. All different ways that you can share your knowledge. You don't wanna give a 45 minute presentation. That's OK. You don't have to you can do a lightning talk or a panel. And where do you find these events? You know, there's Drupal, which is I think, being antiquated, but drupal.org has a new page at slash community slash events. And that's a curation of all different kinds of events right now. And you'll see calls for papers, you'll see meetups, you'll see trainings, all different things there. Which is a good segue into giving back to Drupal in the form of organizing events. There is a formal group for this, you don't have to join, but it's a good start to kind of get some resources and that sun is in my eyeballs again.

So let me just shift one more time. OK, the event organizer working group has its own Slack channel, um, you can reach out to me or like ABI or Kevin and we can get you that Slack channel. They meet the second Thursday, that information is not right, they meet the second Tuesday, monthly. And because of UTC world time, it really turns out to be Monday afternoons for us at like 4PM or 4AM. But they do meet once a month and kind of get together and talk about things. And you know, you don't have to organize a DrupalCamp, you can do a meetup, that's an informal gathering of people who are interested in your technology. And it's about building your local community. You know, I help organize San Francisco Drupal users group because I live in that community. Camps, those are technology focused events that really bring together that it's an extension of your local community. So I have San Francisco Drupal users group. And the extension of that is the Bay Area or BADCamp, where we pull together a little bit more people.

And then there's DrupalCon, you know, that's that continent level gathering usually meets for a few days or a week and includes all different kinds of events, contributions, keynotes, sessions, BoFs. And these are organized by professional event planners in conjunction with the Drupal Association or the DA. But they are always open for volunteers. They're always looking for people to help out with program selection, the different summits, you know at the higher ed summit or community summit, and they're also looking for people to volunteer. So there's all different ways that you can help organize events. What are some of the roles? And I'm just gonna read this slide because of ADA purposes. You can contribute with the website, either through code or through copy editing or offering. You can help out with marketing or the social media. You can provide trainings or do training outreach, you can help organize and select sessions or pitch sessions, you can help out with financing, you can help out with social events.

In more traditional times helping out with SWAG or print, you know, audio visual, you can coordinate volunteers, you can help with contribution days, their sponsorship wrangling. There's always a need to help with accessibility in all of our spaces. Also, it's really important to make sure that we represent all of our communities in our Camps and Cons. So diversity, inclusion & equity is a good way to get involved. And then there's the code of conduct, OK. So moving out of event organization, something else that you can do to help Drupal is promoting the platform, letting people know it exists. You know, what is it 3 or 4% of the web runs on Drupal? Well, you know, there's this little thing called WordPress that everyone seems to know about and it runs 30%. Imagine if all of us promoted Drupal the way that WordPress promotes their platform. I think the numbers would like really well not shift to 30%, necessarily but those numbers can really have the potential go up. And there is a group specifically working on this initiative.

You know, Suzanne Dergacheva from Evolving Web leads these efforts. It's called promote Drupal. They have presentations already made up for folks. So if you're part of an agency and you're pitching Drupal for a client. They have why you use Drupal presentations already made. But on the flip side of that, they also need help creating those presentations. They need help with social media, taking pictures of events and sending them to the initiative leads is a great way to promote Drupal. If you're at your local Drupal event, and you take some pictures, you can spread those pictures around. And you know, Drupal is really fun and having those fun pictures is a great way to promote it. And then there's always a need for the creation of new logos. So if you're a designer, or you know, you're very creative, drawing up new logos for the promoting the platform is a great way to get back. Let's see, there's a marketing role. You know, let's say you're a marketer. They're always needing someone to help, like write the copy, they need designers, they need videographers, they really need communicators in this space.

People who do a good job communicating, and leading and sort of those influencer roles. And I already talked a little bit about translations and localizations. But this slides more about that promote Drupal initiative because they need translations in that too. They need folks to translate the pitch deck, translate the user interface of their media. And again, they need you know, reviewers moderators and translators themselves. In the issue queue, you know, not only is there a code issue queue. There are different issue queues in the Drupal space. And reviewing content is a non-code way to give back. There's drupal.org site moderators queue, this used to be called webmasters, but in our quest for more inclusive language, we've changed the name recently to site moderators. So a few of these, I'm gonna list off [email protected]/project/ this one, site moderators. Site moderators is kind of a low key entry into reviewing content. It's basically participating in the issues that come up in this queue, providing guidance for some folks.

A lot of it is reviewing user accounts and reviewing things that were flagged as spam. Sometimes it's a little hard to get in there and start but I recommend kind of going through the issue queue and reviewing it maybe a couple of times a week. And then when you think you get the hang of it, you know, jump in there, ask questions. Everyone in that space is super nice and super handy, and will kind of help you guide through those first reviews that you do in the issue queue. And it's a great way to kind of get to know the new Drupal community because most of these people who are asking for content reviews on their accounts are new users. So it's a great way to meet new people. And then there's the link is wrong on here. But there's drupal.org content Q and this has all different kinds of things. This is book listings, reviewing case studies. Agencies will request case studies for front page promotion. Hosting accounts will ask for approval organization profiles, don't automatically get put on the Drupal listing page.

They have to be reviewed by people you know, and different camps and different blogs will request access to RSS feeds through Drupal planet. Organizations will ask for their organization pays to be listed on trainings. And again, all of this stuff if you review the queue and just kind of go through some of those past issues and familiarize yourself with what other moderators are doing. It's pretty straightforward. And there's also documentation pages involved with this too. But you know, you're a non-coder, you wanna give back you have an hour. You can spend some time in this content queue and, you know, perhaps approve a couple of case studies in that time. And this issue queue is very very long, there is a backlog of organizations waiting for approval, there's a backlog of blogs that wanna be on Drupal Planet. So this is a spectacular way to get some of those organizations and individuals, you know, getting started in Drupal. There's different community initiatives. We hear about the code initiatives, you know, we hear about, you know, the easy out of the box and the decoupled menus initiative.

Well, those are more of that code. Moving the Drupal code forward, but there's tons of community initiatives to here's some of the the community initiatives. You know, there's the Bugs Smash initiative. This is the initiative to fix known bugs in Drupal core. The non-code way to participate is that they need lots of help with documentation. They need help with issue, summaries, you know, issue, summaries need to be updated, you can contribute to accessibility. These issues are important for both end users. You know, our site visitors who use screen readers or you know, use alternative input devices. And it's also really valuable for people who are building Drupal sites as well, because remember, we need that back end to be accessible to folks who use that same software. So it's not only front end accessibility, but it's our back end builder experience as well. Drupal 8 or Drupal 9 experience, we really wanna improve our content creation tools for Drupal 8, you know, we really want that UX experience to be good, right?

You know, we don't want people to walk away because they can't figure out how to use layout builder. There's the documentation initiative. You know, I talked about this earlier. They have their own working group called the documentation working group. And it ensures that Drupal has excellent tools and procedures in place for documentation. And Drupal ladder, this is getting active users on drupal.org to contribute to Drupal core by having issues sprints, or our learning sprints. And a lot of these are at Drupal user Meetups or Camps and conferences. There is the Drupal recording initiative and Kevin smiling, he's on this on in the attendees over here, but there's always a need for someone to help out with this, because Kevin can't go to all of the camps, you know. So, outreach, you know, once the videos are up on or once the videos have been collected, you know, editing those videos, editing the videos for closed captioning, things like that. Providing camp support, you know, helping marketing the initiative, you know, providing documentation, you know, making sure that the next people who go to a camp know what to do, you know, make sure there's no holes in that documentation.

And I have some words from him, that he's not the only person recording the sessions, but he's definitely the loudest and most prolific again, those are Kevin's words. His tweets in siloed camp YouTube channels are not optimal for the greater community to find content. He just doesn't have that bandwidth. You know so again, aggregating content from all of the events including DrupalCon, you know, curation and content authors to annotate various versions of the same talk, because some of us give the same talk, but it might be irrelevant the next time you know, but making sure that folks know that in the notes in the YouTube comments and things like that. You know, adding tags, you know, so people can discover the content. Captioning and then you know, promoting the local events as well as the project itself. So there's all different things that you can do with this recording initiative. There's the Drupal diversity and inclusion team. This group welcomes all types of contributors as well programmers, content managers, project staff.

However you identify as a contributor and as part of the Drupal community. There's a place to get involved with this team. They have their own slack channel, it's diversity_inclusion in Drupal, slack, they have weekly meetings Thursdays at 9AM pacific time. And there's a few different ways that you can give back to this initiative. They have Resource Library, which is say you came across a good article recently, you can submit that, you know, they curate resources. They have a contrib team. They are a group working to increase code base contributions from individuals in those previously excluded groups. And they have their own specific channel as well DD&I_contrib_team. They provide session help, you know, say you want to submit a session to DrupalCon or DrupalCamp Asheville. You can go into their Slack channel and kind of give your pitch put your pitch in there and they'll help you with that. They'll have people that will help review your content and they need people to help do that as well.

And then they have the diversity and inclusion speaker initiative. You know Atlanta was on yesterday at MidCamp and gave a series of three workshops on how to become a better speaker how to write a pitch, how to write a bio. But, you know, that group can't be everywhere all the time. And so they're always looking for people to help out with those speaker workshops at Camps. And there is the community working group. There's the conflict resolution and Code of Conduct enforcement team. This area focuses on conflict resolution within the community. This isn't a really open space to get involved with. But currently, right now, they are looking folks to fill a role that is vacant. So that's why I have the conflict resolution team in here. They have a community health and development team. This area focuses on providing resources to the wider Drupal community. I'm a part of this team, we share knowledge and raise awareness and promote engagement on issues that impact the Drupal community. We're looking for subject matter experts, kind of global experts.

Some of the subject matter experts we have now or like we have a diversity inclusion expert. We have a mental health expert, you know, so we're always looking for different people to help us out with community health and engagement. And then for more ideas, there's actually an issue queue drupal.org/project/issues/ideas, there's an issue queue where if you have like, this little thing that you're always thinking about, you can pitch the idea in this issue queue. And there's all different kinds of things in there privacy, CLI tools, Composer, Olivero, which is now in Drupal court started out as an idea in this issue queue. So a good way to get involved is to kind of look at this issue queue. And if there's an issue in there that resonates with you, ask to collaborate, you know, give your input, things like that. And I'm kind of coming to the end of my curated part of the discussion. But I wanna remind folks that you can volunteer at MidCamp. We still have things open for tomorrow, you know, we're doing a non-conference.

I don't know too much about it. But you can reach out to organizers and pitch your idea for tomorrow. And we're all kind of like getting around and voting and seeing what things we wanna hear about. We're looking for room monitors. And we're also looking for organizers and volunteers for next year too. We do realize as a team, we're not as diverse as we could be. So please, if you know somebody who can contribute in a way or can collaborate with our MidCamp team, we would love more collaborators with us. And just saying this, you know, I need to pitch that DrupalCons coming up. There are initiative days, this is more in the code part. But each day of DrupalCon is gonna be sort of a half day of sessions and then a half day of contribution. So if you haven't been involved in code contributions, yet, this DrupalCon is a great time to do it. Because all five days there will be space for contributors. There are all kinds of mentors available. If you want to be a mentor, that's great too. And you do not have to have a ticket to drupalCon to go to the contribution half of the day.

So that's really important to know. Connect with me Volkswagenchick. And then just because we're at MidCamp our contribution day is on Saturday. And I will do this workshop but a little bit different where I don't talk about the community initiatives. But I talk about those code things like you know how to create an issue or work in the issue queue, some issue queue etiquette and reviewing a patch going over the old workflow. Which is still being used. But then Mark will come in after me and talk about the new workflow about merge requests. So that is sort of the end of the formal presentation. So I'm going to stop sharing my screen. And we have a few minutes just to kind of chat to, if anyone wants to share like different things that I don't talk about 'cause I don't have time to talk about everything, right? Or I don't know about everything. Anybody? It's okay that you don't share too.But...

KEVIN:
I would just add that it's important for everybody to realize the past life prior experience that you bring to this community outside of or possibly tied to what you develop. Because at my past job, that's why I learned video editing and event organization and so never did I think at that time that that would be useful as a way to give back to the community. Especially 'cause way back then the only published or publicized or talked about way to give back was through patches and issue queue. So I always felt like I was not doing my job. But I think it's, I can't stress enough the value of what your past experience can bring.

AMYJUNE:
..And this is true, because I'm a hospice nurse by trade and Volkswagen mechanic in a previous lifetime. And both of those skills have really helped me in the Drupal community. One, because when I realized that folks could make accessible websites and they didn't, that kicked in my hospice experience of working with people who would have to have their emails read to them. What a lack of privacy? You know, or the Volkswagen mechanic being the only woman in a shop helps me with the diversity inclusion group. Because I know what it's like to be that marginalized person that just gets kind of like, Oh, well, that's just, you're just a girl, you know, just move along and do your thing, you know? So that's really true, Kevin. Think Leslie's gonna say something.

LESLIE:
Sure, I can say something. Thank you, oh, I always join your talks, I've really appreciate what you do for the community in terms of spreading all this information. So I join them because I don't have time to keep up to date on everything, either. So have you go over all the new things that people can do, then gives me that information that I can then share with groups that I deal with? So I really appreciate the fact that you take the time to do this?

AMYJUNE:
Thanks Leslie. Yeah, well, OK so, back to that past experience, right. Like I'm a mom of two boys. And I homeschooled for a while because I lived really rural, that's sort of tangential, but whatever. But homeschooling like was really rewarding for me. And then being a director of Nursing at where I trained CNAs teaching people was really rewarding for me. And when I first got into Drupal that warm and fuzzy feeling of teaching people went away. Because, and I missed that. And so I worked for a company that gave a lot of like, community sessions and training. So I was like, what can I talk about? And they're like, well, you know how to make a patch? I'm like, heey, I don't know. That's the only thing I know how to do. And they're like, that's OK, because someone else doesn't know how to do that. And when I started doing that, I started getting that warm and fuzzy feeling again, you know, like, it's not just altruistic. Because it makes you feel good when you help people. You know, like, I can't stress that enough about, like, why I like, do what I do is because it makes me feel good when I teach other people and I know that like the Drupal projects moving forward, or whatever, darn sun, I think there's a cloud that like, goes in front of the sun and stuff, and I have this, well, you can tell it's venetian blinds.

The pandemic, like, has been this little corner of the kitchen. But, like that one thing that I knew, though, you know, like Kevin, like the recording, you know. Focusing on that one thing can really take you a lot of different places, you know, like I said, I only knew how to patch this the only thing that Drupal shop had me doing was creating patches. And it was like, I didn't think that that was valuable 'cause I thought, well, if I know how to do it, and I'm not a coder, then other people already know how to do it. That was my thought. And it was like, wow, and I met Leslie at NEDCamp and I did my first presentation on that, you know, and I realized that you can be in Drupal for 12 years and not know how to make a patch, you know what I mean? And so, just like, keeping that in mind that your individual skill set and experiences really can, like, help everybody out so. But not everyone's a public speaker. And I know that. But mentoring, Ellie helps with mentoring, you know, you don't have to be a public speaker to help mentor.

You can be side by side with someone, you know. And even though like I don't code very much, I have the toolkit on how to know how to figure something out and just helping that person through stack exchange or going in like using keywords, you know, my contribution to that, you know, it. You don't have to know how to know everything to mentor. It's just figuring out with somebody else, you know, and it kind of feels good when you're being mentored to have someone that doesn't know everything helping you because it's a group experience, you know, and it really, you know, just sort of it's more empowering that way, I think. OK, so I've done a lot of talking like maybe we can finish up and get two minutes back. OK, thanks Leslie and Ellie and Kevin and Sarah for coming. I appreciate you all.

LESLIE:
(CROSSTALK) Yep, thank you and your your recording will help a lot more people that may not have been able to come here today. So thank you, Kevin for doing that. All the recordings are so valuable to the entire community really appreciate that. But yeah, not a lot of people necessarily can come to all these zoom meetings and but having the recordings is awesome. So even though there's only a few of us, you're what you're saying well, will reach a lot of folks so thank you.

KEVIN:
Thank you, AmyJune

AMYJUNE:
See y'alI in a bit