 OK, and we are online. So how are you, everyone? Today is the regular Google Summer of Code meeting. But, yeah, today the schedule is not regular, because today is the first meeting after GSOC project announcements. We have Orchard Beans on the call. And we also have UFA. And other Orchard Beans and mentors will be probably joining later, because we just shared participant link a couple of minutes ago. So, yeah. OK, do you see my screen? Yes. OK, I just wanted to show what has changed. So, yeah, if you have any questions, and if you're on the YouTube call, feel free to ask these questions in the GSOC Gitter chat, or you can just use this participant link. But, yeah, as long as we have enough slots, you are welcome to join. If needed, we will be rotating during the session. So, yes, on Monday, we had GSOC project announced. So we, as GENC's organization, got seven projects. All these projects listed on the Google Summer with Code website. Currently, we are working on updating the GENC SIO website so that all our projects get their own pages there. It will be done this week. But, yeah, you may see that there are seven projects accepted. But, yeah, there was a lot more students who applied to GSOC this year. And there was a lot more mentors and project ideas. And, yeah, actually, we wanted to say thank you to all students and mentors who participated, who invested their time in GENC's GSOC. Because, yeah, we know it's hard work to just prepare proposals to explore their areas. And we really appreciate that. Unfortunately, we were unable to accept everyone we wanted this year. And we apologize for that. But, yeah, GSOC is a highly competitive program. Sometimes you have to make tough decisions. But, yeah, whatever happened, we invite everybody to participate in GENC's or in other organizations. Currently, we're exploring options to have other programs in addition to GSOC. And, yeah, if you're interested in GENC's community, you are more than welcome to continue working with mentors, to ask them questions, to join community channels, and to work with us. So, yeah, in addition to what I wanted to say, that, yeah, as GENC's project, we would appreciate any feedback. Yeah, we sent feedback to almost all students by now. If you haven't received the feedback yet, please speak to Orkut means. And we will make sure that this feedback gets sent to you as soon as possible. And if you want to share anything with Orkut means, please also use the Orkut mean mailing list so that we process your feedback and take it and count it in the next year. OK, so, yeah, regarding admin mailing list, some is here. So, GENC is GSOC, 219 Orkut means. Yeah, and then we will be running a formal retrospective so that, yeah, if you want to share anything with us, we will also edit the retrospective documents. What else is going to happen? To everybody who participated in the application period, we would like to send some swag. So please send us your shipping covers, again, to GENC GSOC 219 Orkut means mailing list. So, yeah, we will make sure that we sent you. And it's not only for students. It's also for mentors and actually also for participants of the 2018 project because we delayed the delivery of swag and we will be sending swag for both ESS at once. So, yeah, we will make sure to send them. OK, yeah, as I said, on GENC GSOC, everything is work in progress. So now there is not that much materials about GSOC 219, but we'll be sure it will be updated. Regarding the guidance for students, we have information for students' page and this page is up to date. And here you can find the community bonding page. So effectively, all the information, all guidance and all expectations are listed here. And we will be using committees in order to provide more information. So, yeah, I'll show the page later. But the basic information is already available here. Generally, what happens now for all asset projects, you start working with your mentors, you schedule meetings, you schedule communication channels, and you start working together on community bonding. Two main goals in community bonding is to firstly, yeah, get introduced to the community, which, yeah, it's all those goals for community bonding and another one, get all the required onboarding and enablement to be able to work on your projects. So it means getting necessary permissions, creating GitHub projects if needed, creating whatever other resources and also getting enough trainings. So what we expect from students now is to actually make sure you have conversation with your mentors and think which information you would need in order to be effective with your products. So any idea you have in mind, please share with us in the chat and we will try to organize something. So, yeah, that's the plan. Any questions so far? I guess not. Okay, so yeah, if you have questions, just put them into the chat. So what are the next steps? Yeah, for accepted projects, the next steps is actually continue community bonding. So I briefly summarized what we expect you to do. For details, yeah, you just created this Google document with a brain down. So you may see that there are multiple sections and actually what we expect to do. So yeah, we expect mentors to initiate communications. So it's really important that mentors start actively working with students now and please reach out to students. If you haven't already done that, please start discussing meeting notes and make sure that you schedule the first meeting. You have to recommend to do in the first week because your community point is not that long and there is a lot of items to prepare. And then what else you want? Yeah, sorry. Okay, so what else we need from you all? We will be posting announcements on Jenkins.io with project introductions. And in order to do that, we actually need some information about you. So we ask you to submit your profiles to Jenkins.io. So we have pages for all authors of the blog post. So you may see the list here. And actually we ask students and mentors tools create their own profiles here. So it's just a summary with short description. So do we have Martin in the list? Yeah, we have Martin in the list. So yeah, here you may see that there is some information added. Generally we need your GitHub account, your Twitter if you use Twitter and also some summary. That's it. And yeah, also it would be nice to have your photos. It's not mandatory, but if possible, please submit your photos to this directory, content images, authors. So yeah, there are also images and you can just, we will be just using it in some materials if needed. Okay. So yeah, that's what we need from mentors. For students, yeah, as I said, submit profiles. Then you'll also need you to update project pages. So what's going to happen right now? There is no project pages on Jenkins.io, but they will be pages similar to what we have had in the 2018. So if you go there, you may see that there are projects and for each project, there is a page. This page includes summary information about the project plus links to all information, links to community channels. And effectively this is a page you will be using to submit to Google as a result of Google Summer of Code. A bit of the third phase, you're expected to submit such page. So Jenkins project provides a place, but the content, yeah, it's up to students and mentors to fill it in. And yeah, we ask to start doing it earlier so that we have some basic information and that we can share this information with other potential stakeholders and the projects. So all these pages actually being developed in ASCII.DOC, all of these pages are being managed by pull requests. So you can just let fork Jenkins.io. And yeah, you will need to fork Jenkins.io in order to submit your profiles. But once you do that, you also can start submitting page patches. And as all that means, we will be integrating them after a quick review. So it will give you something you can start earlier and you will be able to try out Jenkins.io development because yeah, all of you will be submitting blog posts and it's important to be able to contribute something to Jenkins.io. At the next meeting, I can show you how to develop it or maybe we can even do it later today. Okay, so what else do we have in the list? It would be great if you send some introductions to the community. So as a part of community bonding, all of projects have mentors. Some projects probably have many mentors. I believe our record is something like five mentors. We will be probably re-organizing the teams later. But yeah, in any case, it's just a fraction of the Jenkins community and we want you to really participate in the Jenkins community. There is Jenkins developer mailing list. Some of you have already submitted messages there to discuss particular topics. And we invite all students to work with mentors in order to send self-introduction there. So just to introduce yourself and your project and it would be nice if you sent these emails during the community bonding. Preferably during the first weeks because you might be able to find additional stakeholders who will be interested in your projects. Okay, what else do we have? We expect all teams to set up team meetings. So we will be keeping this weekly office hours to discuss JSOC activities, maybe do some Q&A. But really the most of the work will be happening in the guitar charts, in your mailing list, and also at team meetings. We recommend all teams to have two meetings per week so that you will sync up with each other. And yeah, we ask you to set up these meetings earlier. And you will also need to set up charts. The most of projects already have charts, but yeah, maybe you want to change them due to whatever reason. So yeah, just start establishing the communication between each other. So yeah, so we define the time slots which are comfortable to you guys. And yeah, each project is, yeah, you're free to define how we work together within the team. So we don't impose any strict requirements there. What else will you need to do as a team is to create a design document. So currently we have project proposals. So each of you has submitted a project proposal. It was reviewed, $1, we got some feedback. But yeah, there may be open action items. There may be needing some reality mapping. For example, your project may be too big or too small. So currently, since you have mentors, you have more understanding of what the project would be, you probably want to sit together and to define what you want to do. And once you have a design document, you can also share it on the project website. And you can use this design document in order to create GRT kits and epics for the first phase. So Jenkins uses a centralized Jira, almost all projects use Jira and we highly recommend to use it for JISO as well. So that you can start from creating tickets at least for the first phase, so that you have all the information prepared. And then yeah, when the coding period starts, you already have created tickets, you have designed notes and you just start coding. So this is our main goal, to ensure that everything is ready by the first day of the coding period. If you need any help from Orca Means, yeah, just send us a message. So whatever training you need, if you feel that particular areas of your project proposal needs technical advisors because you don't have proper expertise in the team or if you need something from the intrasoaction site, let us know we will do our best to help with it. Okay. I hope that it summarizes what we expect during this phase. Are there any questions? Hello. Yeah. Hi, sir. I wanted to ask one question like later today, I tried to close one of the issues in the Jira phase, but like later you opened it again. So what was the reason behind that? Okay, I can show it, but yeah, just second tell show it. Yeah, it was for promoted bills plugin. Yeah. Yeah, so, yeah, as I said, we use Jira, but the way we use Jira really depends on the project, but here he's the Jira ticket plastic references. So you may see that it's reopened. So yeah, there is a pull request. This pull request has been merged towards the master branch, but it wasn't released yet due to whatever reason, likely it's my fault, it's my fault for sure. And so, yeah, even if the change is fixed, so nothing left to be done from your side, the fix hasn't been released and hence it's not available to users for now. Yeah, we have state like fixed, but not released in Jenkins Core, but for plugins we just keep them in review until they're released. Okay. But yeah. Okay. Okay, sir. Yeah, but yeah, all Jira workflows, please work with your mentors to define how you use Jira. Because yeah, in our case, it's just shared hosting for all plugins, but each plugin is pretty much independent in terms of how they use Jira. Okay. Okay. So it means that it's still in review. That's why it's not getting closed. Yeah, it's not in review, it's waiting for the release. Okay. Yeah. So yeah, there is status which is called fixed, while it's not resolved and released. So I can close with these status and then yeah, then it's probably the best option for here. So yeah. Okay. Okay, sir. Okay. So any other questions? Maybe Martin Jeff, would you like to add something? Hi, Oleg. So like this is a very basic question. I just wanted to ask, I don't know, like why is an GSO website Jenkins mentioned as Jenkins project rather than Jenkins? Wow. Yeah. So it happens. Generally, we have been using Jenkins as a project to distinguish it from other things. Because for example, Jenkins organization is slightly bigger thing than Jenkins project because yeah, it includes, okay, I'm sharing my screen again. So let's go to Jenkins I.O. Okay. So Jenkins I.O. includes many things. So yeah, whatever is here is a part of the Jenkins project including sub-projects like for example, Bloch and Evergreen, Google Summer of Code and Transstructure, whatever. For example, Jenkins X, he is maybe an exception because Jenkins X now moves to continuous delivery of the foundation. So it will be on the same level as Jenkins nowadays. I'm receiving a lot of background noise from somebody. Yeah. It is me, sorry. Okay. Okay, thank you. So yeah, this is Jenkins project or Jenkins organization. But yeah, if you say just Jenkins, it may be a bit confusing because yeah, Jenkins is a server, Jenkins is a whatever, but yeah, Jenkins website is a Jenkins or not. Same for infrastructure, it's not exactly Jenkins. And sometimes it goes to more weird cases like for example, if you go to Jenkins organization in GitHub, you can see that there are some projects like for example, 3D SSH. Yeah, this is a project. It's under Jenkins umbrella, but the fact that it's project being widely used in many other areas. So yeah, even if it's a part of Jenkins organization, it's probably a part of Jenkins as a component. But it's not a part of Jenkins project. So something like that. Anyway, yeah, it's just the details. While we use Jenkins project on the website, likely due to historical reasons because that's how we originally applied. We keep these things starting from 2016. So you're right that we might need to change that because if you're going to continue to deliver the foundation, then yeah, we continue to deliver the foundation. We have four projects now. So it's Jenkins, Jenkins X. Effectively in this Google summer of course, we applied for both Jenkins and Jenkins X. So maybe we will work a bit on the GSOC terminology in order to specify that this is this part going forward. I'm not sure whether I answered your question or confused you even more, but yeah. Yeah, I got it, thank you. Yeah, so yeah, we shouldn't really care. Yeah, you work in the Jenkins organization on the Jenkins project in any case. Okay, anything else? We get more and more people on the call. Okay, if there is no questions, you adjust to summarize things. Yeah, there is a link of what we expect you to do. We'll send it in the mailing list soon. So you will receive the same information. And yeah, the project starts now. So yeah, we understand that all students still need a kind of transition period. So we don't expect everybody to start working on community-bounded tomorrow. But yeah, currently make sure that you finalize your other commitments that make sure that you align your commitments with GSOC. And if you need any help from mentors to do that, please reach out to them. Because yeah, they will be issues with time zones. They will be issues with finding slots for meetings. And it's better to start at earlier, even if it doesn't require much time. For the rest, yeah, end of community-bounded, the best time to do knowledge transfers and to do some planning for the coding, please. I had another one. Like in the community-bounding guidelines, it's mentioned that in the deliverable, after the plugin has been developed, it has to be released to the alpha channel or the update center. Can you please explicitly tell what these two are? Mm-hmm. Well, it's a bit earlier to talk about that, but yeah, I believe Parichet has already submitted a request to host his plugin. So yeah, maybe we'll get some releases before the coding starts, who knows. Okay. So yeah, experimental update center. So I'm not sure what is the link, but yeah, so there is a page called well, publishing experimental plugin releases. And this page should be, should actually summarize what to do. I'll just put it to the meeting notes. Come here. I'll go to this experimental. Okay. So yeah, this page actually summarizes it. So as long as plugin version has alpha or beta in the version number, it gets released to the experimental update site. So it means that it won't be immediately available to all users. It will be available only to the users who use experimental update center. That's it. Okay, that's it. Looking great. Thank you. Mm-hmm. Yeah, I'll look into this. Thank you. Okay. So if there is no questions, maybe I could briefly show you how to develop Jenkins IO, because I believe that everybody will need to do so. What do you think, guys? Yeah, sounds useful. Yeah. Okay. So Jenkins IO website. Yeah, Jenkins IO website is based on GitHub. Effectively, it's configuration as code. So it means that whatever is posted here gets deployed to Jenkins IO here. And yeah, everything is driven by pull requests. So anybody is welcome to just submit a pull request if you see a typo on a page or if you want to extend it. Yeah, and there is a lot of pull requests going in. It seems that pull request build that is broken for an IO, but we will investigate what happens. And there are pages describing how to contribute. So effectively, everything is described on this page and everything I am presenting it will be also shown on this page. Yeah, do I have a little bit of Jenkins IO? So I just put a link here. So, okay. Then how do you develop it? If you have, generally, we use the decrysed infrastructure. So whatever you do, you actually need Docker. And there is a mic file which defines all steps. So in order to prepare your environment, you need to install make if you don't have it and you need Docker. The rest will be provisioned inside the Docker container. So for example, now when I do the development, yeah, you may see that I'm running on Windows now. Developing Jenkins IO website on Windows is a bit more challenging than on Windows, to be honest. But it's totally possible. Yeah, so yeah, we will get to it later. So yeah, there is a checked out repository. And yeah, there is effectively a make file which defines all the steps. So from all the list, you'll actually need two commands. One is a make prepare, okay. And the other are now on Linux. So one command is make prepare. The Docker image will develop an environment which will deploy all the Ruby and other stuff. And that's meant to move now again. Oh, like we're losing your audio. Sorry, when did you lose me? Just a second ago. Okay. So yeah, the first command is make prepare. It's documented and the second is make run. So when I click make run, I just start the local development environment. Okay. So yeah, it usually takes a while to provision everything because yeah, even in Docker with all the system, it takes a while and likely first run of make prepare will take maybe 15 minutes. And yeah, make sure that you have a good internet connection. So I'll just let it run for a while and show you what we have on the documentation side. So yeah, a lot of this said how to add authors. There is a special page about the Edinger blog post. So if you want to post something on Jenkins.io and yeah, we invite you to post on Jenkins.io if you're interested or if you have blog posts or whatever around Jenkins, you can repost as well. So yeah, you can do it here. For students from China, there is also a Chinese website. And yeah, if you want to post something there, please contact Rick, he will provide guidelines, but yeah, it's also possible to do blog posts in Chinese. Though for Google Summer, of course, the working language is English. So yeah, we expect everything to be on the main website. And yeah, if you're interested to repost some content or if you want to post content which is not directly related to your project, you can also do it on the Chinese website if you want. So yeah, there are guidelines for blog posts, but we can probably just take a look together. So yeah, there is content. So all information is based in content and actually the entire structure is here. So for example, if you want to have information about Google Summer of course, there is projects, JSOC. And for projects JSOC, you may see that there is project ideas, that there are a list of projects here and there are all information like index, mentors, et cetera. So this information represents the content we have on the website. I'll probably try to connect to the local instance. Okay. Yeah, it's loading now. So yeah, this is a Chinese website which has been started from my local environment. So you may see that there is Google Summer of Code. I hope it all wants. Yeah. So it's a new version I'm working on now. So you may see that there are some projects listed here and everything it's been loaded dynamically. So if you apply a patch in the ASCII doc, when you reload the page, the patch will be applied automatically without need to reload the infrastructure. And yeah, these are your projects. Currently these are the steps. And as a part of the first things, we actually asked you to update these steps. But you may see that there is just some basic information integrated and later we will be extending this information to beta. So yeah, that's it with Jenkins.io. So yeah, so the process is you develop the site. Once you have developed all you need, you submit a pull request. So it means that you have to fork the repository to your local account. You work with the fork and then you submit the pull request. And for each pull request, there will be a review process. Usually we just recommend to pink your mentors or admins and they will help you with the review because not everybody has merged permissions to the JSoc website, but all our admins do have such permissions. So once the projects are reviewed, we will integrate them to Jenkins.io and they will be delivered. For example, there was some pull request recently called JSoc, like for example, it meant Andre to mentors for remote projects, et cetera. So yeah, there is a lot of pull requests coming in. You just add this pull request and we will integrate them quickly. Okay, questions? Am I still audible? Yes, you are. Okay, cool. So yeah, that's actually what I wanted to present. So everybody is welcome to try this Jenkins.io and it's pretty much similar to pull request process in many Jenkins repositories. So when you need something, you will generate by pull requests or Jenkins g-reaches and then the reviewers will be able to help you to learn the changes. Yeah, speaking of changes, I know that some people still have open pull requests from the application period. So if possible, please spend some time to get them over the line, maybe as a part of coding or maybe as a part of community bonding. If you need any help from our partners, please let us know because yeah, we may have missed something. If there is no questions, probably we could briefly sync up with our partners regarding what we do with Jenkins.io, et cetera, or maybe we just closed on the meeting and then meet again. Excuse me, I just wanted to talk to Jeff. Hi, Jeff. So I'm under you as a student for Multibrand's Pipeline forget lab. So I just wanted to know if you would be available tomorrow, will we talk in the chat that we want to have a sync up meetup among the Mendocent students? I should be able to, yeah. Do you know what time you're thinking? You can contact me offline, we'll set it up. Okay, so the meeting time is 1 a.m. UTC, is it possible for you? Let me see. It's a bit earlier. Yeah, that works for me. Okay. For me. Okay, then so like Rick will be posting other handout link on chat at 1 a.m. UTC. So we'll meet up there. Thank you. Yeah, so if somebody hits issues with time zones, please let me know. We did the kind of spot check that all projects have some time zone over flow, but yeah, sometimes you get most stakeholders who are based in different time zones and yeah, well, it's a part of a distributed work experience. Well, yeah, it's not always easy, but yeah, it happens often. Okay, so anything else you can help please? Actually, Oleg, I have started a document to help track the progress with the expectations for the bonding, for the community bonding phase. I can share it. I think there's no issues with it. Would you like me to... Yeah, please go. To share it. Okay, so let me share my screen. Just a sec. Okay, yeah, so if it's a kind of checklist, it might be really helpful. It is a kind of checklist, just a minute. Did you see my screen? Not yet. Okay. It says I'm presenting to everyone. Does anybody see Martin's screen? Well, you're presenting to everyone, but you're not sharing your screen. Now you're sharing your screen. Okay. So I've started this community bonding tracking spreadsheet with, I think, so horizontally I have the different projects, identify the student, the lead mentor and the participating mentors. Then we have each item that we need to confirm or do during community bonding and I was just working on this list. So that's what I wanted to show. So now what would be useful is for, I guess we have to decide who is allowed to update this and who can confirm that. For example, if the bio has been submitted to NGENZIO, we could say it's done or we could have the link here. Something like that for tricky. Yeah, what you could do, you could permit comments for everybody. So you just share this permission to comment so that at least people can comment in the document and we can address the next comments. Okay. I'll add the list of students and mentors to the document. Yeah, right. It would be nice. So one of the things while we're on this page, you may see that I'm listed as mentor in many projects. Yes. Yeah, just to clarify, actually I'm mentoring only one project, role strategy performance improvements. For the rest, I will be rather a technical advisor. So it means I probably will add additional role there. So it means that I will try to participate in meetings when time allows and that if you need any technical advice, any reviews, I will be happy to do so. But yeah, it doesn't mean that I will be able to join the meeting every week, et cetera. Yeah, that is understood for actually technical advisors. Yeah, right. So yeah, we will still figure out how to do the thing because this is the first year we do technical advisor. Yeah, but anyway, I'm really interested to help all the projects here. But yeah, let's see how we organize. Yes, that's the goal of this spreadsheet is to confirm the roles as well. So thank you for that. Yeah, right. And yeah, again, while we have community bonding, there might be some changes in the teams. So yeah, some mentors can decide to join the project because yeah, we will be bumping visibility of all the projects soon. And yeah, maybe there will be more people. Maybe there will be people who have some unplanned activities. Happens sometimes. So yeah, we will adjust the list to the reality. And in addition to technical advisors, so some projects already have linking to special interest groups. So special interest groups, for example, cloud native special interest group for cloud features for external workspace manager and for remote in Cova Apache Kafka, platform C for plugin installation manager. And yeah, we will see what we could do for other projects so that we also get them involved in the bigger communities. So we think that special interest groups and Jenkins or subprojects, they have their own regular charts, so they're on regular meetings. And as a part of community bonding, we really want you to participate in them so that you get more stakeholders and you get more contacts in the Jenkins community. Okay, we can make this spreadsheet do what we need. So we'll keep it live if it's helpful. Yeah, I think it should be helpful. Okay, all right. So I'll stop the sharing. Thank you, Martin. Yeah. Like this, I just wanted to know your time zones and if possible for the other mentors too. So we can coordinate well. Yeah, it's something we could actually add to the spreadsheet. So I'm based in Europe. So my common time zone is UTC plus two, but yeah, I will be traveling a bit during the JSOC time frame. So it may change, but yeah, for me, it's plus two. For Martin and Jeff, they're based in the United States. Well, sorry, in America, Martin is based in Canada. Yeah, sorry about that. But yeah, so yeah, they have less overlap with Asian and Pacific region. But yeah, on the other hand, you can do meetings during the night in European time zone. I'd like to ask the same question to Klosso also. I'll say UTC plus two, I believe. Okay, Danish time, I suppose. Yes, correct. Okay. Yeah, right. So yeah, I think this is a topic you should discuss with mentors at the first meeting or in the chat because generally all this mapping work starts on the team level. So as Orkan means, we want to help you. We want to help you to be successful, but generally, project teams do the most of self-organization works in order to work on the projects. We just help and we'll debate if you need some assistance. Thank you too. So what else are we missing actually? Well, community bonding is a pretty flexible phase. Yeah, if you have any major time commitments, if you are unable to start community bonding, for example, this week, please let mentors know about that. It's totally fine. Yeah, but by the time of coding period, it would be great if the entire framework for the project is established so that you will just start coding because coding periods, they may look to be long, but I think there are just seven weeks and that is a lot of things to deliver. Okay, so actually I will be absent for like 10 and 11. Actually, I mentioned this in the proposal also. No, I'd have to, so that's why like two days, 10 and 11, I will be absent. Yeah, it's totally fine. So you generally just let your mentors know about this and it's enough. Okay, we can do this in the chat room also, I suppose. Yeah, it's better to do it in the chat room on the main piece because again, time zones. So yeah, we have this office house meeting. I'm not sure that everybody can join this meeting because well, the time probably is not that convenient, especially for some mentors because a lot of mentors have meetings in this timeframe. So sometimes it's difficult to join. So we do not expect anybody to, everybody to be on this call. Or yeah, sometimes people will be missing team meetings as well because yeah, life happens, everybody has various trips, vacations, family emergencies, whatever. So it's better to use communication chat not to have conversation history so that you can use this information between each other. Okay. And like, apart from this common conference, will we having like project specific video conference also, sir? Like project specific. Project specific, what? Confluence? No, I mean like the video chat, like project specific, like for instance, mine, specific channel to like talk about our projects. Like this happens to be a common one, right? So yeah, it's common, it's expectation from all the teams and we expect all teams to have at least two meetings every week. Okay. All right. Whether you decide to do it in the video chat or whether you decide to do it in the chat, it's up to you. But our expectation that there are sync apps, though yes, some teams can experiment. So for example, if you want to try a service like status here or whatever to have a synchronous sync apps, you can definitely try it. But yeah, our initial expectation that all teams start from regular meetings. Okay. Okay, thank you sir, thank you. Yeah. Thank you. Yes, speaking of meetings, at each evaluation phase, we will be performing Jenkins online meetups or other recorded events so that you are able to present your work to others. It's really yet to be decided how we will be doing it this year, but yeah, we will be setting up time slots for meetings with several mix advance because we need it in order to properly announce the events so that we will be creating doodles earlier for recorded meetings which are over the regular schedule. But yeah, you'll like to have these meetings. The example trainings for QTs, everything will be recorded, everything will be posted. Okay. Okay. Anything else? Nothing from my side. So there is nothing from me as well. Martin Jeff, would you like to add something? Nothing from me. I'm good, nothing from me. Okay. So then, yeah, thanks everybody for your time. Next regular meeting please in one week. If there is a need to change the time slot, yeah, let's use the JSOC million please if you want to propose a time change. But I would rather default to this time slot but it's a significant need to change it, okay? So yeah, thanks everybody. Thank you. Thank you, bye. Yeah, bye. Thank you.