GitHub Community, 7 Oct 2020

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: India Community Meetup - 06 October

Description

0:19 - Welcome address - Karan Venkatesh - Developer Relations Program Manager, GitHub
9:05 - Contributing to Open Source through Hacktoberfest - Peeyush Gupta, Sr. Developer Advocate, DigitalOcean
35:01 - Getting Started Contributing to Open Source - Richa Kumar, Sr. Director of Engineering, GitHub
59:23 - Road to CNCF & growing a contributor community - Umasankar Mukkara, Co-Founder, OpenEBS project
1:20:18 - Closing remarks and announcing next month's event

A

All right, hello, everyone and uh thanks for joining in today, I'm current and I manage developer relations for github in india. Sorry for the small glitch on the audio, uh I hope I'm audible right now and uh elsewhere, all right. So let's get started. uh So this is our second virtual meetup out here in india and we're going to be talking a lot about open source.

A

uh We have an amazing speaker, lineup today, so stay tuned meanwhile, uh do drop in a hi to everyone over there in the chat, because this would be a great place to connect with everyone else, who's like-minded and want to know more and learn more about open source, all right.

A

So a quick intro, uh how I mentioned um very passionate about devops, open source, etc, and uh like how I mentioned, I managed to have real uh here at jata, india, but I'm not into devrel devops and open source, I'm logged into books, acting filmmaking and other things, etc. So you can catch me on twitter or later over here in the chat as well.

A

So, moving on uh to give you a brief about, what's the agenda for today, uh we're gonna have three speakers uh share a lot about open source the journey and how you can get started. uh Firstly, we'll have uh pius gupta, who is a senior developer, advocate at ditch solution, talk about contributing to open source through hacktoberfest, and then we'll have uh one of our hubbard. That is richard kumar. Who is the senior director of engineering at github? Give you some tips around.

A

How do you get started, contributing to open source and finally, we'll have uh omar shrinker? Who is the co-founder of the open ebs project, uh which is also a cncf sandbox project talk about their road to cncf and how they were growing uh their contributed community, but before we get started there are some really exciting things that I want to share with you about. What's new at github, uh you might have come across some of these, or maybe you might have not, uh but let's go through it once again.

A

So, what's new at github, uh if you have tuned into our twitter uh feed or our blogs or other things where you know, we keep talking about how you can really use github to accelerate your workflows and also your software development. You would get to know how much of an importance that we have around security.

A

So recently uh code scanning was made available. So github code scanning is a developer first and a github native approach to easily find security vulnerabilities uh before they reach production. So you can enable it on your public repository and you can start playing around how you can use uh code ql for your code analysis, uh making it much more easier to catch bugs early on. uh So this is something that's uh that's new and has been announced.

A

Just kidding, uh you know, making it easier uh to code along and in track, so with that uh we also had the github cli generally available, uh so it has been in beta and then it's out of beta right now and available for all of you to use. uh So if you haven't checked it out now, you should really uh look at it, because uh this brings kit up to your terminal to reduce a lot of the context, uh switching and to create even more workflows.

A

So all the things that you've been doing uh through the github ui, uh most of it you'll, be able to do it using the github cli as well. Even things like looking at pull requests, reviewing issues etc. So you can just head over to cli.github.com and uh give it a shot. uh It's gonna be a super easy, uh a peaceful experience to just interact with github uh all within your terminal itself.

A

So for all of you out there um who are a lot more into the devops world and uh you know talking about uh containers and docker, etc.

A

uh Github container registry is in public beta, so the github container registry or ghcr uh allows you to seamlessly host and manage your docker containers uh either within your github organization, account uh or even your personal user account on github. So uh one of the real advantages of github container registry is: it allows you really fine grain control uh and managing the access permissions for all of your containers, so you can even uh specify that you want certain images to be shared only with certain people or not, etc.

A

So it's right now uh in public beta, uh so you can head over uh to github.com features packages uh to check out the github container uh registry. uh So during the beta storage and uh bandwidth is free and right now we support only the docker uh image formats uh so go and try it out.

A

And lastly- and this is something that's uh super useful, uh especially for me as well, um which is get a mobile. uh I know this was announced long ago itself, uh but it's it's something that uh you know makes your life as a developer or pretty much. Anyone using github so very easy, uh because you can do a lot of the tasks uh through your mobile itself.

A

uh I personally use it for reviewing a lot of the requests or adding comments or issues etc, and even notifications becomes so easier uh because you know you can get these notifications on your mobile itself uh without having to go to your uh get a ui. um So for those of you who haven't seen it or checked it out, uh go check out github mobile, which would give you a much more easy seamless experience of using github.

A

So there's a lot more uh that has come up or is coming up and in case you're not aware there is a public roadmap for github, so just head over to github.com and uh all of uh you know the exciting uh features uh around uh various uh parts of kitten. uh We have a roadmap over there, um so that's something which you can take a look at uh if you haven't seen already.

A

Finally, there is one thing which is fresh off the press literally- and this is uh you know specifically for all of us out here uh in india, and if you haven't seen this, um we are really proud and happy to support uh the times of india lost words uh challenge, um and this is a tech solutions challenge uh where uh a lot of us, techies developers, programmers, are invited uh to create a lot of the solutions uh that can help uh india find uh the lost votes due to migration, etc.

A

So there are some real, exciting uh cash prizes to be won and also some exclusive uh access to get a team etc. uh So uh this is an opportunity uh for all of us uh really to contribute to uh the growth and the development and.

B

A

It really easy for e-voting uh for this, as uh addition um so go, do check it out on uh toi lost words, challenge dot com uh and do participate, uh and uh that's that's about it for uh right now. So if you have further questions any comments, um you can uh talk to us on the chat we are out here uh to answer any of your questions.

A

So, uh let's move on to the first uh session for today uh and that uh is uh piyush gupta, so push gupta is a senior developer uh advocate at digitolution, uh who is really uh passionate about devops as well, and today he's going to be talking to us about uh how you can really start your contribution to open source or even find some of the newer projects to contribute to and start connecting with others from the community through hacktoberfest. So let's welcome push over to you.

C

Hi thanks karan, and thanks for sharing all the good things kitab has been doing loved the cli. I tried it out and it works flawlessly. Making 50 commits uh it might be a bit difficult task for a new person who is coming to open source. uh It might be an easy stuff for, uh for uh you, know, open source veterans, uh but when, when somebody is just starting with his open source journey, his or her open source journey, it might be a bit difficult for them to make 50 comments.

C

