 OK, we are live. So today we have our regular corner session with students interested in Google Summer of Code. We have several students on the call, as well as few mentors. Just to update a bit about the program, yes, the Google Summer of Code has been officially open for student applications. So whomever is interested in the Jenkins project, recommend to start submitted applications earlier so that you have more time to polish them. And yet we still have more than two weeks to finalize these applications. So I think we can just proceed with questions and answers. As we discussed before, we will limit every question to five minutes. And we will be rotating between students after the questions so that we use the time more efficiently. And yeah, this is the plan for today. So if you have any questions, we can start from them. Hi. Yeah. I had a question. I had already submitted my proposal. I mean, I showed it to you through the GitHub chat. Now what is the next step I have to do? Should I submit it to Google or should I wait for your comments? So you can edit your proposal after submitting, right? What we recommend is once you address the first feedback, I will do my best to provide more comments in one or two days. Then you just submit it. And then I recommend to continue the discussion so that you can improve your proposal. And maybe a few days before the deadline, you can just upload the final version. But in any case, you will already have a stake in the ground so that if something goes wrong, you will already have an application. So this is how we recommend approaching that. OK. OK. Next question. Yeah, sorry for the background noise. Yeah, we have a conference today. So yeah, there are many looks like that. And there are some test drives. So yeah, sometimes you may hear noise because there are cars passing nearby. OK. Any other questions about the application process about your projects, whatever? Yeah, so I would like to know that whether the submitted proposals by the students will be selected by the mentors of a particular project or the mentor of the whole community. Like, oh, it will be displayed to the whole community and all. Yeah, so how it usually happens, yeah, once you submit your proposal on April 9, we as an organization, we will see all the proposals and we will start reviewing them as an organization. So it means that we have 25 potential mentors or so, all of them will have access to your final proposals. All of them will be able to comment. All of them will be able to flag your proposal and to say that I'm interested in mentoring this project and the student. So yeah, this is the first step. And of course, we will filter out proposals which are not relevant, et cetera. And then we will have meetings with mentors in order to define how many project slots we want to request this year. So as an organization, our first objective is to send two numbers to Google. One number is minimum number of projects we want to have and another number is maximum number. So we send these two numbers and then Google reviews the application, reviews applications from other organizations and then returns us only one number, number of projects we are eligible to take this year. So we will get at least one project. It's not guaranteed that we will get a minimum number of projects, but yeah, we will get a number. And after that, we will start forming the mentorship teams so that we will take proposals. We will work with mentors. As we discussed for each project, we expect to have at least two mentors. And our objective will be to form these teams. So once we form these teams, we will submit this information to Google. And on the day of final announcement, this information will be published. So this is the process. OK. That's why it takes one month because there is a lot of background work happening. But really, it's organizations who select project proposals. OK. OK. Any other questions? So if there is no questions, we can just close down this meeting earlier. Yeah, we will need to send another announcement about these meetings because we noticed that there are many students who joined the mailing feast, et cetera. So we need to recent the message in order to get contraction. But yeah, we still have a few weeks to finish all the applications. OK. If there is no other questions from students, just in case, are there any questions from mentors? Yeah, OK. So one more thing that, like, sir, had you gone through my proposal? Like, you had said that you will just have a look on my proposal and just see my replies to your comments. And after that, we'll be having discussion. So have you gone through or else? Yeah, I'm trying to help as much as I can. But really, for advanced built discoverers, it's rather Martin who would be the main contact. So I'll do my best to review this proposal. But I'm not sure whether I'm listed as a potential mentor there, maybe. Yeah, I'll try to review that. But everybody of us has limited bandwidth. So sometimes the review may be delayed. That's why we recommend to start early because, yeah, we don't have 24 hours per day. I wish we had one hour per day sometimes. But yeah, this is how it works. Yeah, OK. So my only request is that I have replied to your comments for a particular section which you had given. You have already reviewed my proposal for once. And you have commented a few points. So I have replied to it. So my request is only to just have a look on my answer. Yeah, I'll do my best to review it. Yeah, OK. So thank you. Thank you, and thanks for reminding me. Because sometimes you have a list of action items to do. But this list continuously grows. Sometimes I have difficulty with screening them up. OK, I will review that. OK, thank you. OK, any other questions? Parish, you were silent today. Yeah, actually, I don't have anything specific to the project. I just wanted to ask about the Blue Ocean container. Actually, I wanted to connect with the, like, communicate remotely with the container. So, like, I was trying to SSH, but by default, they do not support SSH. The download does not support SSH. We need to work forward that. So I just wanted to know, what is the correct way to do that? Yeah, so the correct way to do that is Docker exec command. Because how it usually happens, you start the container. And there is a command which allows to execute arbitrary execution there. Just a second, I will probably screen share for a second. OK, do you see my screen? Yeah. OK. So what you need to do is something like that. Docker exec minus I, because you need interactive mode. Let's see whether there is a sample. Yeah. So I believe here, so this is actually what you want. So you can just run Docker exec minus I minus T. And then you can run command, for example, bash, and then you get a CLI running inside the container. So it can be an option for you. OK, I did that. Actually, what I saw is on the internet, like on Stack Overflow and other blogs, people suggested that we shouldn't run SSH server on Docker. Yeah, but it doesn't use SSH server. So it uses Docker CLI in order to connect to the container. I can probably show it to you. Yeah. That is fine. If I want to use Jenkins CLI, we need to communicate with some method, right? If you want to use Jenkins CLI, Jenkins CLI doesn't require SSH. So Jenkins CLI has multiple options. And one of the options is to connect over HTTPS. And this is the recommended option. I'm going to do it. Hm? Sorry? Yeah, over HTTPS, I was able to do with my authentication credentials. But I just wanted to know why wasn't SSH working? Like, in this website, the SSH is, like, the procedure is given, but it works on if I'm running on a local instance, but it doesn't when I am running on a Docker instance. It's mostly because my Docker hasn't forwarded the SSH port. Yeah, right. But this one, even if you use SSH here, here you don't connect to a SSH server in Docker. Here you connect to Jenkins, because Jenkins runs this SSH server, and you just connect to the port configured on the Jenkins site. So you need to configure your Jenkins instance to have this port fixed. Then you expose this port using minus P option in Docker. And then you can connect. So you don't need to run SSH server if you want to use SSH mode here. But actually, maybe it's missing from the documentation. There is not only SSH mode, but there is also HTTP mode. So by default, HTTP mode is used. And this is what I recommend to do. OK. Yeah. So if you expose web interface, HTTP mode should be working well. OK. But is HTTP mode as secure as SSH? Well, if you use HTTPS, yes. If you use HTTP, of course, no. So HTTP mode just means that it's over HTTP endpoint. But here you may see that the example actually, OK, this example is actually for, yeah. So this command goes to HTTPS and Jenkins. Can you operate in HTTPS? Is it? OK. Oh, OK. Does it answer your question? Yeah, it does. OK. Anything else for today? If no, I'll just close down the meeting. And yeah, we have another one tomorrow at 4 PM UTC. So yeah, if you have any questions, please join that meeting. And yeah, thanks a lot for your time. By the way, we have another student on the call. So maybe he has something. OK, kill it. So yeah, I guess that is nothing else to discuss today. And yeah, in such case, thanks a lot for your time. And we'll see you tomorrow or next week. Sure. Thank you. Bye. OK. Bye. Thank you.