 Okay, we are live. So today we have a regular weekly sync up for Jenkins Google Summer of Code. Today is April 3rd. We have several mentors and organ means on the call, Matt, Supoon and Martin. So it's just one week left till we have students application deadline. So this deadline is on April 9th. Today we've got dozens of applications and student things about the Google Summer of Code. So I'm really optimistic about this project. Maybe I should turn on the camera because otherwise you just get the Jenkins logo talking. Okay, so yeah, we've got a number of applications and we ask all mentors and organ use to keep monitoring guitar charts and main increase for their project ideas so that you can answer questions timely. Usually in the last week of Fujisoka, especially at the last weekend, there is a lot of students who come to the project submit their proposals. And we still want to provide some kind of feedback to them if possible. So yeah, obviously it's a bit later compared to other applications. But yeah, it's available. We sometimes get good applications just at the very end of the application period. So that's the update from me. Generally everything is up and running. So yeah, if you have any questions, you can just discuss them. Okay, let's take a look at what we have in the agenda then. Can you see my screen? Yep. Okay, so yeah, we don't have specific topics for today. Maybe one topic I would like to talk is about Google seasonal dogs because maybe you haven't discussed it yet. Just sort of looking at status. I believe I provided the status update. So everything is okay. Regarding friction items, we have a bunch of action items in the bottom. Well, mostly on me. We'll just copy paste them. Okay, we do a lot of action items, but some things get stolen. So yeah, just an update from the top. So YouTube recording, we smart and we didn't. So we didn't do that. We had a kitty with Martin, but I think I won't get to it any time soon because again, it depends on CDF, like the work of YouTube ecosystem because it's not clear how we will be working with participants. 10 participants in parallel is not enough for many meetings. So likely we will be moving to another channel. So. And document for mentors about sharing information to students. It's still to do. And the same internal meeting schedule. Actually Martin, if I was able to start scheduling that, so Martin, if you don't mind, I will just assign it to you. It's fine? Yes, fine. Thank you. So budgeting process, it's postponed. Again, due to CDF. So until CDF is established, it doesn't really make sense to do any kind of work on it. And we have a swap for 2018. I think that once we have applications, we will just create a list for 2019 and 2018. And so it's to do and it's lonely. And I believe this will all our handyman's nighting. We have a lot of independent ones, but usually we just do it on the right. OK, I placed it to the wrong column. OK, Google Season of Dogs. This is not a JSO, but it's a great project. So maybe I'll just give a quick update here in the screen. The applications has been open yesterday. And we have submitted an application job. So there is a guitar chart for synchronization of all activities related to the season of dogs. Here are some new community dogs. And here is a draft of our application. So if you're interested, just take a look at this document. But yeah, it's pretty straightforward. You need to enter much less information than in the Google Summer of Code. So we just applied. And this year, the part which wasn't known before, that actually the target is just one or two students. Yeah, so here. So this year, there will be only one or two technical writers in JSO. So we just applied for two. But it limits the skill of the activities so that we actually already have a number of potentially interested managers and work admin who can pull it off. In my case, I'm still listed as a kind of contract work admin. But yeah, I'll step down once we have something established there. So my plan is to just facilitate the thing and to be at running. I don't really plan to work on that. And yeah, that's pretty much it. If you're interested to know what are the current project ideas, there is another Google Doc where we accommodate all the stuff. Once we have more project ideas, we'll likely move to the format similar to Google Summer of Code this year. But now we just put descriptions right here in the document. And if you want to propose some projects, just propose change here. It's publicly open for comments so anybody can go to this document and propose something. For example, if you want to implement documentation for plugins, or if you want to improve solution pages for your area, or if you just want to improve development documentation, all of that is possible for Google Season of Docs. OK. Any questions? Yeah, I have a question. Similar to GSOC, can potential applicants suggest projects or make proposals in GSOC? Yes, they can. So these initiatives are quite different. Google Summer of Code is only about code, and it's only for students. Google Season of Docs is for technical writers, but it includes professional technical writers or whatever students if they have a portfolio and if they are interested in this area. So yes, potentially a GSOC student can apply for GSOC. And potentially GSOC mentors can also be mentors in GSOC. Well, I mean to ask, you know how in GSOC a student can make a proposal for a project of what they want to do, and not just a mentor making the proposal of the project, right? Yeah. Is there something similar here, or is it only projects proposed by mentors? Well, it's yet to be seen, because we haven't seen the final location site yet. So this is the first year in GSOC. But the documentation says that these things are project ideas. OK. We're a bit interested technical writers, so they can do their own proposal potentially. And in any case, we have this documentation channel. So if anybody is interested, you can just go to this channel and make your proposal here. You have almost three weeks before the application deadline, so that even if there is no relevant project idea, you can add one for the very interested mentors. OK, sounds good. I'm sure I could find probably a zillion potential ideas for documentation. Yeah, what if we had a zillion of potential mentors? And I guess that's the hard part. Let's start full-time mentoring. Yeah, so GSOC doesn't seem to be a future investment. It seems that the time investment from GSOC mentors will be lower than for GSOC mentors. But it's not 100% clear so far. This is just the first year in the program. So I believe that everything is in flux. OK, I'll keep my eye out then. I got to get going, though. Thanks for the info. OK, yeah, thanks for joining. OK, if there is no more questions about Google seasonal docs, you can just press it with GSOC. You have another 20 session in two hours, but we can answer some questions now. Martin, Subon, anything else in your agenda? Have anything specific here? I think we've received, we've started to receive some proposals from students. We've had discussions on the mailing list and Gitter and on the proposals we've received so far. And I have nothing to add at this point. I'm just glad to see that we have interested students who have worked really hard to prepare proposals. And I thank the students for doing that and for preparing ahead of time. That's really, really good. It helps us quite a bit. So one thing, though, that I want to mention is for students and mentors who might be listening, or watching this at later time on YouTube, we want to make sure before the students apply to the program, we want to make sure that students are eligible and they meet the eligibility criteria. And the one thing that Google is not verifying for us is for foreign students studying in the United States, there is some special letter that needs to be obtained by those students. It's called the CPT letter, Curricular Practical Training. They need to obtain this from their supervisor at their university. And if they do not obtain this letter, they cannot participate in JSOC. And if they do, they risk losing their visa. So we want to make sure that students are eligible, especially under that condition for foreign students in the US. The thing is, students have to make sure they can get this letter before the April 9 application deadline because at that point, they are in the system and they could be selected. And if they are found to be uneligible later, it's a loss for the organization and the student. And it cannot be recovered. The allocated slot from Google cannot be recovered if it's lost in this way. So just to clarify, we will be selecting project applications in April. So by the time the project slots are fully selected and by the time they are announced, there is still a way to reverse the decision. But the problem that we cannot really make it with students due to the selection phase. We can do some verification queries, but that's it. So please don't expect long negotiations or whatever during the selection phase. Orc admins and mentors would be mostly in the radio silence mode for one month. But yeah, be sure we will be working on the proposals. If any issues appear after the project announcement, as Martin said, there is no way to reverse them. If the student is uneligible or if something else happens, the slot is just lost for the organization and also for JSOC. Because even if you are unable to take another student for this slot, maybe other organizations have been able to run a project. Yeah, thanks for the clarification, Oleg. So I would continue to make sure that all students who want to submit a proposal, they do so as soon as possible. And I believe please do not wait until the last minute. And if you have a proposal and it's not final, I think the Google website lets you keep uploading updates to your proposal until the deadline. So you can keep on publishing your submitting your proposal. And I think remember at the end, I think you have to submit a PDF so that it's kind of a static proposal from that point of view. So maybe we can, sorry. I don't know. Go for it, Martin. Sort of philanthropic. I was just going to invite students who are on the call. They have questions to just jump in and ask. Hi, I have a question. So I have seen some proposals. So basically, the program doesn't really start until May. And some of the proposals I've seen have further timelines. They include even April. So I was wondering, is that something we should do? Or is that just like extra information that you guys don't care about? Or I don't know. I think I've kind of taken the approach of like, oh, I just fill out the required fields. But I've seen some people could do more than that. And then it makes me wonder, do they get extra points for that? Or is it not really even taken into consideration? So I was wondering if you guys could give some feedback on that. Yeah, so quick answer. No, there will be no extra points for that. But yeah, so if you're interested to contribute to Jenkins in April, if you're interested to study Jenkins, et cetera, you're more than welcome to do that as a part of JSOC or not as a part of JSOC. It doesn't really matter. So no, we do not block any kind of contributions in April if potential students really want to do that. But we will be judging on what information we get by April Lines. So if you edit your application draft after this time, well, it won't impact our selection process. And the same way, if you do contributions, you'd also want to impact the decision we will be judging from the state of April Lines. So yeah, if you're interested, you are welcome to do that. No, it's not required. No, it's not expected. So if I may, the calendar states that the community bounding period starts on May 6. Now, if students book in their proposal if they say that they are going to work on the JSOC in April, we cannot consider that in when we review the proposal. Well, all the applications I've seen, it was rather about exploration. So studying Jenkins or whatever in April. Yeah, if you plan to do coding for your proposal in April, it's probably not the best idea because yeah, there may be other students working on the same area. Well, we cannot say no. If you want to contribute, if you want to produce code, you can definitely do that. But yeah, I would advise against that. If you just want to study Jenkins, it's generally your choice. If you're interested, feel free to do that. Does that answer your question, Natasha? Yeah, thank you. Yeah, so if we speak about work in April, maybe we should also talk a bit about work in May because yeah, you may see that community bounding period is pretty long. So it's three weeks. And yeah, what we would expect in our organization that once you get the acceptance notice, we don't expect you to drop everything with your study, et cetera and start working on JSOC immediately. It's not expected. We want to have a smooth transition but we're ready to start from the second week of community bonding. There will be regular meetings, scheduled use mentors. Maybe there will be some introductory letters and other things to be done. So yeah, we expect some events to happen during the community bonding and also we will be organizing on-demand trainings and other things which we haven't touched. For example, we wanted to have a session with former JSOC students during the application period. Obviously it didn't happen because we were just note on the other stuff. But yeah, we will definitely have something like that in the community bonding period. So yeah, please expect that there will be some events there and you will also expect it to work with mentors in order to do some reality marketing of your project idea and so that when the coding period starts you can really start coding. So that, for example, some adjusting designs, creating GRT kits, ordering them, et cetera. We expect a bunch of that to happen during the community bonding. Does it make sense? Okay, any other questions? Okay, if there is no questions, we can just close down the call and we have another corner session in 90 minutes. So if you have anything to ask, if you want to discuss a new proposal or session, we can do it during the next session. Hello. Yes. Hi, Oleg. Can I discuss project ideas right now, like I should read for the next session? Oh, yeah, actually you can. Okay, I'll ask. I was asking about. Okay, I'll ask one question. As discussed yesterday, like Klaus said that something about the build pipeline, I'm talking about the Artific Promotion plugin. He said something about the build pipeline view, right? Yesterday. And I found that there's something called a manual trigger in the build view. So if I introduce a new plugin, Artific Promotion plugin, should I eliminate that particular function of the build pipeline view that there's an existing manual trigger promotion condition in the build pipeline view, right? Yeah, both ways should be doable. So yeah, our expectation is that you have the plugins available in classic pipelines, whether you have it in other plugins like pipeline view or devotion. It's something for you to decide and to propose as a part of your application. So if you want to extend devotion and to offer special integrations there, you cannot do that. If you want to update pipeline view plugin, pipeline stage view plugin, then yeah, you also can do that. So it's just your choice. If you're interested, you can explore how to do that. Spoiler alert for devotion, it's not trivial right now, but yeah, if you really want to do that, it might be possible. Okay, okay, fine, fine. That is my only question I think. Okay, sir, I'm done with the questions, okay. Thank you. Thank you too. Thank you. What about you, Nisark? Yeah, okay, so I also have only one question. I don't have any specific doubt, but I was just confused for the implementation for discarding bills from the multi-branch pipeline. Like the points of implementation, which I mentioned that would run, but I was just looking for any other method which could delete the bills in a better way. And like I want to ask one thing that like the current delete method, which is used in the log rotator, like it could work for discarding the bills from the multi-branch pipeline. So like in previous few meetings, we had discussed that a new delete method would be useful for that, but actually that new delete method is useful for the external workspace manager as the information of the root directory would be different there. So I think like one point was mentioned in my proposal that new delete method would be implemented as the root of workspaces of pipeline of multi-branch. So like I think that the existing delete method would only work. So I want your views regarding that. Marcin, what do you think? Oh, boy. So I don't, this is a technical question and I'm not familiar with that code. It's fairly advanced. Like I cannot offer any advice here. I would have to go into the code and study it myself. Yeah, so what could we do? We can spend some time now on the screen share. So let me show some bits of this code and we try to find answers together or we can just take it offline or maybe in the main at least. Like yeah, it would be preferable I would say because I also didn't have an immediate answer. Right, I agree with that. We should take it offline and to me, I need like a subject matter expert to dive into this. So let's take it offline. Okay, okay. So like I'll just comment that point in that specific point and like I'll just mention both the ways possible. Like we can use the like the method which is implemented right now and also we can propose a new method which could delete the bills from the external workspace manager by fetching the bills, you know, like by fetching the bills from the or specifically the workflow branch from the abstract workflow branch project factory. Okay. Yeah, we, it's fine to put it in your proposal. Yeah, okay. Like I'll just mention both the points. Okay, yes. Thank you. Yeah, and if you want to discuss it in detail, main at least would be better because it's hard to follow in the discussion, especially when there is no screen share, et cetera. So yeah, we want to discuss details. So let's just discuss with them in the proposal that it can. Yeah, okay. Actually the mailing, sorry, the mailing list is a very good idea. If you can put your questions in writing, you can send them to the mailing list and then we can ping specific developers of that plugin so they can chime in and provide some more advice. Cause right now Oleg and I do not have this knowledge. Okay, so like I'll just start a new thread and I'll just put the proposal link and just write this question. And yeah, also like if you have any better idea or a better way to use any method in the multi-run pipeline for the efficient integration. So like your feedback would be much more valuable. Yeah, so one of the ways is to actually raise a question in the developer mailing list. And then we can ask for example, Steven Connolly or who else, maybe Robert Seyendal or JC Bleak who will be working on this area. We could just ask them to provide some feedback if they're available. Yeah, okay, thank you. So like Oleg sir, are you asking me to post my query into the developer mailing list or in the GSOC public group mailing list? Developer mailing list might be better for such kind of deep questions. Okay, yeah, sure. I'll just post my query there. Yeah, okay. Okay, thank you. Yeah, thank you. Okay, so do you have any other questions? So we have Jason on the call for Jeremy recently. So Jason, if you want to ask anything, just go forward, we definitely hear you. But yeah, if you want to ask something, just do it, it doesn't quite work. Maybe he's gonna try to log in again. Okay, do we have any other questions to discuss for now? Oleg sir, one question by the time he joins. For the Artific Promotion Projects, we were discussing some sort of like dedicated session for that. We did not meet up at, I mean, we did not come up with an exact date. So can we do it in this week, later this week, if you're free? If I recollect, we agreed one of the options was to have it after the daily meeting. Yes, sir, but the thing is, cluster will not be available today. So that is the reason. Okay. I'll just make another doodle invitation and I'll try to invite him on Friday, because he said he'd not be free for Wednesday and Thursday. So can I invite him on Friday? And if he agrees, we can do that on Friday, if you're free with that? Yeah, I'll try to join. Okay. Friday or Saturday, like as well? Yeah, so just find time slots when clouds can join. Yeah, if I'm available during this time slot, I will join. Okay. On Friday at this particular time, will he be free? Check. For me, it's usually, it's just difficult to guarantee for sure these weeks. But right now, yeah, right now I have nothing scheduled at this time. Okay, okay. I'll try to come up with a date. Okay. Thank you. Okay. Thank you, sir. Thank you. Yeah, so sometimes it might be challenging to get mentors on the call, because everybody is busy, everybody is working in parallel. For coming into bonding and for coding places, we will be setting regular meetings between students and mentors to circumvent a bit. But yeah, right now, we mostly rely on offline communications. So mainly in-place chats, et cetera. So if you have any specific questions to clouds, maybe you can just ask them in the chat. And even if he's available on Friday, then yeah, that's perfect. We will discuss these questions in details. If not, you might get some response while everything is being scheduled. Okay. Thank you, sir. Thank you very much. Okay. So if there is no questions left, we will just close this meeting and we'll see you in eight minutes. Hello. Hello. Hello. Hello. Yeah, now we see you. Can you hear me? Yes, you can. Sorry for the... I have connection issues just now. And actually, I just want to ask if... So I'm working for the plug-ins that requires a bit of encode, and will it be useful if I include some sketches in the proposal? What do you think? Sketches are always helpful. Yeah, is it? Sorry? Sketches are always helpful, especially if your proposal involves changing a web UI. So I just include like screenshots or sketches in the proposal. Is that what you mean? Yeah, right. So any visual information may help because, for example, you can take a resistance screenshot and mark what you want to change there or you can take whatever project I think for things like the envision map or whatever and just create a draft of new UI there. So as in which such thing can be a part of your application and be a full UI project, it's really helpful. All right, cool. What if I include some external resources? So like if I push it to external links and I include it in the proposal, will that be accepted as well or do I need to like directly embed it in the proposal itself? No, there is no strict need to directly embed it in the proposal. Sorry? Yeah, you can refer it, start on all resources. Just make sure that they stay available during the application period at least and that there is no major changes during the application review. Preferably to avoid any changes. You're welcome to refer any kind of external resources if you feel it's reasonable. Okay, sure. Actually, Oleg, I think the final proposal by the students is PDF and should be static with. It can have external links, but everything the student proposes has to be kind of embedded in the final PDF. But it can have links. It can have links to reference material. But if you prepare a picture or some diagram or sketch, I would embed it in the final PDF. And I think you can upload the final PDF until the deadline. I see, I see. So it's better to embed it in the PDF itself, right? Yes, that's what I think. Okay, that makes sense. So the links would be some links like external repository, I guess, only for that purpose. But for pictures or graph, I need to embed it inside the PDF itself. Am I right? Yeah, if you draw a specific picture, a specific diagram, I would embed it. Okay, cool. I don't have a strong opinion on my own. Well, if it doesn't take much time to embed it, why not? Yeah, sure. Okay, so like... Yeah, sorry, you can continue. Okay, if there's no other questions, we can adjourn the meeting. Oh, I have one small question. Sorry, you can hear me. I have one small question about that. I have a poor request for about the mailing list. Is this okay? I mean, we put like that, or what do you think? Just a second, I will screen share. Yeah. Okay. In infra, yeah. There are some leftovers, but let's take a look at what's in the currency. Listen, can you mill your... Okay. So you generally move these instructions from the student guide to the main page? I mean, I don't move like this, copy over. So... Actually, I think it's too less for this year, but maybe we can... Yeah, for me, it's not really why we need to just copy this information. Yeah. Martin, what do you think? So I believe it was being asked to actually... Yeah, so the idea was to clarify which communication channels to use, right? Yes, yes. Okay. So maybe we could cut this part, because yeah, if it's a copy piece, probably it's not needed, but we can keep this part and merge it. Is this... Are you copying the information from one page to the other good one? Yes, I copy it from one page to another, because I mean, although this information already there, but I feel that all the students just use it, they don't use mailing lists. I mean, yeah. So it's a bit like very difficult to check. Mm-hmm. Yeah, it's what I feel. Okay, so what we could do, for example, here we could explicitly set that this is a recommended channel. I mean the... Yeah. Something. Sorry, I'm... on another keyboard. Okay, and for example, we have set this also... Right. So the reason you're copying this to the front page good one is because it's because you think it's going to be hard for students to find this on their own page, on the student page. Yeah, I feel that nobody is following that in the student page. I mean, yeah, I mean, I just happened like from two weeks ago when I submitted the pull request. Mm-hmm. Actually, we don't have any like mailing lists here. I mean, we don't see much mailing lists. I think it will be happened this year for Jason. That's, yeah, you're right, because we promoted the Gitter channel quite a bit. Oh, okay. But do you feel that Gitter is... I mean, if everyone using the same channel, do you feel it's difficult to check? Yes. I prefer the mailing list. Yes, yes. So that's the reason why I... Okay. Yeah, yeah. So if we rewarded them something like that, so we use the project proposal discussion for discussions. This is a recommended channel for communication. There is also a Gitter channel for real-time communications, but it is better to use mailing lists to request technical feedback or to have long discussions. Okay. Does it make sense to you? Yeah, I mean, yeah. Just a minute. The sentence which says, this is a recommended channel for communications. If you want, if we should say that this is the primary channel or the recommended channel for... Yeah, this is more specific. It means it's this one and the other ones are secondary or optional. Okay. I'll send you a link to the article about articles, because unfortunately, in my native language, there is really no article, so I don't see a difference between a and a in some context. Okay. Yeah, I understand what you mean here, but it's not something like waiting for me. Okay. So I propose the change then. Okay, sure. I just propose a change there and we will update my request. Yeah, I believe we agreed to cut this part, right? Okay, we cut this part. We don't copy paste this part anymore. Okay. Yeah, it's already there in the student page. Okay, I can remove that. Yeah. Thank you. Okay. Yeah, even if it's a bit late, we will still have four months of JSO, five months of JSO. Yeah, yeah. Okay. Okay, yeah. That's all from me. Yeah, sir. Sir, I have one question. Like, after the student application deadline, after nine, like, is there any specific thing that Jenkins want students to do or having a look on any specific thing or like that or do like any specific task which students or like students should do after submitting the proposal or, you know, like anything like that. No, we don't have specific tasks. We want you to do after submitting the proposals. There was a question from Natasha in the beginning of the meeting. But yeah, generally once the application review process starts, we don't expect students to do anything except being patient and waiting for the project announcements. We really, yeah, we won't really communicate with students. We won't really have weekly meetings in public because we can't say anything in public before the project's announced. So you will be just waiting. Yeah. Okay. So like from nine to six minutes, there will be like no meeting, you know, which students are like that. Okay. So like after six minutes with the selected students, you can. Yeah, right. So you're welcome to join the regular meetings if you're interested, like special interest group meetings. We will still keep running them. But yeah, we won't be discussing project proposals and the review status there just because we cannot. Okay. So yeah, there will be activities in the Jenkins project. But yeah, from the application standpoint, we won't be able to say much. Yeah. Yeah. Okay. Thank you. Okay. Thank you. Okay. So we're almost out of time. Anything else to discuss today? I would invite Lee Roulang to ask questions. He just joined. So if you have questions, please do, please ask. Sorry. I just want to hear what you're talking about. So I have no question. Okay. We're just answering questions from students at this point. Okay. So I may have some specific questions for OLAF and Wutuan. So I'm going to revise the proposal and I'm going to move everything that is related to Kubernetes to the first phase and every optional feature to the second phase. What do you think about that? What do you think, OLAF? Is it too much for the first phase we do the whole Kubernetes thing? Well, it's better to start from things which might have, so that even if they take longer than expected, they get delivered. Because if you postpone the kernel things of your proposals till the second coding phase or till the third coding phase, there is a high probability that something doesn't go as expected. So my general advice is to start from more important things even if they're more complex. So it's still time to have some preliminary research, but then if your proposal is mostly about Kubernetes, it makes sense to have it in the power list. Okay. So one thing is there's a feature that we can auto provision Kafka from binary files. Things I think, I mean from my point of view, I think this feature is quite important with the current plugin. So I mean, do you think we can do this in the first phase or we want to move it to the second phase? Any idea? I think the proposal is like integrating with Kubernetes feature. So I think I should focus on the Kubernetes part first. Okay. Although this is very useful. I can move it to the first part of the second phase. Okay. Yeah, I think it should be okay for me. Do you have any opinion on that? Excuse me? Yeah. Okay. Do you have any other concerns about the proposal? Do I need to include an implementation detail or architectural detail? Is it necessary to include it? I don't think it would be a requirement to include this, but if you have any ideas, maybe just include that. It would be nice to have that. I mean, it's not required, actually. But it would be nice if you can draw something there. I mean, yeah. It's up to you. Yeah. I fully agree with you, Zvuton. So if you have any ideas or if you have done research for whatever interests of your projects, just put it in the proposal or maybe even in the appendix so that it's below your main proposal. But yeah, any such information will be helpful because once we start community bonding, we will be actually talking about architecture and about first steps. So if you are prepared to that, it will help everybody. Oh, I see. I see. Thank you. Okay. So thank you for answering my question. I have no more question now. I'm going to review. I mean, I want to rewrite the proposal now. Yeah. Okay. Thank you. Yeah. So I guess that's it for today. Well, thanks everybody for participating. And yeah, see you in one hour, I guess. Or maybe not. We have this meeting next week. We still have, right? Yeah. We still have another meeting in one hour. No, no, next week. I mean, this meeting. Next week? Yes, we will have this meeting. We won't be doing Q and A. We will probably have a short meeting in public and then move to private chat but it is something which we need to decide. Okay. If we need to connect sessions next week, I am available to organize additional meetings on Monday or Tuesday, but we will do it on the one-demand. There are many students who need a video meeting. Then maybe we can do that. Otherwise, we will just discuss proposals in the charts and in the middle piece. Okay. Okay. Sounds good. Yeah. Thanks, everybody. I will stop the broadcast.