So we uh moved on to create uh to measure the impact in terms of uh opening pull request right and uh active office uh in essence created a platform uh where well people from uh you know. All all uh all sections uh can come together. People with different backgrounds, people with different skill, sets right people who have never contributed to open source.

C

They can come together, they can collaborate, they can start working and they can start contributing to open source right and open source is essentially made out of people like people are at the core of open source and uh oktoberfest. As a program has been able to provide a platform where these people can collaborate with each other- and you know make the world a better place to say last year we had around 700 events where a lot of people and lot of lot of contributors came together and you know start signing pull requests.

C

So it's not just about uh the numbers behind sign ups and uh you know completions and signing pull requests. It's also about creating that feeling of community right. And if you talk about pull requests, we had more than 480 000 pull requests last year, and these are all valuable requests right.

C

uh These are the ones that have been either merged or accepted by maintenance right and that's the kind of growth we were able to provide uh to open source uh in the month of october 2019, and we look forward to do more of that in 2020 right. So, uh let's talk about hector, boffs 2020.

C

This is an october long celebration of open source software and where individuals can learn, contribute uh meet other developers and they can contribute four pull requests to earn a limited edition t-shirt right now. I know uh the key part of that sentence, sound like earning a t-shirt, uh but trust me. That's not. The key part of that sentence is uh learning uh and uh you know contributing uh to the open source and also meeting uh other developers right.

C

uh This is what makes hacktoberfest uh what it is like uh you get to learn from experts all over the globe. You get to contribute to the projects you like, uh and the projects you actually care about to the communities you care about, and you also get to meet other developers all across the globe that you can, that you can collaborate with right.

C

One of the change that we had to make this year is uh since we are in this situation. Nowadays there are no physical events. uh We had to we partnered with mlh to create a platform for hosting virtual events.

C

We had updated event kits for all virtual event, organizers, because community is one of the core part of oktoberfest, and we all we wanted to provide a platform for community uh to come together to talk to each other, uh though we can't meet in person, but at least uh virtually right, and this year we had the september uh where, uh where uh sorry, where the grip owners and maintainers they can, they can get their repos ready uh for the contribution, because we have seen once the hector buffet starts.

C

There are a lot of contributors out there who are looking to make the contributions uh to the open source depositories right and sometimes uh those repositories are not in correct shape. They don't have the contribution guidelines or they don't have the uh issues stacked properly right. So we gave that one whole month uh for uh maintainers and repository owners to prepare themselves for the event, and uh one of the thing that I want to call out, uh we are doing this here. Is we have a big trees, not peas, option right?

C

uh We understand that uh shipping t-shirts all over the globe uh is uh pretty it's, not environment friendly, exactly right. uh This includes this increases our carbon footprint. So we want to offset that and when you complete the challenge, you get an option where you can uh plant a tree and for that we have partnered with an ngo called tree nation right and when you choose that option, we make a donation on your behalf to that ngo and they planted free right.

C

So uh if you, if you can uh please plant a tree and help us make uh the world a better place to live in right, and uh I would like to talk about uh an important change in rules this year right and uh this has been uh demanded for a long time- and uh we have listened to the maintainers and the open source community to make these changes uh to make hector fest better than ever. One of the biggest change that we have is hacktoberfest is now opt-in.

C

Right until last year, you could have contributed to any open source repository and your pr would have counted towards the challenge, but this year uh and then, if you, if your maintainer, didn't want their repository to be part of hectobuff s, they had to explicitly opt out right. But we have reversed the process this year. This year uh you have to explicitly opt in to the hacktoberfest program, or a repository has to explicitly opt into a hack to process program right and how you do that is.

C

uh Github has support for topics so for any repository that wants to take part in hacktoberfest. They can just add the hacktoberfest topic uh to the repository and only peers that are being sent to that particular repo would be counted uh towards uh towards completion of the challenge right and uh it's not just about sending the prs right earlier. We were counting openpr's as well, but this year uh we have changed it that pr has to be either merged or approved right.

C

An open pr uh would not be counted towards completion of the challenge right uh now we understand that this basically restrict the number of reports you can contribute to. uh Last I checked we had around 30 000 reports uh opting into the profess program, and um it might happen that you are. uh You are contributing to one of your favorite favorite project, right, uh one of the project or one of the community that you care about, but they are somehow not participating or due to any reason they are not participating in hacktoberfest right.

C

For those cases uh we have an option of adding a hacktoberfest accepted label uh and that works on an individual prs right. So if you, if you think your contribution is meaningful, if you think your contribution uh impacts that particular project in a in a better way, it helps in makes uh make that project better. uh You can uh request the maintainer to add the hacktoberfest accepted label right, so this gives maintainers a lot of power on uh on making sure that there are only valid and meaningful changes uh are accepted into their repository right.

C

uh We have also increased the review period it earlier. It used to be seven days now, had it become 14 days right and uh the deadline to do all of this is november 1st right. So, uh just to give you a summary or just to give you a run through of the new rules, your pr should be either. It should be in hacktoberfest, opt-in, repository and, if that's the case, it should either be merged or approved after the review period or during the review period.

C

If you are sending a pr to a non-opt-in depository, it should have an october fest label, a hypothetic accepted level right, otherwise that we are going to be counted right uh as actoberfest. We have been growing uh you know, year after year uh by our communities, and you know in sponsorships and everything uh so for 2020. We have two name partners this year. That's intel and dev uh intel is a big name in open source right. They contribute a lot of lot of code back.

C

uh That is a platform for developers to learn, and we have got a lot of sponsorship partners, one age at princess frequency as well, and you know uh we work with github uh to make sure that you know all of your contributions are safe and uh counts in account in a proper way, and we have also got a community partnership with mlh. Indeed, uh pro gate matter most to name the view right. Let's talk a bit about why oktoberfest? Why why we keep doing this right and one of the core reason of doing this?

C

Is we have seen when people come together when they collaborate with each other, uh when they, uh you know work with each other? They create awesome stuff right. There have been awesome projects that have come out of uh hector, buffett's, be it for internal use or be it for external use right. It provides a learning opportunity for for the newcomers or for the beginners in the open source journey. They can learn from experts uh in their in the specific projects. Right and uh maintainers also get a lot of help uh during top offers.

C

Right, as I said, oktoberfest is all about people and when you are running an open source project right, not all the maintainers actually get paid to maintain that project right. They usually have their day job, and then you know they have. They are maintaining an open source project due to their love of community or because it's an hobby project or it's a personal project could be any of the reason and they can always use some help. Right.

C

