 Thanks for joining us today. And welcome to Open Infra Live, the Open Infrastructure Foundation's weekly, hour-long interactive content series focusing on case studies running in production, open source demos, industry conversations, and the latest updates from the global open infrastructure community. We have some great content coming up in the next couple of weeks. And we hope that you can join us every Thursday at 14 UTC streaming on YouTube, LinkedIn, Facebook, and Twitch. My name is Kendall Nelson, and I am an upstream developer advocate at the Open Infra Foundation, and I will be your host this week. So today, we are streaming live and would love for you to drop questions as we discuss our topic into the comments section of wherever it is that you're watching this. And we'll try to answer as many as we can throughout the show. So let's get rolling. Today, I'm being joined by some really awesome people, many of whom I've actually had the privilege of working with directly. And I will let them introduce themselves, and then we can jump into today's discussions about mentoring programs and onboarding into the OpenStack community. First up, we have Victoria. Would you like to introduce yourself? Of course. Hi, everyone. I am Victoria Martínez de la Cruz. I'm originally from Buenos Aires, Argentina, currently in Madrid, Spain. I'm a software engineer at Red Hat. And I started on OpenSource because I was a really power user of OpenSource at a very young age. And I was really amazed by tech and how people share their knowledge in this community. So that's how I become a contributor afterwards. Thanks to Aricy. Nowadays, I'm working as an option developer for the OpenStack Manila project. That's the share of my system as a service for OpenStack and also wearing other hats within the community at Red Hat. Aikana Kumari, up next. So hi, everyone. This is Akshna. I am a competitions graduate. And I am currently interning here at OpenStack as an outreach intern. I have started my OpenSource contribution with the Haptable Fest back in two years from now. And now I'm currently here as an OpenStack intern contributor, so Ashley. Thank you, Aikana. Hi, I'm Ashley Rodriguez. I recently graduated from Boston University with a BS in computer engineering. And I am currently living in Boston. I started working with OpenStack through my senior design course. My project was to establish the foundation for Manila support in the OpenStack SDK. And we managed to push code for all the resources listed in the first two priority buckets in the spec. Currently, we have a outreach intern continuing what we started last fall. And I was also just hired by Red Hat as a software engineer. And I started in late June. Fatima. Hello, I'm Fatima Khaled. I live in Cairo, Egypt. That's where the parents are if you're familiar with them. I graduated from Cairo University majoring in computer engineering. I interned in OpenStack throughout Ricci in my third year of college. Kendall here was my mentor. And also, I interned in Microsoft around the same time as well. After graduation, I worked in the testing field of automotive industry for Belial for over a year. And then I switched. I'm currently working as front-end engineer in RISA for oil and gas, which is headquarters in Denver, Colorado. I was first introduced to open source in college. The whole concept of being open, sharing the code with the users, for them to maintain, customize, and solve the issues was just fascinating for me. I heard about some programs that support the students to contribute. And that's where I knew about outreach. And I found Storyboard to be the most interesting project for me to intern in. And that's where I did my internship. I also continued on contributing. I contributed in SWEFT, which is another OpenStack project. Afterwards, and still contributing in Storyboard as well. Currently, I have posed on contributing for a while, but starting my recent job and this hustle, but stable now, surely I'm planning to go back contribution. It's always beneficial, whichever career level, on both technical and non-technical aspect to be a contributor. Moving to Dawson Coleman. Yeah, I'm Dawson Coleman. I am a software developer at Lullsbot 3D printers. We design and manufacture open source 3D printers. We're based out of Fargo, North Dakota, USA. My involvement in OpenStack actually goes back to my time at North Dakota State University, where I was able to participate in the OpenStack Octavia project as part of my Capstone project, which is essentially where they throw out a bunch of projects. The students get to pick them. And we get to work on it for a semester to get some real-world experience. I thought the open source aspect was really cool, because now the code that I wrote is still out there. I can still go look at it. I can still go visit it from time to time, rather than it being locked behind a closed door. And Cloud Software is super cool. So that's kind of how I got involved. Awesome. Thank you all for your introductions. Let's jump into the first question. So I'm sure you all obviously learned a lot when you came to the OpenStack community. But what most stuck with you that you enjoyed? Fatima, do you want to go first? As a student, for the first time working remotely gave me a great sense of independence. Also, it was my first time diving deep into such a large code base. On the technical aspect, this gave me a great deal of debugging skills. Also, I learned how to navigate my way around the huge code base and fit my code pieces into it. And on the technical aspect, I have learned so much about working remotely and with different time zones. The time difference between us was about nine hours or something. So I've learned so much about that. Also, I really enjoyed working with different people from different cultures and different backgrounds with different perspectives. This added more depth and variety into my full process for both technical and non-technical issues. And finally, I really got the actual chance of meeting those people live and team gathering and in the summit as well. Anyone else? Something that was great about your experience? Oh, sorry. Totally relate to that answer. Like, I love it's being able to work in a community that has people all over the world with so many different cultures with different, like being in different time zones, remote, and all being able to, like, even though we have that distribution across the world, to be able to collaborate effectively. That is something that you cannot get elsewhere. And we are also developing very complex code. Like, we are basically doing software to manage data centers, right? That is key gas. And that is something I believe, like, in my case, I think that I wouldn't be able to do that in a specific place. Open source community is the only place I actually could find out. So totally relate to the answer, Fatima. I mean, yeah. I think I had a pretty enlightening hands-on experience with Git. It was a little hard getting started learning all those commands. It was my first time really working with it. And it was interesting, to say the least. A lot more confident in my Git skills now. But I think the greatest part of my experience with OpenStack so far is all the connections that I've made and the things that I've learned from my mentors. Victoria, she was one of them. Great help in getting started with Manila. Very generous with her time, very supportive. And that's something that I think Open Source community is very good with, is just always being there to help out the new contributors and just being overall the best community ever. Yeah, I think to echo kind of what they were saying is kind of the ability to work on a real-life product. Like this isn't just some toy program that you're copying out of the textbook. Like real companies are using this for real products. So that was kind of a big step up from anything that I had seen before in terms of the scale and in terms of like, oh, we have a complete test suite that we actually rely on. Like, oh, we're not going to let you merge if it's not pet bait, which are all great things. But if you're coming from an environment where that's kind of an afterthought or non-existent, that's a new thing to kind of wrap your head around. But it's great to see projects that are a model of that and be able to see like, hey, here are people who are putting all their stuff out in the open and you can just kind of learn from that workflow. So it's something that's really cool to be able to see and kind of model things after. I know I feel really cool knowing that code that I've written is running at like CERN and maybe potentially at Blizzard and all of these other companies that like you use every day that, yeah, it's awesome. So awesome to be a part of this community. So obviously there are tons of fun things that we all have learned of working in open source but what was the hardest part of getting started in the community? It could be technical or non-technical. Archana, you are the newest to the community of all of us. So do you wanna start? Yeah, sure. So hardest part of getting started was basically finding the right community or their project, which is closely matched to your passion in which you are completely interested. So when I found this and got into the Outreach Internship Program, the challenging part was about getting started was to set up the whole DevStack environment. But the whole process seems to be tough in the beginning but thanks to Victoria, my mentor who completely helped me and it was manageable at the end. And yeah, so this was also my first project with such large code base so making myself familiar was a bit challenging too. So yeah. Yeah, no, I think at the beginning of my journey into open source contributions, the biggest obstacle I had was gaining access to the right resources and to actually be able to contribute. Since my introduction was really through my university, I had a limited avenues that I could use. AWS was frankly too expensive for a college student. And it just was an issue also with my teammate trying to get some stuff with the MOC and it was just a lot of bureaucracy and red tape that we had to go through. And that was a bit of a hassle. But in the end, Kendall was actually the one to get in contact with the CEO of Vexhost and he generously provided us with some free accounts to be able to start and run a bunch of virtual machines. And then from there, it was just smooth sailing. So excellent work, Kendall. More of Vexhost and Muhammad. They were the real MVP there but happy to make the connection. I'd agree with Archana. The start is kind of tough because we learned from those hard parts but given I had both experiences on maybe parallel if I can say, open interning in open stack was showing such time flexibility and remotely working with open community on the other hand, I was interning in Microsoft which was a corporate which is a corporate with the closed source and we were working from the office. I found the open source facing some challenges about communicating with others with different time zones and working with people that I have never met. It was a bit intimidating but eventually after like breaking the first ice people are real friendly and they are they just jump to help whenever there is a question. They, you might never talk to this person before but they are just, what's your question? Let me help, log me and send me the logs and it's really nice there. So it might be or look like it is rough but it's just way to go. Anyone else have other hard parts about getting started? Well, we'll come back to it a little bit and a little bit later here but we can also move on. Obviously, we are a reasonably geographically distributed group. We have like Cairo and like a couple in the US and well, I guess Victoria you're in Madrid right now not down in Buenos Aires and Archana you're over in India, right? But yeah, so geo localization is definitely a thing and obviously we all come from different places and we're raised in different cultures and some of us speak different languages. Were there any parts of that? Were like a problem for you? Victoria, do you wanna go first? Having moved recently to another time zone. Yeah, so oh God, this question actually has many sides to it. Like I can totally see geo localization as being hard for many people. Like, well actually I saw a tweet the other way, the other day going round about how remote work is allowing people that is in distributed areas to join a tech field they want and start contributing and kickstart their careers. And I totally relate to that question. Well, to that tweet actually, like the whole cloud computing concept was quite new. It's like it was beauty niche technology. Like we were just starting there. It hasn't been so long ago, but technology is measured by dog ears. And that while computing at that moment was a more popular thing in US and in Europe, of course, but not so much in Latin America and well, I don't know about other areas, but I know that it was not so popular in Latin America. And actually being able to connect with contributors from other areas allowed me to learn about cloud computing at a very young age, I would say, and very early. But afterwards, like being there, it was really hard to find my next step. Like I finished my internship and there were not so many companies doing cloud computing, right? So it was like up there that I couldn't feel right away. And I totally see this happening in other areas in which maybe a technology is more popular and it's more adoptive in some areas and it's not so much in some other countries. And being in that some other country, if you have to be inside, it is not easy at all. Therefore, one side from the geolocalization aspect and for the culture and language barrier well, I still cannot forget my first OpenStack summit, it was in Poland. And well, I couldn't speak English as fluent as I wish. Like I was thinking in my head like, oh, you know how a smart I'm in Spanish, right? But I could actually communicate that to you, to the people that I have around. Unfortunately, I think the OpenStack community did a great job about that. Like usually like, since everybody takes into account about this situation, like everybody is very patient, everybody waits until you try to finish making the sentence and communicate your idea. I also implemented some other techniques in some cases like, I don't know, writing down stuff instead of actually speaking up. And that helped me a lot. And that helped me become more proficient in English, of course, and be able to be more connected, more engaged and move closer with the community. Which is already a community that moves really fast imagine if you get half of the information. So, I think that open source, remote work, there are things that are helping people, like very talented people to kick-start their careers and to reach to their next level, which is something great. I totally agree with Victoria here because given the current situation and how things have changed, the whole world is just heading to working from home and working remotely. This has been, okay, so after I graduated about five months or something, the pandemic started and everyone just were shutting things off and we need to work from home and we need to know how to work concurrently and sing things. My colleagues were, so they are seniors and stuff, but I have this skill because I have tried it before and I had the tools from my internship. So, it may have been a challenge but this challenge was just such beneficial and gave me a great edge in my CV and got me to currently working for a company with the headquarters in the U.S. So, it's really beneficial although it might be a struggle or a challenge at the beginning. So, totally agree. I know we as an open-sec community do as much as we can to make it welcoming in as many ways as possible. We, you know, list meeting times in UTC so that everyone has the same amount of pain doing the time zone conversions and we try to have everything text-based so that if you need like a translator, you can like, you know, pipe the logs through that. And yeah, we try to be as friendly and open as we can being an open-source community. So, we kind of touched on this so we kind of touched on some of the other blockers that you have but were there any specific technical blockers that you may have encountered? I know when I was working with Dawson on Octavia, DevStack gave the whole team quite a bit of problems if you want to talk a little bit about that. Yeah, I have never complained about DevStack before. No, so it was obviously, you know, it's a little more complicated than your little, like, hello world type-in-a-number script, you know, that you get in CSI 101. So it was really interesting when we kind of had our meeting and we were suggested that we needed about 16 gigabytes of RAM to run this and like, oh, so for our computer and they're like, no, no, for your VM instance and that's not something that everyone has lying around. I'm fortunate enough to have a computer that can do that but another guy on our team had a laptop with four gigs of RAM and that was his workstation. So there is the aspect of getting all that worked out. The computer science department at NDSU was generous enough to provide us with a pretty beefy server for getting that done but of course, you know, that also adds on the remote management part of that which was a good learning experience with some pain points but yeah, I certainly have to give a shout out to Michael Johnson here for patiently working through all my issues and my load balancers inexplicably not working and all the little things that came with that. I can't tell you how many times I just completely deleted OpenStack and reinstalled but we got there. I think a funny story with that is the thing that I was told to do when something didn't work was to start from scratch and we ended up getting throttled by the university I think because after installing it like once or twice, my download speed would go to zero. We never got that part figured out but it was certainly something that showcased just the welcoming aspect of the community and just how many people were out there willing to solve all our dumb questions so I think we really appreciated that a lot. Definitely just scrap DevStack and start over like people that have been working on OpenStack for five plus years that's definitely a very common MO we just like, yep, kill it, make a new one, it's fine, whatever. We can dream. Yeah, maybe someday. Anybody else have technical blockers that they ran into when they were getting started? Oh yeah, so my biggest fear about, well, eight years ago nowadays I feel more comfortable with it but it was good, like in fact I started calling it it's like it's a nunchaku. You never know when you are going to hit with it in your face and at the beginning I was really like a newbie like I didn't understand anything of what was going on and every time I had to execute a good command for me it was pure stress and fear that I was going to lose everything and I was going to, you know, I don't know start stepping on to some other people's job but it was like, it was fear I think thanks to my mentor, Shuli, she, I'm back. Yeah, I think we lost you for a sec, but you're back now. Okay, cool. So yeah, it took me a while and even now like when I see people struggling with it I really, you know, get in their skin and it was like, okay, I got this. We are going to do this and that and everything is going to be fine and that's how we solve things, but I guess Victor has done but I really wanted to build on that because I just was learning AngularJS to start with my contributions and I thought that this was the technical blocker that I have it's so large, a really huge good base but then I got the work done and I cannot count how many times I'm just on camera and I got pushed but I couldn't publish it I do not really know how it goes and then many times I got detached heads and many times she helped me oh my god, that was so much but I managed to learn that through the internship with mentoring, I got over it and now I'm killing it I just can't solve any issue that with any other colleagues so it's a really, really good journey that you cannot get anywhere else to know the process, the review and how to use the right comments so it's totally beneficial might be a little thing Yeah, Git is definitely not the easiest thing to work with in the world but I do think that Git review and Garrett is a little bit better a system than GitHub which I know is a controversial opinion but yeah it looks like we have some people David Medbury totally awesome community member he was talking about his Git and Payne's as well and totally agrees that Garrett is the best open source tool but yeah, thank you for engaging today on YouTube and LinkedIn and stuff definitely keep sending your questions in and comments and we'll keep showing them so thank you for participating everybody so for each one of you what is the best thing about working in an open source community obviously there are tons of things I have a lengthy list but if you could only pick one thing what's the best thing Victoria do you want to start? Sure, all right I think the best thing for me about working in an open source is that you get to work with the best people like in each technology like the most experts, the most experience and all my colleagues they all have so much experience and so many things to share that is something that it's something I appreciate a lot actually well, in some open infra summit I would run into some person and somebody else would say you know this guy, this is the creator of SEF and it's like oh god can I talk with him? it's like a super start to me and having that possibility is something you don't have everywhere so I totally see that's one of the most important part of being in an open source community What resonates with me is that you are free to choose what you're working on you just go find a project that's interesting to you and you genuinely care about either as a user or might be technically the technical aspect of it that you are interested in working on it's just not that it gets better because you see the future that you have worked on or initiated yourself in the hands of the other users as well around the globe anyone can use it as well and sometimes this user is yourself so adding a feature that you needed or fixing something that just was aching you it's just perfect also you always end up learning something new and it's quite about the output and the product and the difference and you just can't see it out there so it's perfect because next Archana you want to go next yeah okay so if I choose the best thing about being in an open source community then I can choose a mentor I started my journey with OpenStack with my mentor Victoria she helped me so much when I saw her tweet on Twitter she is finding someone for the OpenStack Manila project I just reached out to her and she helped me so much like giving me a way like how can I start with the project joining also join IRC communication channels and what I have to do next also assigned also helped me like choosing bugs to work on and the hardest part in that was like the code the codebase was in Python but like the support she gave me like understanding whole codebase and working on fixes that was like that's part like choosing a mentor helped me so much in that thank you yeah I think for me one of the obviously other than the aspect it's awesome to be able to work with so many like minded people I'd say another thing that was unique especially from the especially when you're able to do it as a part of a requirement for something else like for school or for work is that usually when you are doing that sort of work it's for some sort of proprietary need or purpose and you can say that you participated in it but once you're done with it it's kind of behind closed doors but the thing I think is cool about the open source contribution side of that is you kind of still have ownership of the code in a way that someone who's working for a closed source product definitely doesn't have so I alluded to it earlier but I can still go back and I can look at Octavia and I can see what I did obviously I don't run load balancers in my basement as of now but it is cool that in that aspect you know I still have some sense of ownership in that and I think that's something that you don't really get anywhere else you know I think my absolute favorite part about being part of this community is the community itself very collaborative very supportive I mean I literally spent hours talking to my mentor Gotham working out some differences between the documentation and what I was getting on my local machine and I just I have never seen that happen anywhere else where I can like work on a problem for hours if not days with someone and they're just there with you know any answers to what I like the questions I may have stuff like that it's just so satisfying to have someone there to you know help with a problem and then finally getting it fixed getting it done the sense of accomplishment that you get with you know working that and then with your team as well it's just amazing awesome well so comically enough Gotham actually just commented on LinkedIn and asked what is one thing you want to do to make the community more inviting to a new contributor like you so if you want to answer that Ashley can start or whoever if you have an idea I just say that you should they should people should know about the opportunities some pretenses are just need some digging to be out there so they are doing outreach for example they are doing great job about advertising about themselves and inviting people it has been to my to the extent of my knowledge it has been spreading more and more and this is they are achieving more getting to more audience so keeping that going is what will I think get more people to contribute providing the opportunities that the open source is already doing and just promoting that these are opportunities that are there that you can always just touch the code fix it and that's you did the new job and you did a great work and we are all supporting you it's just once you get in there you cannot go out it's just pulling them you know I have to agree there's I was in a unique position in that my introduction to this was through my university through my coursework so I never saw anything about hey do you want to join the open source community or this is what we're about or this is how you can get started I never heard of the outreach program until I had already been introduced to the community and then I would see all the information that's out there but I think getting more to share I suppose or just get the word out there is something that would be beneficial so doing things like this today hopefully awesome anyone else want to answer what is one thing you think you can do to make the community more inviting to new contributors like yourselves I think the sort of like outreach or just knowledge that it exists is a big deal because going into it I was pretty intimidated sitting down and looking at all the code like oh boy what have I gotten myself into but you know the part that made it you know really great was that all the people involved were actually really willing to help me I think I was told at one point oh yeah just ask me about anything even if it's how to CD into a directory so I think that's something that is super helpful as a beginner it's maybe not necessarily obvious if you've just never interacted with the community but you know once you know about that it really flows naturally from that I think especially in open stack awesome well looks like we got another question in here it's kind of a little bit more general but besides open source what led you all to software or technology as an interest and a career so actually the summer between sophomore no junior and senior year in high school that summer I did a girls who code program I was like seven or eight weeks and we touched upon you know just introduction to software we did some scratch we did some python we worked a little bit with a tiny robot and that summer was the best summer of my life after that I was like okay technology software development this is something that I want to explore that I want to learn more about that I want to work with and then that senior year I applied to a whole bunch of engineering colleges universities just hoping for the chance to learn more and do more in this field and I was lucky enough to get accepted to Boston University I completed my bachelors and I am so happy so satisfied so proud of this field like it's just amazing you can do anything and it's just great well for me I was like in my ninth grade we study computer we study coding with visual basic at that time so I had my little brother he was about four years or something I created a whole game for him about with photos and the names of what is in this photo and the feeling and the achievement of creating something from scratch and how it built up and how he enjoyed it was just amazing so I went searching and found that this is a major that you can study and since then I put it as my goal and my studying college to be and I graduated from it so I accomplished kind I can go next I guess so in my case all grades goes to my mom she is such a nerd like when I was growing up she would totally you know encourage me to do you know smart hacking scripts with the machine that we have but I remember it was an AMD K6 with very very low run and yeah I would spend some time with her learning about how to use a computer and after that I guess that which ended up kick starting my full interest in programming was like I'm going to say year 2000 I was 13 year old I think and IRC was the platform for you know making friends and meeting communities in my area so I would spend summers like just connecting to IRC and making friends and you know trying to learn about how to write plugins for IRC for the clients right and that kind of led me to open source as it is and you know the first GNU Linux distributions and well after that I started getting more involved and when I could decide what I wanted to do well obviously programming was something that was very interesting to me so that's how I'm here I should add my mom being such a nerd now she makes like she doesn't she doesn't know anything so I go there and fix stuff for her so so now you're geek squad you know yes yes every Christmas anytime go there you know fix her computer just about any time I go home my parents have like a laundry list of things that they need me to fix phones and computers and stuff so I can totally relate to that yeah no one knows how to use the printer but me well printers are just cursed I don't think there's much to that commutant about that well we still haven't heard from Dawson or Archana do either of you want to talk about how you got into technology and stuff yeah so it all started go out to Google so that's how I started my career in tech field and with that I joined some technical communities so with the help of that scholarship I started maturely in the frontend development things which I imagined so everything was like when I started frontend it's like I can build anything what I can imagine and the community there was like so supportive like whatever the help you need there are always so many people out there to help you also after that I started join some technical communities and arrange some workshops or events meetups and all so yeah that was quite interesting and that's how I started in my software development yeah for me I think like it was for a lot of young boys I think I can trace it back to playing video games and kind of saying like there's someone who could make this it'd be so cool to like have an idea and then bring it into reality and I think I kind of pursued that through just learning having opportunities to learning to program and all that but I think like as of today I'm not a game developer and don't intend to be but it was more of a matter of falling in love with the process I guess and sort of just you know being able to dive deep into something technical and just just being able to think something and then make it happen or just that kind of like first principles reasoning where you can if you know the more you know about something just being able to break it down and rebuild it better like I think that's just the coolest thing ever and that's kind of what's driven me through my entire career awesome yeah there are so many different ways to get into like technology and then open source but I'm glad we've all found our way to open staff together through different paths so maybe one final question before we start wrapping up here about advice so what is like one piece of advice that you would give to somebody taking their first steps and getting involved in open source or open staff specifically Archana do you want to go first again yeah so what advice I can give to future contributor like if you're done making the organization and your project make sure to read the documentation of that project and this is going to be your friend to your entire journey of the project and also once you are done picking some issues or business issues or your mentors are going to assign you some issues this is not going to be solved in one or two days this is the that's the learning process you're going to enter it's going to take so much effort and so much time of your year and it's going to be a learning process for you and if you get stuck somewhere reach out to your mentor and the community member and if somehow it's everything not things okay and you can also choose the stack workflow or some other developer forums yeah yeah you go ahead no I definitely make use of the documentation there is a lot of information out there on what tests have to be written the code style checks you have to pass just so much out there and then once you kind of know what it is that you have to do if you don't know where to start I would recommend looking at the code that's already been published look at what other people have contributed and see what their style is what methodology that they use what functions they write what they make use of what was going on how did they get to where they got and then just kind of use that write your own code and then ask someone to review it obviously post it to Garrett and if you're not getting the attention go to IRC and say hey I need a little help can someone pick this out for me and they will so definitely do that just cannot agree more with Ashley and Archana it's just you need just to start the advice to start is just to start dive your head first it's the challenge is how to start so just start clone the repo read the documentation of the how to build and you will definitely find the issue that you had in the documentation if not you will just go and ask someone ask on the IRC and you will always find someone in your time zone or out of your time zone maybe a while later but there's always someone who would answer so just dive with head first and the community will catch you I think one of the best tips that I received was don't be shy because if you don't ask questions you're not going to get answers and I think I'd really break it down into two different pillars of you know what it takes to have productive conversations with people first I'd say don't be shy and then second just you know value other people's time just you know make sure you're doing your due diligence with the issues or your troubleshooting as I know I it's easy to get frustrated and you know maybe I would just say like hey my load balancer isn't working just trying to you know that that little extra step of you know just trying to explain you know everything that you know and you know realize that there's another person on the other end who wants to help you but at the same time you know needs you know maybe some background or you know doesn't you know only has so much time in their schedule you know the cool thing about open sources we're all volunteering it our time to each other and I think so long as you know you you know you you're aware of that and but also not being afraid to participate in that I think it's really hard to go wrong regardless of who you're collaborating with really really good advice yeah Victoria I think you're the only one that hasn't answered yet yeah and so well actually my my advice is quite similar to the one that Dawson just mentioned like I think that contributing to an open source community teach you how to make good questions like you like time you will learn that considering that how busy is everyone in the community and you know how fast things move is like every time you hit an issue you try to summarize everything in a single line to explain what's going on with your with your environment and you go there you ask and well being able to do smart questions is definitely as questions in the smart way that's a different thing I hope that you understand me but that's something that is very a very good advice and related to that make connections don't hesitate on asking people like as mentioned like everybody is quite busy and there is a lot of things going on but everybody is willing to help and you don't need to be blocked in I don't know for one week with a single issue if you have people in the community that may be able to help you out and get you right back at where you want to be in no time and also those connections help you to get to your next place like to the next step so making connections learning from them sharing with them is very very important that is excellent advice as well it's all about the connections and our successful community because we like focus on communication with one another and open communication being one of the principles of our community definitely makes for a more successful resilient strong community and better software as a result so we've kind of talked a little bit about the outreach program but Victoria maybe you want to talk a little bit about the next round and stuff of course I always love talking about Orichi so Orichi is a paid internship that aims to bring underrepresented people to contribute to open source communities these internships last for three months and the whole process is that interns are paired with mentors which are contributors in the community and those mentors guide them through the whole process both in technical matters of course as we just discussed but also from the career side career advice and helping them make these connections that we were talking about currently there is a round that is ongoing actually Arcana here is part of that round and next round is going to be on September the applications open in September is due in October and the next round is going to be from December to March next year the goal for Orichi is to increase the diversity in open source and well after I think it has been at least eight years in OpenStack and probably more like before OpenStack it was only for the Genome community I think it's a bit more than 10 years I will ask somebody in the Orichi coordination to correct me if I'm wrong but after 10 years a bit more 10 years of doing this well there has been a representation from groups that historically it has been contributing to open source well obviously it's working because our panel here today is like mostly women instead of men like normal so Jocelyn you're in the minority today but yeah so aside from Outreachy we have the Grace Hopper open source day coming up in July it is a free all day hackathon that includes workshops the OpenStack community will be participating so if you're interested in getting started upstream I advise you look into the open source day all skill levels are welcome our focuses are going to be on like getting you started in the community getting your environment set up helping you push a patch to our test sandbox repository it looks like according to the website there are about 730 spots left but it is like a global event so I'm guessing it will fill up so go check it out if you're interested and then if you're not able to attend that or get into Outreachy or you're not lucky enough to have a community that works with OpenStack like Boston University or North Dakota State University we have other resources accessible all the time so we have the contributor guide which basically goes over all of the introductions basic basic things about getting into the community our structure our governance how to get connected to IRC and set up Garrett teaches you some get commands which we kind of talked about as being a little bit difficult sometimes and as you go through the contributor guide you have questions please reach out to anybody in the first contact SIG we have a link here that has a list of all of the people that are involved in that SIG and their time zone and also their IRC nickname so hopefully you can get to IRC but if not we have mailing lists that you can send to and be like help I need help and then we also try to do a training a like virtual lately because coronavirus but sometimes in person upstream institute and that covers everything that is in the contributor guide we have talked a little bit about running a virtual one later this year so if you're interested in doing that keep an eye on the docs.openstack.org and when we get dates they will be there so thank you so much to all of our awesome guests today you've been fantastic we really appreciate you joining us from all over the world if anyone in the audience has an idea for a future episode we would love to hear from you you can submit your ideas at ideas.openinfra.live submission deadline to be included in like an August or September episode would be this Friday actually July 16th so get them in next week we have another great episode lined up we have guests joining from Canonical and City Network and Morantis and also T-Systems to talk about current job openings company cultures and what they're looking for in candidates so if you want to get a job in open source you know building off of today's episode definitely tune in next week and mark your calendars we hope you're all able to join us at 14UTC for next Thursday thank you again to everybody joining me here today Victoria, Archana, Ashley, Fatima and Dawson you've all been amazing and we'll see you next week for another Open Infra-Live episode thank you for having us thank you thanks