 Everybody, sorry for the way I took the difficulties. All right, very quickly, let me talk. My name is Jason Meredith. I'm a staff software engineer at Procord. I'm also the lead and one of the chairs on Harvard Health. My talk is a four-quest welcome. We need this in a very nice way. So thank you to all of you who use your image. We'll decide that. These are our projects. And as was mentioned earlier, we've had a pretty strong increase in contributors to FIRO this year. Harvard City and Harvard Northwest especially, the rollouts have increased also. And you get a central review where we track membership and stuff like that. When you're contributing to open source, the first question is where do you start? As always, in my opinion and other opinions, documentation is a great way to start it. And a great way to contribute to DOCS is to try to set up your local environment. We've all seen some pain points in some open source projects to do that, and a good way to help other people is to contribute to documentation for that. Another little hidden gem that a lot of people, even very strong software engineers that I've met that don't know, there's a slash contribute URL built into GitHub. And if the repository has flagged the issues with a good first issue, they'll show up in this list. All of the ARGO projects have tagged the issues with good first issue. So if you're looking for a low hanging fruit issue to take on for your first contribution, this is a great place to start. But as always, if you have an idea or a contribution you'd like to make, make sure you go look at existing issues and pull requests and see if there's one you want to attach or maybe take on. So if there's an issue that exists but no pull request, you can grab that and go from there. The best place to communicate is the Slack. That's the link at the bottom. It's very active. The channels are ARGO-CD, ARGO-Wareflows, self-explanatory, and people are very friendly. I'm in the ARGO home one, pretty active. And we have many people here in the audience that are contributing to the others. If you do contribute often, there is a membership scale that you can go into. You start out as a member, you get nominated by two other people in the group, and you can actually get into the org and you get more focus into the system. Then you can become a reviewer, an approver, and eventually a lead. And that's kind of what I did kind of on the side with ARGO-Helm is at ProCore we needed it. We were at a Helm shop and it was a little bit behind, and Marco, the other maintainer, was pretty overwhelmed. So for the past 18 months I've helped out, I've become a lead, and we have a couple other people in the audience like Tim Collins who helps out a lot with the ARGO home charts. The other place to contribute and get involved is the calendar. So on the websites you'll find a link to the ARGO calendar and you can actually contribute to the community or contributing meetings. They're open to the community. Some of the meetings I think they're only the maintainer meeting. You have to be a maintainer to attend. But there's also SIG meetings like security and scalability. So if you want to learn more about the project just listen in. You don't really have to contribute, but you can go into the Zoom meetings and there's a Google Doc where they take notes what happened in the meeting. So all those links are available through the ARGO website. Here's the resource links, death by texts. This is Puka. Puka thanks you for attending. This was short and sweet. I wanted to thank the ARGO home approvers and maintainers and then the software delivery folks at Procore for helping. Especially call out to again Tim Collins. He motivated me to do this talk. So yeah, short and sweet. Thank you everybody. Oh, and this is my Venmo QR code. Just kidding. That's the feedback QR code. Please be kind.