Hacktoberfest provides a platform where new people can come in, they can contribute to the project and they can actually help those maintainers right. It helps in growing real world experience where you talk to developers across the globe right and learn something new in the process, and uh hyderabad has proven to introduce people to free and open source. Software like uh there are a lot of people who have sent their first prs ever uh during hector buffers.

C

There are thousands of testimonial uh where people just started by sending their first prs uh ever and you know, rose till the level of maintenance as well, and the contribution is not just about code right, uh you can you don't have to go ahead and specifically add features uh to the project. It could be making the documentation better. It could be about writing new test cases. It could be just about.

C

You know, probably writing a blog each each contribution as long as the pr gets counted and we have had testimonials where people just started working uh over started contributing uh as part of hector fest and then you know they finally got a job right and when you are working with a project right, uh probably the company that owns it or probably a company that actually uses that open source project would be interested in your skill as well, and it has been, uh it has been proven, a good tool uh for the contribution letter as well.

C

uh There are a lot of people who started as a beginner and became active contributors, and there were a lot of active contributors who actually became maintainers.

C

And this also ties up to one of our distillation schools values. That's our community is bigger than just us. We have a tech stack based on uh you know, open source technology, and we understand that for our survival, uh sustainable, open source growth is, uh is one of the key points right and we want to give back to the community and we beat in way of court contribution, beat way of uh sponsoring open source events or open source foundations right or beat via hacktoberfest.

C

uh I want to talk a bit about my hector buffet journey as well. uh I started a two years back. I've got two t-shirts to prove that and uh my first pr was sent on. You know, I'm not sure if you can see the date. That's past october 2018 uh exactly two years back and I was a learning goaling at that time and I I was learning cloud native technologies and I wanted to contribute to a project that that that was in those areas right and I found out about open ebs right.

C

uh Oma will talk about that. He is one of the co-founder of the project and uh I found the looks like my screen is gone uh right uh and then that's how I made my first pr and it was not a big change. uh I just added a unit test for a method and it worked well right. uh It helped me talk to the maintainers of this project. It helped me understand how that project works and I must say, that's an awesome community right.

C

uh A lot of I mean I talked to the maintainers of the project and they helped me understand what the vision of the product is, and I felt like this is something that I can contribute to over a longer period of time, and then I recently became a mentor of that project right. So uh it took me almost two and a half or two two and a half years uh to reach at that level, but I I consistently contributed to the project I became a part of uh you know uh those the community discussions right.

C

I I talked to the maintainers and developers of the project right and that's what hacktoberfest empowered me to do now. uh That brings me uh to talk about hector, buffett's values uh and one of the biggest value is. uh Everybody is welcome right when you are contributing to an open source project. You will talk to people uh who are from uh you know different sections of life who have different background, who have different skill sets.

C

You might meet somebody who has never contributed to an open source project, and you also might see meet somebody. Okay, you know who has been contributing to open source. Probably you know 10 years 20 years right so uh just be kind to everybody, because this is a platform where everybody is welcome and the second one is the most important value I mean I, I cannot stress this enough. uh Why it's not about the quantity, it's not about the four pull requests that you sent.

C

uh It's about the quality, how what meaningful change you are providing right uh and, as I said, hector belfast is a platform where maintainers and contributors can meet. Now whenever you are sending a change, whenever you are creating a pr just make sure it has a meaningful impact on the project right and that way you get to improve your skills, you get to learn more, you get to, you know, uh become you get to become a better developer and also from the maintenance points of view.

C

They get a meaningful changes in their project right and uh don't just make it a short term action.

C

uh Don't do a shoot and scoot right, uh don't just send before pr's and disappear from the project whenever you choose a project, make sure this is something that you would want to commit to a longer term like when you, when you are contributing to a project uh check out their roadmap, understand what the where it is going right uh see if that aligns with what you want to uh what you want to do with your open source journey, and you know probably talk to the maintainers like talk to other developers like um chat with them on either on slack or discord or irc, whatever communication medium, they are using and then make sure that you stay there for the long term right make the hacktoberfest you're beginning for a longer journey, not just you know, for the month of october right.

C

uh So how do you get started? uh The first thing. First, you need a github account right, I'm sure I hope you have a github account. If not you can just go to github.com. The onboarding is pretty straightforward. You can get a account within minutes and then uh you have to register on hacktoberfest.digitalocean.com uh once you register with that. Get familiar with basic github operations. What are issues? What are pr's? How do you raise a pr?

C

You know what are labels? What are topics, those things and there are a lot of good resources available uh on the web and on the hacktoberfest website as well right and then you have to search for repos uh that have the hacktoberfest topic in that uh you can also filter based on the uh based on the language that you would want to contribute to. You might be a golang developer, you might be a python developer, you might be a c plus developer right.

C

We have got something for everybody uh and you have to make four pull requests to any of those opted in repositories uh between 1st and 31st october right and just make sure uh your prs meet the matching criteria right.

C

So whenever you are making a pr to an opted in repository, it should be either accepted or it should be merged right and if you are making it to an uh non opted in repository, uh your uh the pi should have a hectoberfest accepted label right uh and if a pro representative doesn't follow the octoberfest code of conduct, if you are sending a pr that is not a meaningful change, that is, uh you know, just you are sending it for the sake of completing the challenge.

C

uh The maintainers can actually mark that pr as a spam or invalid, and when that happens- and if you have you know too many of the mprs you we are implementing a system where you can actually be banned right and not just for this year, but for the coming years as well, and that is that doesn't help anybody right so make sure.

C

Whatever I mean, if you want to complete the challenge, if you want to work on your skills, if you want to make yourself a better developer, make sure you are only sending the meaningful challenges so meaningful. Yes right, uh I want to give you a run-through of what should be the do's and don'ts uh of the of the program writer of oktoberfest.

C

uh The first thing you have to send me as to the opted in report we talked about that. uh Do not send prs to the random repos out. There make sure whenever you are sending it, they, the maintainers and the rep owners have explicitly uh expressed their desire to take part in hacktoberfest right, read: contribution guidelines of the project right. uh Every open source project has one where they talk about. What steps you have to take to become a good contributor to that project.

C

Right, look for open issues, you might want to change something or you might want. You might want to add a feature you might want to fix a bug in that project and there are good chances that there would already be an open issue on that right and uh also there might be a chance that somebody is already working on it. So ah don't duplicate those efforts.

C

If you feel that there are some issues- or there is a new feature that can be used, look through open issues or you can open an issue right and uh talk to those maintainers uh talk to the project, maintainers uh explain them.

C

What exactly you would want to do right uh and once you have had this had that discussion when you have understood the requirements of the project and when they are uh when there are owners and maintainers, are satisfied with the approach, uh then you can start working on it and start signing a pr right.

