 So yeah, however, when today we have the regular session for students. So if anybody is interested to ask any kind of questions about Google Summer of Code, about organization and the next steps, this is the place to ask. And yet today we don't have so many people on the call, so probably we could just start from questions. So I had a question regarding the Jenkins code. So it's like I see Jenkins is associated with cloud bees. Like you work there and Jenkins is provided as a service by cloud bees. So I wanted to know how is that association like how is that Jenkins associated with cloud bees? And another one what I want to know is like what has Jenkins primarily aimed at like early at enterprises or for everybody? Okay, answer the question. Yeah, this question pops up sometimes. But we can say that Jenkins is a great person. Maybe it's on my side. Okay, should be better now. Okay, so Jenkins is an independent open source project. Yeah, cloud bees is one of the biggest contributors to the project. Cloud bees offers some services like cloud bee, Jenkins support, etc. But Jenkins itself, Jenkins community are considered as independent. Jenkins is formerly a part of software in public interest now. There is an ongoing discussion and the plan to migrate to continuous delivery foundation, which is a part of UNIX foundation, sort of UNIX foundation. But Jenkins is an open source project. It's available for everyone. And this is an open source project. And in the case of Google Summer of Code, we discussed it last Wednesday. Yeah, I work for cloud bees, but all three other JSOC work admins don't work for cloud bees. And if you take a look at the mental list, yeah, we have several people from cloud bees and thanks a lot to them for participating. But yeah, again, JSOC is a community project for Jenkins. I hope it answers your question. You're muted, so yeah. Yeah, I figured. Like, how is cloud bees exactly associated? Cloud bees is a contributor. I want to know how Jenkins as an organization is supported? It's open source organization, so I want to know how does it act as a sustainable model? Well, Jenkins is an open source organization. We don't have full-time employees. Yeah, actually, we don't have employees at all as Jenkins project. So Jenkins, yeah, it's open source project. Yeah, we need some money for the infrastructure, etc. We get this money from the nations, from various activities. For example, even for JSOC, we get some money as an organization, though we mostly spend them on JSOC, like travel funds. So yeah, Jenkins as a project doesn't consume a lot of money. For example, one of our biggest expenses now is Jenkins infrastructure. You may have seen a message from Tyler in the infrastructure, so we spent approximately 50 key per year on the infrastructure. But it comes from sponsorship from Microsoft, so yeah, we generally don't pay money. And yeah, this is how Jenkins is sustainable as JSOC project. We get contributions as engineering time, we get contributions or financial contributions, and that's how project evolves and that's how it works. So yeah, Jenkins is not a company. Okay. Yeah, quite an unusual question for JSOC, but yeah, thanks for asking. Probably this continuous delivery foundation will become a bit more clear, because yeah, there are plans to formalize some bits of Jenkins things, like having technical steering committee and other common things you may expect from an open source project. Okay, now we have written it quite differently. Okay. Any other questions? So I muted everyone when they started, so if you want to ask a question, just unmute yourself and ask. I had another question regarding Jenkins pipeline. Like in the pipeline we're writing mentioning in all the stages which particular agent will be used. So suppose I'm running a Jenkins container and in that particular build stage, I'm running another docker image. So it's like supposing I'm compiling Python, so Python container will run. So what is it exactly happening there? Where is the container getting stored? Or is it on my local machine that another container instance is being run? Or inside that Jenkins container that Python container is being run? So if you use docker ecosystem, you have a docker machine, docker host. So this is an execution engine. For example, if you have docker for mac or just docker installed, it usually accesses a docker machine. So what happens in your case when you run Jenkins, it uses docker plugin or whatever to provision a new container with Python, as you said. It spins another container in the docker machine. Where it runs, it really depends on the docker host and documentation. For example, for docker for windows, docker for mac, there is effectively a virtual machine running on your host. This virtual machine is Linux one so that it can just take your containers and execute them natively. If you run on Unix you may have docker containers running directly in the operating system. It depends on the implementation. So if I am locally developing, so like in my local machine itself the Python container will be running as another instance. Yes. But yeah, containers are not virtual machines. So this is something to keep in mind. So containers rely on isolation layers provided by your operating system. So for example, now I use docker for windows. Docker for windows uses Hyper-V in order to run docker host virtual machine and this docker host virtual machine runs containers. But yeah, as a user I don't really care because I get CLI on windows and docker for windows I think just magically handles it for me. Yeah, and if you use other tools, would you treat machine the same? Yeah, it becomes a bit more complicated if you use docker clusters, but yeah for local development usually we just rely on the local docker host. Does it answer the question? Yeah, it does. Thanks. Any questions process-wise? Yeah, you may have seen that yesterday I posted an announcement about Google's season of documentation. So this is a separate program we will be like participating there as Jenkins organization or as CDF. It's yet to be discussed, but it will not impact the schedule and GSOC capacity. I believe that Google's season of docs will be handled by another team of org admins. So it's something which shouldn't impact GSOC at least my current vision. But if you know people who are interested in creating technical documentation etc. yeah please feel free to connect them to Jenkins community because we will try to participate in GSOC this year. Any questions from mentors, org admins? Because if there is no questions, there is no need to spend more time on the call. No questions from my side. Thank you. Anybody else? So yeah, I think we can just close now on the meeting. We will have another session tomorrow for Americas and European region. We can organize more sessions. But yeah, I think next week we will also spend some time to share experience from students. So we think we will discuss in class week. If there are any questions about the process maybe next week is right time to ask because it will be the meeting before the application opens. Even if applications are not open now you can start creating the drafts you can start discussing with these potential mentors. So for GSOC organization everything is open now for all kinds of discussion just feel free to bring them up on March 22nd. It's just the first day when you can submit it to Google. And guess that's it. So thanks to everybody for participating and if you're student and if you don't have any questions this meeting is mandatory. So we welcome you to participate if you want to just see what's going on. But if not it's perfectly fine to just stay in chat and to ask questions in chat. So that's it. I'll close the broadcast and thanks again to everybody.