 Okay, we should be live now, so we have today's June 5th regular JSOC meeting, we are recording this session as usual, one of the things to keep in mind that it seems we have some issues with handouts on air, because we had two recorded sessions day and yesterday, and in all sessions we had issues with screen share recording, so just in case we do some screen share, maybe the information may be lost, hopefully not. Okay, we don't have a specific agenda for the today's meeting, some we got a doodle sent out for transport evaluation phase, so on May 24th, sorry, on June 24th, the evaluation phase starts, and what is our plan? By June 24th, the majority of tasks within the scope for field coding phase is completed, the mentors will start the evaluation and we will use this gap in order to do some org things like doing demos for other contributors to present the work for stakeholders, like special interest groups, and also some planning for the next coding phase. So our expectation is that by June 24th we finish active coding for the phase and then we do some cleanup things, etc. needed, but then coding continues in one week. So this is our plan, and yeah, do you see my screen by the way? Yes, I do. Yes. Okay, now this thing was definitely messed up, but it should be okay, so yeah, this is what we have. Regarding the rest, I think we just keep coding what we discovered over past weeks that not all students requested the knowledge transfers, and not all students got the right knowledge transfers as a part of community bonding. So if you feel that anything is missing, let's discuss it now, and yeah, if needed we will schedule additional sessions. So yeah, we have several people on the call, including Jen. So is my screen visible? Of course, Natasha says it's not. Yeah, I can see it now. Okay. So Natasha, do you have all the information to do the coding or doing the additional knowledge transfers? I have some questions actually, it's like about them blockers. About knowledge transfers or about the project generally? Yeah. I think it might be some general, general knowledge, so if I should ask it right now. Yeah, well, we'll bring the topic up and we will see whether it makes sense. Okay. Just show you what it is, right? Yeah, well, so what's the area you want to talk about? All right, it's just about the, oh wait a minute, I'm going to share my screen. Okay, please do so. Yeah, because basically maybe Martin understands what's the context, I don't understand what you're asking about so far. Okay, wait a minute. All right. So here is a question. So basically, I want to, I have a base class called, no, it's not this one, called, I built the wrong plugin, sorry, it's a mess. Here, I have no base class called disk, right? And then I have some derived class, so which means, and there is a, and there is a heat hero list that is called inside the disk pool. If you look at here, you will find there is a property called repeatable hero property and it points disks and this disk is a list, right? It's a list of disks. But I want the, so potentially there might be multiple types of a disk. What I want to do is like, every time when I load the disk, I want to first load the config jelly here and these are the fields in the base class and then I want to add some, I want to add a, I want to include the config jelly in the specific disk type here, like in here. There are some, there are some type specific fields of each derived class and then what I do, I noticed that in EC2, it does it like this, there's config.jelly, just do some stapler, include the descriptor and something like that. But when I do in my plugin, it just doesn't show up. I don't know, is there any, anything I needed to, to like some prerequisites I need to meet to make this mechanism work? Well, the mechanism you're looking at, EC2 plugin is quite outdated mechanism for jelly because what we use is a repeatable property, describable property and other things. So what you see here is all the implementation, which was used before. All right. Yeah, it's still operational, but in the most of cases, you do not really want to have it in the new code base. The question itself, yeah, maybe it's something to ask me, but yeah, if you want to ask me, that is, but you need to mention me in GitHub or maybe bring a question in the mailing list. I didn't know that you have such a question. I'm not sure when it was asked. I planned to ask you here on Wednesday. It's just a question. Yeah, after the meeting is perfectly fine. So we firstly discussed general topics, so then we can use the rest of the time to do such Q&A. But yeah, basically the approach for such questions is that you just ask in the mailing list or in the chat. Because if you wait till this meeting, you'll probably lose several days while waiting for this meeting. And yeah, we want the project to be more dynamic. Okay, thanks. I have done my asking. Okay, so yeah, we can discuss in details later, but yeah, it's probably not the question for this meeting. We can discuss later. Okay, back to knowledge transfers. Do we need any? Okay, maybe another question. Does everybody know what is expected by the end of the first coding phase? I think yes. Yes, so if you need this information, this information is actually available on the student page. Actually, I know. I know. I mean, I know. I raise my hand and say I know. Just for others as well. So if you scroll through this list, there are some details about evaluations. But yeah, generally, we expect you to have online presentation. This is what we have doodle about. And you publish a summary page. In addition to that, of course, please spend some time on planning the next phases. Because some projects in the first recording phase already struggled to go forward because there was no clear plan what to deliver as a part of the first coding phase. So keep it in mind when you start the second coding phase and use this time in order to do planning, because it should really help you to iterate quicker when the coding starts. Okay. Okay, I know. Sorry, I didn't open my mic at the end of my mic. Yes, thanks. Okay. So regarding the rest, Natasha, do we have any questions? Yeah, I would prefer not to ask them when everyone is on if that's okay. Okay. Okay, that's fine. So do you want to talk after the meeting? Yeah, that sounds good. Okay, let's do that. Or actually, we have the org admins on, or do you just want to handle that individually? It depends. Natasha, so if you want to have other org admins on the call, let's do that. Yeah, I think everyone would be fine. Okay, then I'll just send a meeting and invite right after this meeting. So if you do it, well, maybe in 30 minutes, is it fine with you? Yeah. Okay, then I'll send the meeting and compare it with the discussion. Yeah. Okay. Okay, I dig up in the rest. Any other questions? Yeah, there's some background discussion from somebody. Okay. Yeah, I guess it was Swedish. Okay. Okay. So if there is no questions, I think we can just close the meeting or maybe managers and org admins would like to add something to the conference. I just want to say, Oleg, that it's much easier for org admins to track questions in the mailing list. Yeah, so questions go to the mailing list as long as possible. Regarding the question from your fate, if we are on this call, we can take a look. But firstly, there is no guarantee that this question really makes sense to discuss with everybody, then it might be complicated to just do it because somebody needs a background etc. So the preference. I have a question for Natasha. Natasha, do you have a link to your design document? No, it's just something that I wanted to talk about. Okay, I'm just trying to complete the important fields in the community bonding tracking spreadsheet. So that's why I was asking. Yeah. Okay. No more questions from me. Yeah, I'm missing any other fields, Martin. The repository for the working hours plugin is not set in this spreadsheet. There is github.com where you can see a working hours plugin. So this is the main repository for the project and I believe that actually it's one we used. Just a second. I'll show my screen again. Do you see my screen? Yes. Working hours plugin. So this is the target repository where we expect all the changes to land. At least this is my understanding for the project. Okay. Yeah, there is already some cool requests, but yeah, I guess that, yes, it was discussed in the Github channel, the plan that Jack will be pushing code here because right now there is a private repository in Jack's repo where the coding happens. And yeah, I also noticed that it's something confusing for people because there was a question in the mailing list from Zachary about the progress in the project and since there is no full request, it's really hard to track it down. So yeah, basically by the end of this calling phase we want to have all the projects in public operating with the NGTCI organization. Okay. Okay. So yeah, I think that it applies to all the projects. Okay. Basically, we have hosting requests from Natasha and other projects already operate within the public, so the remote and crawl strategy, external workspace manager, they use existing plugins, promoted builds for pipeline, they also use existing repositories as a target. So yeah, I think we are good there. Anything else? Nothing for me, Oleg. Yeah, nothing from me as well. Yeah, I sent an invite for this in Cubs, so yeah, we will jump to another meeting in 10 minutes. So if you want, we have 10 minutes in order to discuss other stories. Okay. Do you want to discuss your question or do you want to proceed offline? Well, I think I will post a new mail in the public mailing list. I think you said that the previous mail is not, the hair is not good enough, so I just want to create a new one. Okay. So yeah, when you create a new query threads, make sure that you put a topic subject to the title so that I'll try to keep the mail as long as possible because I can track the issues in one mail, but it looks like it's not good. Okay. Thanks. Okay. Thank you all. So if there is nothing else left to discuss today, thanks everybody. Let's just keep this meeting short so that everybody gets more time to actually write code. So yeah, thanks all. See you in one week or the next project meeting. Okay. Sounds good. Thanks. See you. Bye. Bye. Okay. Thanks. Bye.