C

So that's the ideal way or that's the dose of october first, that that's how it is supposed to yeah it's supposed to work right, but uh I'm sure you would be aware there are some people who try to game the system as well, and I would like to say that's one of the reason that we have new set of rules this year right and I'll. Just go over a few don'ts as well, uh don't send via pr fixing minor text edits, because that doesn't help anybody right.

C

uh If you mix, if you make a grammar change or if you just add a preposition or if you you know just add an adjective right, it's not going to improve your skills and also it's not going to help the maintainer as well. uh It would be a probably the the material would just be annoyed by that, and if he marks that as a spam, it won't the pr would be counted as well.

C

So all in all, it's going to be a waste of time right, so ah don't do that uh always send meaningful changes, always send impactful changes right. Most of the github repos already have good. First issues right: that's the label uh that is usually used for issues that are beginner friendly, go through them and these issues would actually help you. These are not complicated issues like you know, creating a new feature. These are minor issues that you can use. They help you understand the project and how you can actually contribute right.

C

So if you are looking for an easy way to get into a repository, make sure you go through the good first issue label and then uh don't send stampers. We take these things very seriously. uh That's one of the reason we have changed the rules.

C

If you start spamming any repository, you would be banned from hacktoberfest and then you know, um and it won't be counted anyways right, because in the end of the day, the power right now lies in the hand of maintainer right and if a maintainer thinks you are spamming, they won't accept those changes. They won't merge those changes or they won't put the heck to the fest accepted label and in all of these cases, uh if that happens, uh your pr would anyways won't be counted right.

C

So uh you would take the risk of you know getting a bad name in the community and also you wouldn't be able to complete the challenge right. So it becomes a complete waste. Don't do that and uh there, as I said, there might be cases where there are maintainers who don't want to opt in uh in oktoberfest and that's completely. Okay right, uh you might like that project right top and you might be contributing to that project and if they are not opting in hacktoberfest. uh That's that's completely.

C

All right right since hacktoberfest is not just about completing the challenge. It's about creating that platform. It's about creating that community, where everybody can come together and collaborate right.

C

uh So I I don't want to end it on negative note uh on just saying about don'ts, uh one of the one of the good thing about hacktoberfest is community, uh where you know people all across the globe more than 170 countries they come together, they contribute uh they meet right, so focus on that- uh and you know just focus on your skills focus on talking to uh talking to the project that you like that you care about, and you know it would be a good experience for you right.

C

uh So that's all I had the thank you for being a brilliant audience and if you like to get in touch there are some contact details there, be it on linkedin, be it on twitter, be it on email, and if you want to try out digitalocean, uh you can go to the link. That's do dot co forward, slash, oktoberfest hundred and you can get hundred dollar credits uh to try out uh dissolution, and you know all our services and products.

C

uh I'm not sure if I have time to answer some questions, uh but I'm just gonna take a couple.

C

uh I have a question. How can I add my repository so that others can contribute to it right? uh I'm just reading it up from the chat. uh How can I add my repository so that others can contribute to it right? So uh you can you can look for github topics. We have a very nice gif uh going on as well uh on the hector buffs website. You can just add uh hacktoberfest topic to your website and it would and whatever pr you send, that would be counted uh for towards the completion of the challenge.

C

uh How do you think of dealing with invalid prs right? uh As I said, uh when there is an invalid pr, the maintainers can mark that pr as a spam or invalid either one of those tags and as soon as that, pr has the invalid tag. It won't be counted towards completion of the challenge right. uh I've got just one more question.

C

I have made a pr2 and it accepted, but still it shows matured in some time in active fs profile. Is there something I missed right right? So we do have a 14 days of review period uh for all the pr's right, no matter if it's accepted or merged or anything right. So whenever you create a pr, uh it's going to be reviewed for 14 days and it gives a chance to maintainers to make sure that uh that your changes are meaningful and they are helping the project in one way or another.

C

So just wait till 14 days and if it accepted it will just show that you know that pr is a valid pr and it would be counted toward completion of the challenge right. uh So ahead, thanks karen, I hope I didn't take too much time.

A

Yeah all right uh thanks a lot uh pierce, and that was a good intro to uh hacktoberfest and also how people can get started contributing to uh hacktoberfest. uh Moving on. uh We have our next speaker uh who is going to be talking about. How do you get started, contributing to open source? What are some of the resources available out there uh and also give you uh some more insight as to how uh you can start contributing to open source in different ways, and uh it need not be even just code.

A

um So I would like to welcome our very own hubbard, uh richard kumar, who is a senior uh director of software engineering for the github ecosystem uh here at github, who will be talking about uh getting started, contributing to open source, welcome richard and over to you.

B

Thank you karan. Thank you so much it's wonderful to be here today and I'm really excited to be talking to all of you. So uh today uh I'm gonna be talking to you about the open source ecosystem and getting started contributing.

B

I think I'll be um emphasizing a lot of things that we use also uh talked about, and uh you know uh maybe getting a little bit more into the details of it. uh So before we begin, um I just want to start with a little introduction. uh Who am I uh so I'm richard kumar, uh I'm the senior director of software engineering in github, we're really proud to be a hubber.

B

uh I've been uh in the software engineering space for about close to 18 years building products and services that span various domains, uh some of them that pop up our identity and directory stint and mixed reality and devops, and as part of all of these experiences, I've had some great opportunities to interact with the broader developer community and I've always found that they have enriched the the the product and the services that I was working on and um and it's it's uh very powerful to be uh today in a place.

B

uh It feels very empowering to be in a place today at github, where I am helping in enabling this developer community. So it's really really deeply satisfying outside of work. I'm a running enthusiast I like to travel, which is on hold right now. Music have been dabbling a bit with piano and I'm into books.

B

So let's get started. um I want to talk about. You know where we are in today's world. uh Software obviously powers most of our experiences from daily activities to solving uh complex global problems and the heart of it is the developer community and uh today, uh technology, open source platforms, um open source uh and platforms like github are really um enabling a huge and diverse set of uh developers to sort of come together and collaborate so that uh they can build the software that you know the whole world relies on so um open source.

B

Is you know uh what what is built by a global team of maintainers developers, researchers, designers, writers and so many more people, uh and just to to to uh you, know uh put that in perspective. uh We see that on average, each open source project and github uh welcomed contributors from 41 different countries and regions last year.

B

So uh it's just a testament to some of the diversity that we see in the developer community and what technology and platforms are are able to do to bring these kind of diverse people together, and uh this diversity is um um sorry, is mixed up.

B

So this diversity is not just about you know where people are coming from or their backgrounds which it's also about the skills uh that they bring in the perspectives that they bring in, and so it's um this open source really uh enables uh us to share our ideas to build on top of each other's work and uh to build something great together.

B

So let's look at some uh inspiring numbers. uh We saw how we were bringing in people from 45 different 41, different uh countries or regions. Some other numbers that are um give us a perspective into you know how powerful the developer community can be and how powerful it can be to collaborate with each other. uh 3.6 million plus repositories uh today depend on each of the top 50 source uh open source projects.

B

So here's a great example of how people are able to leverage the work that is being done around them, and you know if you look at 350k plus people who made 5 million plus contributions to the top uh projects last year and, most importantly, and what we're going to be focusing on today is uh look at the 1.3 million plus first-time contributors that joined the open source uh community last year and made their first ever contribution, and so with that, I want to talk about um how each one of you can get the most out of open source.

B

uh How you can explore how you can be part of shaping the future of software, how you can work with the best in the field and how you can grow your skills and how you can help others. So, let's uh so today, I'm go the rest of this session. We're gonna talk a little bit more about. uh You know why uh why? Why should you contribute to open source? What can we get from it?

B

uh How what are the different ways in which we can contribute to open source, and then we'll also talk a little bit about hey? It can be quite intimidating when you're thinking about you know your first contribution.

B

um What are some guidelines or tips that we can help you with and what are some resources that you can use that will make this journey um fun and uh a great learning experience and a very uh enriching experience for you. So uh let's get into a little bit more detail of that.

B

So um why do people contribute to open source? So there are you know a few different reasons. Again. You just talked about many of them uh uh in to improve software. That you rely on a very natural way of getting into the open source um area.

B

Is that if you're already working on the software that relies on another open source component, uh you know if you stumble upon a bug if the source is available to you, it's easier for you to look at what's happening, perhaps even fix it yourself and uh contribute it back to the main brand so that everybody can benefit from it. That's a sort of a natural way of getting into a contribution mode.

B

Other benefits that you derive from it is that open source projects provide all types of opportunities, uh whether it's coding, whether it's ux design with its writing, documentation, testing, devops, organizing, and so it's a great chance for you to practice. All these skills, uh of course, you're gonna, open source, is all about the community, so you're going to meet people who have similar interests as yourself, and um it's it's a great opportunity to uh again learn from each other and, uh as so many people say to form lifelong friendships.

B

So um that's another major advantage. So, as you share projects and work towards a common goal, you'll find and as new people contribute you'll find that there will be a lot of need for explaining things. There will be need for asking questions for asking for help, so it really makes for great teaching and learning opportunities.

B

um Open source is public, so it's a a great way for you to build uh something of a public portfolio of the work that you have done. The contributions that have that you have made and to sort of make it like a living resume of. You know your skills and your capabilities, and more and more today, as organizations are looking to source great talent. uh These are the places that they look for to see.

B

um You know uh where you've made contributions and it's a great way for them to get more insights into your strengths and your experiences in addition to that, along with you, know, learning on the technical side, there is a great opportunity for you to build other skills like leadership and uh management skills. uh As you work on open source projects, there, you will be building teams, you will be organizing efforts uh around a common goal, you'll be resolving conflicts or you'll, be prioritizing work.

B

So again, it gives you these great opportunities to learn many of these uh additional skills, uh along with learning on the technical front.

B

So, uh let's get on to what's on your mind when you're thinking about it, let's say you're new to this, and you want to contribute and you're like okay. Where do I start? It's uh uh you know also overwhelming, or how do I find the right project or uh what, if I don't know how to code all right? That's not what I enjoy. uh What if I mess something up you know so these are.

B

These are all fairly valid questions uh but- and I think and a common misconception is that you can only contribute to open source through code and you'll, be surprised that there are various other ways in which you can make a contribution, so um you don't have to contribute only code. So let's talk a little bit more about. You know other ways in which you can uh make a difference.

B

uh So there are so many uh other ways. So you know, let's say that you know uh you like to plan events. uh You can organize workshops uh you can uh or meetups. You can um help a project to find relevant conferences or help the people uh the uh to to to participate in those conferences. If you like to write, you can look at contributing in the form of documentation, either.

B

Writing or translating documentation is such a critical part of a project that you know it can greatly improve how many users can benefit from the project from using the the the component or from or encouraging people to contribute to it. uh If you like or organizing you know, um you can um uh link to duplicate.

B

So you know uh we, we have tools like issues that help in uh creating uh ideas and discussions or uh tracking uh improvements to a project, and that can be overwhelming with you know so many people contributing so there's a need for uh somebody who can help triage and sort through all of those things. So if you're, the kind of person who's great at that, you could even contribute in that manner. If you like to design you can conduct user research, you can create a new logo.

B

You can help create style guides for a project or restructure the layout to make that component uh improve its user experience. So there's just so many different ways in which you can contribute. If you like helping others, you can be involved more in code reviews in writing, tutorials or in mentoring, other people.

B

And, uh of course, if you like code according uh then, you know there's just so many things you can do from finding an an issue uh that you want to uh address, to asking to write a new feature: automating project setup or helping with tools and testing. So this is just a a you know, giving you a feel for there's.

B

So many different ways in which you can contribute uh to an open source project uh so moving on, so we talked a little bit about why we talked a little bit about hey what are the different forms in which you can contribute uh beyond just code. uh So where do you get started? So there are a few um uh different places that you know can help somebody who's new to this to find uh ways in which they can get involved.

B

uh Github.Com explore is a place that will um identify based on some of the topics that you're interested in uh you know what might be some interesting uh projects. Repositories that you can start looking at or contributing to codetriage.com also allows you to filter um through you know, a various repositories that are looking for contributions.

B

uh Interestingly, you can also sign up for getting issues in mail in your email on a regular basis, and then you can look for what what matches your interests open source friday is a great place that has uh lots of great tips uh and and guidance for how to get started. I'm gonna cover a little bit of that uh right now um and talk through that.

B

uh So these are some of the places that uh you can get started so so what are some of the things you know that will help you or how do you prepare yourself like so we'll walk through open source? Our guide is a great place to get started if you're looking to contribute um and it it.

B

It has a a good, uh fairly detailed um set of guidelines on uh you know how you know.

B

Let's look at what a few steps might be, as you start to approach your first contribution, so you want to uh find a project to contribute to um again, as I mentioned before, sometimes this a natural way of getting into this is that you know you, you want to fix something in a component you're already using, and that takes you to the the source for that um project, and then you start looking at it, and you might be at a point where you feel like you might be able to fix it.

B

um You know so that's one way of getting into uh contributing towards a project. If you are looking at starting in a very different way, where you're just exploring um you can start with something small. No contribution is too small. You can start with anything that you notice, such as a documentation improvement, even something as simple as a broken link in the documentation.

B

uh uh 28 percent of casual contributions are documentation updates and they really really help improve. uh The overall project projects also have often have the beginner friendly issues marked in some ways. They might have a slash, contribute page that lists some of these simpler issues or they have. It might have a particular tag that you can look for to identify some of the simpler ways that you can get started.

B

Also as you're looking to select a project, you can look at some of the activity on the project. In terms of you know, uh um are the issues and the pull requests. How how active is the project in general? How responsive are the maintainers? uh How welcoming is the community? These are some of the other things that you can look out for as you're trying to pick and obviously you're going to look for something that matches your interest, something that you're passionate about, because that's what's pulling you towards that.

B

So there are some quick tips on. You know uh how you might go about finding a project. uh You know once you've found a project or you know interchangeably. The two things might go hand in hand, um orienting yourself to a new project. You know how do you, how do you get yourself comfortable with a new project? uh Each open source community may be a little different, but there is some common um anatomy. You could say of an open source project or some common vocabulary.

B

That would be good to familiarize yourself with you know what are what are maintainers? What are contributors uh there are certain uh standard documentation constructs like a license.

B

uh Readme, um you know what the contribution model is, what the code of conduct is, uh so it's it would be good uh as a first step to sort of orient yourself uh before you even jump into a project to understand some of these common terminologies um and concepts, um some of the common tools um that are used for organizing discussions and contributions, such as issues for requests, discussion, forums, uh mailing lists or chat channels. So what are the typical?

B

What does that open source community typically use for discussing their ideas, um understand the contribution model. For example? Are there specific templates you should use? uh Are there tests that have to be run? You know how do you contribute? So these are just some basic things that uh some which are very generic and some that would be specific to the project that would help get you oriented uh communicating effectively is extremely important.

B

um You know uh the open source community is so successful because we are able to collaborate with each other, and collaboration requires a good, effective communication. So some basic tips on you know uh communicating effectively uh giving context. Remember this is written communication so um again giving context to being direct uh keeping communication public. So you know so that you can actually derive the entire power of the community.

B

Instead of you know, doing direct email or messages do your homework in the sense that you know, if you want to contribute to a project, do a little bit of you know, understanding the project yourself, observing and learning before you contribute and understanding the contribution model being patient with questions uh and, of course, respecting community decisions and, above all you know, written communication can often be challenging when it comes to expressing tone. uh So you know do that extra bit to be respectful and you know to always assume good intentions.

B

uh We are all in this together. We all want to help out. We want the communities are usually really welcoming and very approachable, and we want to have that same behavior as we start to become part of that community opening issues and pull requests so again, there's some standard ways in which you would use issues and pull requests in open source projects. uh You know your um there is a sort of uh you could say best practices around when you open an issue.

B

How do you um inform when you have started working on an issue or if you um or you, can help resolve an issue even if you're not already working on it, because you know that it has been uh fixed in a different way um and- and you know so on so so familiarize yourself with how what the life cycle of issues looks like how is uh what's the best way to use issues to uh again um be productive in managing the project and in tracking the project, opening a pull request.

B

Again, there are some standard things you would do and again each project may have its own very specific uh instructions on the contribution model, but typically uh you you would fork the repository clone it locally, uh create a and connect it to the remote remote branch create a branch for your edits, and then uh you know an example of what uh one project may mandate is that you know you include screenshots of before and after your changes, if it's a change that affects ux, uh that you test your changes with a certain set of existing tests or that you also create the necessary tests that go hand in hand with your own changes uh and wherever possible, contribute in the style of the project to the best of your abilities.

B

So uh you know, as you work on different open source projects, you may find that um the design of coding guidelines tend to be a little bit different in all of these, so trying to maintain consistency and uh contributing in that style of the project as much as possible is uh also uh what we would recommend uh so uh and of course, at the end of all of that, uh you know um you will be able to submit your first contribution.

B

uh You know post that you may find that you may get feedback. You may uh may get rejected you may, or you may get accepted uh it's important for us to understand. uh You know again respect the decision of the community uh learn from what they are telling us uh and before, um and you know in no time you're going to be very successful in making that first contribution.

B

So um with that, I want to again sort of uh invite every one of you to join the community.

B

um To begin with, you know, follow some of the open source projects, uh there's nothing better than learning by observing and seeing how many of the open source developers run open source projects just follow that learn a little bit more about.

B

You know how people, collaborate um and um uh that'll give you a little bit more uh confidence in sort of making, taking that first step yourself build on great ideas, so one of the biggest uh advantages of you know open source is that you?

B

You have this problem that you want to solve, or you have this great idea that you want to implement, and you may find that somebody has uh uh also had a similar idea or they've solved part of the problem or something almost similar to what you're trying to do, and you don't have to start from scratch.

B

You can uh make a click uh clone off that repository uh experiment in your private repository, uh build on top of that, and uh you know, maybe uh get your idea implemented in no time uh and when it's appropriate contribute back to the community.

B

So um and then, ultimately you know you contribute your skills and you learn a lot along the way. So uh I hope that this has helped uh again uh re-emphasize.

B

um You know uh why it's um so uh valuable to be a part of this great developer, community, this great open source community and some of the different ways in which you can do it and also some early tips and places for you to get started.

B

Thank you again to everyone for being here today um and I'll be happy to see uh you know uh if we have the time um kind of. Let me know I have not been uh following the chat uh for the questions, but if you wanna bubble up anything, I can do that or uh whatever you say.

A

All right um thanks a lot uh thanks, a lot richard. I'm sure you know. That's that's something! That's really helpful, because anyone when they're getting started uh they want to know how and where you can get started. Where can I find resources who can help me etc?

A

So uh I I want to let you know all one thing that um right after our session here we'll also have a breakout, uh but all of us can come together and you know uh also interact with all of the speakers over here, uh so stay tuned um towards the end of the session, uh we'll let you know how you can get into the breakout as well, uh so we uh in the first two sessions.

A

You know uh the speaker spoke about uh hectoberfest and you know also how to get started with open source etc, and uh our next speaker uh is actually gonna talk about uh the success story of their own project uh and how they've been able to grow their contributed community and go on to become a cnc of sandbox uh project as well.

A

um So I would like to welcome uh obamacare mukhara, who is a co-founder of the open ebs project um and he'll, be talking to us about their road to cncf uh and also how they've been able to uh grow their contributed community uh and a few of the other things as well. um So welcome uma and then with you.

D

Thank you karen. I'm just going to start sharing my screen again. Thank you, karen and thanks to github for inviting me here. It's a pleasure to speak here on the github meetup for hacktoberfest.

D

um So to speak uh a little bit about myself, I go by uma mokara, I'm a co-founder and chief operating officer of my data.

D

We are an open source tech company that specializes in technologies on kubernetes and, as you must be knowing one of the main ways to build uh open source tech in the cloud native space is actually to develop this tech through cncf.

D

um So I have created two open source projects.

B

D

From scratch and build the communities around these two projects and we've taken them into uh the cloud native computing foundation, and that's exactly what I'm going to talk, uh how we started. What were uh the milestones that we achieved, and uh you know a little bit more about the projects itself.

D

um So about uh my data. um We are the fifth largest contributors in terms of pr authoring uh to cncf and, as you can see, the other four are very big companies being a small company. uh Having achieved this weight really shows our commitment uh to open source and open emails itself. Is um you know one of the most used uh cloud native uh storage or container attached storage projects?

D

uh We have a lot of expertise on kubernetes how to manage uh stateful applications on kubernetes and uh um much of our team are actually cks and uh we are last time this was written. It was 19, maybe now it's around 25, uh so we take pride in being part of the open source journey and that's part of our core business as well.

D

So a little bit of um how this project is doing, we found it open ebs, um as you must have heard from piyush the first speaker here. He was one of the early contributors through hacktoberfest to open ebs. We really found it in october. We just missed that hack to work fest.

D

uh We really started in 2017 for open ebs, but we've been um one of um the many projects which have actually built communities using uh hacktable fest right, so we definitely made use of it and uh that's uh thank you again for uh digitalocean and github and the community around it to have this program there. So today we have a lot of contributors, 90 plus, to be precise.

D

We started with our own team, and first contributors came in through the hacked over fest a little bit before that, but a bunch of them came in and the first actor got best and we actually now celebrate not just participate by actually running meetups every weekend uh and also um by uh dedicating some time for helping the new uh contributors succeed right so in terms of reviewing the prs or helping them raise quality prs. So that's! Actually uh we are proud of doing that.

D

So the other second project is also um in cloud native computing foundation. Cncf. We started uh around 18 19 months later uh in time around for the 2018 oktoberfest. Again there were many contributions that came in, and it's also growing very much as you can see that there are about 30 to 40 new users that are coming and using this project, and there are about 50 plus contributors.

D

Overall to this boring small. um You know one line, two line uh prs. If you take them out, you still have about 50 plus right. So that's a good uh statistic to show that we've been able to build good communities uh thanks to um github itself. You know it's a platform for open source building and thanks to cncf uh the community around it, there's a lot of chum going on right now in the cloud native space around kubernetes around other applications on kubernetes.

D

So how this talk was really not about. You know, details of how to contribute uh to active purpose or how to participate that was covered by push and why github and how things work that was discussed by the next speaker now, actually, as karen said, um it's more of a success story and uh how we actually went through uh the journey from uh writing. The first line of code in 2016 november december to actually uh you know one of the leading projects in the world with respect to container that has storage on kubernetes right.

D

So we found it on github this project and, as you can see, we have participated in three october quests and then um fourth, one.

B

D

A I'll be talking about. You know how to contribute uh to open ebs, prs and atmospheres after a few slides, but uh it took us about a couple of years to build the community. The initial communities where around community building is around writing good documentation and making sure that we help the early developers to come in and help them run. Open ebs, use, open, evs and contribute through small prs and encourage them to go uh for a more challenging prs.

D

So it takes work from uh project maintainers to work with these developers, and then uh you know, move them and then.

B

D

uh Part of the contributing community and then it it's it's a cycle and that adds up to itself right, and uh so we did uh achieve the status of cnc of sandbox around 2019 may and we're about to move to the next stage. Incubation is in progress and we followed a very similar experience.

D

You know I was a newbie in 2016 for open source, but by the time I created or co-created the second project in cloud native space litmus.

D

I felt like I already know how to do things, so it took us less time to achieve uh the milestone of getting into sandbox and build the community faster and, of course, the cncf ecosystem itself has, you know, grown uh a lot and github is more more much more popular right now so and as we can see, we have participated through the two hacktoberfest and we are now big time celebrating both the projects on um this hacked overpass and happy to say that we already received uh a lot of enthusiasm um towards both the projects and in fact we are finding it difficult, hey.

D

You know, like uh mentoring them, coaching them. uh On the first few days, you will see a lot of doc and uh small prs and uh those are great right and then we will try to get them to submit in a proper way that the project guidelines expect and then encourage them to move to. The next uh next appears. We do have the whole month and of course you know it's not the end of it.

D

uh You, the idea of um oktoberfest and open source, is to get started and then continue, and then you will be able to. uh You know, do a lot of things and why you have to do uh the previous sessions talked about it and, of course, uh you are really contributing to uh two of the most popular projects, most happening projects uh on kubernetes or cloud native space today.

D

So with that, let me talk a little bit about the two projects, as well as uh how to contribute to these two projects. So, first about open ebs, it's um it's based on converse law, which says that the architecture that is built by teams is really uh similar to how they operate right. If they are operating silos, you will end up having the application architecture in silos, but that's not what we want today right.

D

So what we want is uh you want a micro service applications that can run independently by a few team members that is cutting across different specialities right. So that's really what makes your application more portable in other stuff. So this is what we apply to open. Ebs and storage is a complex topic and storage is always the last area in which you store your data and it has to be more critical at the same time.

D

You should not, uh you know, get into the trick of um it: keeping keeping the storage as monolithic or getting funneled into storage, and that becoming a bottleneck for your flexibility or moving your application across kubernetes clusters in various cloud providers or data centers.

D

So the whole idea is: keep the data loosely coupled and let it be operated by loosely coupled teams and that will be suitable for loosely coupled applications, which is nothing but our new mantra for kubernetes right, so open ebs philosophy is build storage within containers and make it small in such a way that it is just serving the data for a given micro service right. So it's like building your enterprise storage features for a given volume.

D

Don't build an array like in the olden days right, so an array would be serving hundreds of applications, but here an array in open abs array will be serving one application and you don't need to tune your big array for hundreds of applications making it so complex. Now you can just you know you have the entire array for yourself and it runs within kubernetes. You don't need to know uh any specifics of your array if you know how to manage kubernetes, you know how to manage your storage right.

D

So that's the idea of container attached storage right so uh make it completely containerized make it specific uh tunable for a given application and let it move uh along with the application or let the controlling and scheduling of the storage be taken completely care by kubernetes itself right.

D

So the advantages of that is you're not really logged in into any cloud or a specific technology, and it is completely open source and you don't need to know a lot of storage level, knowledge or a specific arrange, knowledge typically, which is required to manage storage in the legacy world right, and this is the right architecture for high speed uh disk. That's coming out right. So sometimes your disk is faster and what's the bottleneck is the kernel right?

D

So you need to probably you have so much of cpu such a fast hard disk, and you don't have the software to run it in a way that you want, and probably um that's one of our architectural goals to solve and open ebs. My store really solves for it, so how to get started with contributions. We have a well nurtured, contributing guide and a lot of mentors available on slack they're on kubernetes slack, and you go to kubernetes, which many of you are already there search for open ebs.

D

You will find two channels, one for opening base, dev and another open ebs. Open abs channel is really for asking questions or helping people who are trying to use open abs, open, abs dev is what is mostly interesting for you. If you are trying to contribute and the project is actually pretty big, so you will see a lot of areas uh right from very basic docs to supporting multi-arc, and you know, if you're um an expert in this area- storage areas, docker nvme data protection, and then there is a lot of you know.

D

Our website itself is open and uh there are other uh javascript based development that we are doing as well. So, if you're a go and if your rest, our primary uh engine, my store is written in rest, which is one of the most happening languages right now for developers.

D

So if you know rust or if you want to prove that you can write a cool code in rest or you want to get started on rest, go to open ebs, my store and then you will see a you know, a bunch of opportunities to to help yourself and the project right so um as discussed by push, uh follow the active octoberfest guidelines.

D

So we have tagged the issues with hacktoberfest label and you claim it and you go raise the pr work with the maintainers and resolve the comments and will be uh very forthcoming to help you succeed in this prs right. um It's a win-win for us as well as for you uh and then, um of course, you know, it depends on what kind of pr you took easy one or difficult one. The difficult one may take almost like a couple of.

B

D

To do a feature, but we really want uh you know contributors to go deeper and deeper as much as.

A

Possible in the entire.

D

Month and after that as well, so that's about open ebs and the second project is a chaos, engineering, infrastructure or tool set project, and let me talk a little bit about why chaos engineering right, so you know kubernetes is uh happening now, and a lot of code is being churned from development into operations pretty fast right. That includes the kubernetes itself right. So a core infrastructure like kubernetes, is coming out every quarter, whereas something like linux comes out every 18 months right. So that's how fast kubernetes comes.

D

It comes in thanks to the great community and support from a host of vendors, as well as to the developers themselves right. So it's happening and then you'll see a lot of uh other um services on kubernetes um databases uh that are developing pretty fast. So if you are developing a kubernetes application or maintaining it, you really depend a lot on the resilience.

B

Of your app depends.

D

On a lot on the underlying stack, so typically most of the resiliency of your app depends on how stable or how resilient the other services are implemented on kubernetes right. So in order to make sure that your service level objectives are um maintained, you need to maintain a philosophy of chaos, engineering and that's where litmus comes in. You can use litmus to actually build a complex chaos, workflows which are predefined and pre-tested. You can just deploy them, automate them and you can start measuring the resiliency and then taking um step-by-step improvements from there onwards.

D

So it applies to the entire stack of applications on kubernetes and kubernetes itself. The platform and the beauty of litmus is. It is completely cloud native. It's. uh It has got a open way, sdk uh to write new experiments and there's a good community around it, and then you have a chaos operator or apis that will help. You run these things in a very cloud native way and there's a hub just.

A

D

We got a chaos hub where you will find a lot of pre-defined experiments which can be used to get started.

B

D

Then build uh more uh complex, workflows, so chaos portal is a monitoring um and workflow management solutions around chaos hub, and this is very much under uh development. If you are a webs web developer, you will find uh great challenges and opportunities to contribute to hacktoberquest through uh litmus portal, so how to contribute to litmus.

D

We made it easy again. The areas are if you're a web developer or any uh cloud native application developer or stack developer. You will find um an opportunity to develop a chaos experiment around that uh and we have actually integrated with another developer cloud platform called octato and for hacktoberfest we made it pretty easy to develop the entire experience.

D

If you want to set up litmus on octato, and you want to actually start running your development environment, it takes as much as you know, I'm just deploying right now, late most live on um octato, it's a namespace that I'm deploying litmus on and I'm ready to go right. So it's a pretty simple app litmus. Of course you can do a lot of complex workflows, but you all you needed uh to develop litmus and contribute and test. Your prs is right. There set up on update. It's a free platform. I guess so.

D

You can go and get started uh within a few minutes, um so not only that uh digital ocean and other good swag you get, and my data also gives a big price, uh maybe a couple at the end of october fest.

D

Last time we gave away one laptop now, maybe more, and this time you can actually get more details on my data blog um there's, a good blog that our team has written on how to participate, uh much of which I covered right now, but more details are there here and then some success stories around you can see. We are very proud of how we did the last meetups and again thanks for.

D

Watching so with that, um probably I'll take some questions. If there are some um back to you, karen.

A

Thanks a lot uh uma, uh there are a few questions, but uh since uh we are towards uh almost the end of the session, we can probably take up uh most of the questions together in our breakout. um So thanks thanks everyone for uh joining in.

A

um So today's virtual meetup saw uh uh piyush gupta from distillation talk about how to contribute to hacktoberfest uh sorry to open source through hacktoberfest, and we saw richard talk about how to get started, contributing to open source uh and uma mukhara talk about um their journey towards growing their contributed community and a little bit about their projects and how they went on uh to becoming a cncf sandbox project and also starting uh a new project as well. um So so now, let's uh you know jump into our uh breakout uh session.

A

uh You will see a link to join this uh towards uh the end uh now in a while, and uh you can hop in uh uh using uh that link and uh uh we can take some conversation uh further on uh over there as well. uh So thank you. Everyone once again for joining in uh we'll be having these virtual meetups uh frequently every month uh and we'll be announcing our next month's uh meetup.

A

That is for november uh very soon, as well, so stay tuned to our uh meetup.com group, as well as our twitter uh channel uh uh to be updated on um all the new uh events that we'll be having for you and also the programs uh and uh connecting you with a lot of the other uh open source leaders out here in india.

A

So thanks everyone and see you on the breakout side of the meet up for today,.