 We're on this computer. OK, so I am now recording. Sorry, everyone, that we're starting so late. Thanks very much for your patience. So how many people are there from the pool? Just us. I think it's just you. Oh, Markey has joined. Good. Yeah, I'm here. Excellent. Thank you. My sincere apologies for my complete ineptitude in running YouTube live. Thanks very much, Markey, for being the test drive and for being patient. Hit is completely OK, and I understand. Thank you. We just got an expectation infrastructure issues. So yeah, I was unable to start Hangouts on Earth recording. And then we tried with Mark. We were still unable to run it. So yeah, finally, we are 20 minutes late. Right. And my apologies. And I think, oh, good. Hey, and I've shared my camera so you can now see my face. OK, good. So I propose let's talk through the things that are on the agenda are there. We've got on the agenda open action items as one, a Java 11 status check, Google Summer of Code, and YAML on Windows Service Rapper, and Custom War Packager. Are there any things that need to be added to the agenda before we actually start doing the agenda? Well, I think that since the meeting went south a bit, so there is no time pressure to have Custom War Packager demo. So maybe we do it next time when we have more participants on the call. Great. All right. So yeah, I'll move on to it. And then in the YAML configuration for where we have Alex on the call. Yeah, if you're generous, I propose to have a discussion. If not, yeah, I'll probably take it offline. OK. I didn't kiss for reasons, so why not? Great. Excellent. Good. I was actually prone Oleg to say that we let you talk briefly about Google Summer of Code and how that's been proceeding. Marky, were there specific topics you needed to bring to the meeting? Or Jeff, I see that Jeff Pierce has joined us. Are there specific topics you wanted to bring? From my side, no. I'm just more here to answer if there's anything with the Google Summer of Code. Oh, thanks. Great. OK. And I assume that's probably Jeff's reason for being here as well. So it feels like we should take advantage of this time and let's spend some time on Google Summer of Code. We did have a few open action items. My summary of the action items is nothing further progressed on those action items to propose. Oleg, anything else you wanted to say on action items? Well, so one of the action items I was working on, a community bridge stuff, we will be discussing later today the advocacy and outreach. So it's a way, for example, to have this Windows Service Trapper project accommodated if you want to proceed with that. But yeah, regarding the action items we have in the list, well, it's pretty much the same. So multi-architecture package I came to do with us. I got feedback from the, but yeah, basically, we need to fix the scripts, because it doesn't look to be infrastructure issue, but unfailure, not an entry issue. Oh, to not be an entry issue. Yeah, some of the pipeline library works properly. It passes the environment. We have reference jobs, which are unsuccessfully. But the deployment scripts don't accept credentials, so they just got listed there. So yeah, I'm not sure what I can do there, but yeah, I just don't have much time to deep dive, though I could probably do that later. Regarding other action items, code sending infrastructure, there is a thread by Olivier. Basically, it's one item above. OK. Yeah, it's for code sending. And regarding the support policy, again, I'm blocked on stakeholders. So I just want to get someone signed out before I press it in public on that. Yeah, it is that the support policy is not an immediate topic for us, because it was kind of blurry for 10 years. And well, yeah, they just broke it maybe one month ago, but that is fine. Great. All right. So then I would think, let's take this time for Google Summer of Code. I'm going to strike, or we're going to ignore any Java 11 status, because I've not seen anything that was urgent. So let's talk. So I'm not sure which topics are Oleg, are there particular topics on Google Summer of Code that you wanted to be sure we addressed here, or concerns, areas of? So the Google Summer of Code, you have one project, which is Plug-in Manager and SIL-i2. This project is happening under the umbrella of Platform Special Interest Group. We don't have Natasha on the call today here, but yeah, as far as I know, she was moving from one place to another. But yeah, I think that step from the next will have a lot of data in the platform. Great. All right. Any other hot topics then that we need to be sure? In Google Summer of Code, I think no. So yeah, once we get to a prototype, maybe in one month or two months, something that would be interesting for this SIL-i2 to consider. Another project which is somewhat related is a remote and cool Apache product. It's got options for components, and likely it will involve enhancements in the packaging. But yeah, this project is from the umbrella of Platform Special Interest Group. So we were unable to get in the meeting together. Maybe I will consider a little bit to talk a little bit. And yeah, what else might be interesting? We have another project about the whole strategy. Obviously, this project has nothing to do with Platform SIG because it's a secure tension. But the first coding phase targets performance testing framework for Jenkins. We have to do a message. We are not going to get a prototype soon. So maybe in a couple of weeks, they will be able to update. And this project can be interesting to SIG members who work on performance testing. Yeah, so you say that a platform testing framework, so we can see we'll use that to compare Java 8 and Java 11 or various hardware platforms? Theoretically, yes. But well, it's just the Java microventure framework, GMA-ish. So it's one of the default standards in Java mode. So the whole idea of the current prototype is to actually have something to do with performance. So when you have a Jenkins tool, and basically which perhaps the logic and bootstrap Jenkins instance maybe is applying configuration as code and other such things. So we'll see it to be decided. But yeah, basically, the function is the same. And then you just run in microbenchmarks. Excellent. Thank you. OK. Yeah, so it's something to discuss maybe at one of the next meetings. So now I just go ahead and write. OK, so it's pretty much all for me in terms of JSOC. Maybe Marky or Jeff or one plus something because they also participate. I don't have anything from the Google Summer Code. I'm just meeting with the students tonight at 9 Pacific to go over the GitLab project. Oh, and see, for me, that's it. Well, that's a particularly interesting. Thanks, Marky, for leading that. That's for working with them on that. That's a great hope. Thank you. You're welcome. Yeah, so there is a team of mentors. Rik, it's a little bit surrounding the GitHub. He basically leads the project. Yeah, plus there is a number of other mentors. And Marky, a bit to join the team yesterday because there is already a bit of progress, for example. A GitLab API plugin has been already posted, I believe. I think that having a comment would definitely help to proceed. So if anyone is interested in GitLab as a source control management system, you're welcome to join this project. Great. Thank you. All right, I see Alexander, you joined us. Were there any topics that you wanted to be sure that we covered today, Alexander? Yeah, my topic is about the project which was actually dismissed. Hello, everybody. But I have some idea which I could continue to develop in this project. And we could use the results of it like a practice for my university if it's possible. I just had a conversation with my dean about this. So it could work out. So basically, it's the topic below, Mark, about YAML configuration support. Oh, good. OK, thank you. All right. Yeah, this is a topic. Yeah, so if folks on the call are interested, I can briefly show what was implied in this project. Yeah, as Alexander said, we were unable to accept this project this year. It doesn't say that the proposal was a bit because we had a lot of applications. Finally, we had to make many tough choices. That's why I'm explaining this, for example, because we would be interested to have a way to make more projects later this year. Because we got a number of really good applications which we would like to have somehow. But unfortunately, not as a GSOC this year. I would love to see if you're willing to go ahead. OK, so I can start to screen share when somebody else is doing screen share. See, so I have to stop, share, and do you now have permission to share? Yeah, I guess so. Yeah. OK. So there is some ice cream? Yes. Yeah, I have 35% of my laptop left, of my battery left, but it shouldn't be enough. Yeah, we've got about. Yeah. So yeah, we have a project, so yeah, we had a project idea about Extended Windows Service wrapper. It's just the bottom more young configuration support. So me and Darnak have your potential mentors. And yeah, basically, this project is about Extended Windows Service wrapper. So Windows Service wrapper is a company that used Jenkins in order to install Jenkins master and also Jenkins agents as Windows services. Why do we use Windows services? Because it improves failover, it improves stability of the system, and it also improves various edit failure features. For example, a runway process killer so that you'll be able to kill processes which are not killed properly when you use Batch. Unfortunately, it happens sometimes. Then there are some additional features like just monitoring, integration with system logs, and all other things. And yeah, one of the examples of usage authority is actually Windows slave starter model. So it's a part of Jenkins core. This model installs agents. So effectively when you connect an agent using the Java web starter using CLI, you have an option to install it as a Windows service by clicking the button. And it's been handled by this plugin. So there is XML file, which is Jenkins slave XML. We still haven't renamed everything to agents in this part of Jenkins code base. So you may see that there is some configuration here. For example, you can configure what you run, which Java version you use, which arguments you pass. So you pass Jenkins agent, these first 10 arguments. And then we have some additional logic, for example, of the automatic failure. So when a process fails, we restart it. We have a log rotation enabled by default in recent versions. And we also have automatic agent download. So when you use Windows services and when your master is connected over HTTPS, we do automatic download of new remote ant versions and new Windows service wrapper versions. Because it was one of the issues of all Windows agents, because before, they used to be always saluted. And then there is a runway process that I was discussing. So yeah, this is a kind of sample configuration. You may see here that actually it's in XML. This configuration is pretty complicated. One of the ideas was to actually follow the approach of what we do in Jenkins configuration as code for you and other companies, and threat support of YAML. Actually, if you take a look at full configuration, it's even worse than what we have in default settings. Because there is a huge number of options, like environment variable management, various descriptions, automatic start, which delays for services, advanced login, whatever, whatever. So the configuration can be extremely long. We have some samples in the repository, but the idea of the project was to just move everything to YAML, offer tools like, for example, just JSON schema or YAML schema, which would allow to verify conflicts. Right now, there is no access defile for Windows service wrapper. So there is no schema, which would allow to self-document and verify configuration files. And, yeah, it would be one of the interesting improvements in the Windows API system. It would also help Windows installers because Windows installers currently, I mean, Jenkins, MSI, Windows installers, so that Alex Earl is currently working on a new version, but it still uses Windows wrapper under the hood. And, yeah, it would be nice to apply some improvements in order to simplify work done by Alex. And, yeah, you can also see that there are some other things, for example, Partitforge integration, and it's like package manager for Partit and the levels, other implementations, which could be in the scope. But, yeah, basically what was proposed in the project, firstly, to improve configuration and maybe also to focus on other stories we have in this repository, like better login, another thing, such things. So, yeah, this is the scope of the project we had and we had a discussion with Alex multiple times before. Well, as a part of student application we read in Google Summer, of course. And, yeah, so now, yeah, it's not Google Summer, of course, so we are more flexible in terms of what we could do here. And, yeah, Alex, I'm happy to help as a kind of advisor in this project. So, yeah, if you are interested to invest your time, I'll do my best to assist you and probably somebody else from a special interest group will be also interested. Because, yeah, there is a lot of Windows users in Jenkins ecosystem. Okay. Yeah. Yeah. I mean, yeah, I would love to take part, just we just need to formally sign the papers at the end of it, like, it will be like a practice for my university, so. Speaking of that, do you need any formalities from the Jenkins project set? So, yeah, as an open source community, we are happy to welcome you. We are hoping to provide some assistance. But, for example, if you need to do some paperwork from the Jenkins project, that may be quite tricky. So, if it's needed, it would be better to know about it in advance. Like, as far as this time, when I discuss with my Dean, so the process of practice in my university, it's like, I will provide the paper on English language, which states on what company I will make a practice and they need five copies, five original copies of these stamps, which should be stamped and the minimum length, as far as I know, it will be like eight weeks, so around two months, and at the end of it, it will be like a short paper about practice and, which should also be stamped, as far as I know, in one, two, three, four, in one, in one original material. That's the administrative requirements, which I got from my university. And by that way, I could earn some credits. Yeah, so paperwork is required before and after the project. In your company, sorry, in your country, how is it considered as an internship or as practice? Because just to make sure whether it's also a financial site. It will be like internship, I could post this paper on GitHub, for example, in whatever place which you would like. It's not the private document. So I could post it on Google Docs or somewhere else. You could see it and make some comments or whatever. And yes, it's great. And I don't think I could have the same availability, which I stated for Google Summer of Code. I think it will be less because it's a bit different situation, I think. If it's okay for you, and I mean, I could spend less, but still around, I don't know, around 20 hours a week or something like that. Yeah, so for us, if you are active as a contributor, for us, yeah, if you can spend one hour per week, two hour per week, it's already something helpful for the community. I appreciate that one thing about the practice, yeah, I'm not sure what are the conditions there. So paperwork is something I can check because I can't really export and come into the bridge, but the community bridge won't produce these papers as practice. So, yeah, I have an action I can. I'll take a look whether it's something we could do. Okay, I will post, I don't know where, I will post the papers on Google Docs and you could see and ask questions. Yeah, actually I could do it now, maybe even, yes. Okay. Yeah, so one thing you need to know about Jenkins, so Jenkins itself is a company. So that's why we might have some issues. So Jenkins is under umbrella of continuous delivery foundation, continuous delivery foundation is under umbrella of Linux foundation. And yeah, Linux foundation is a legal entity and yeah, CDF foundation is also a legal entity, I believe now, but yeah, we need to check whether it's possible to do this paperwork. So what I will do, I will reach out to proper people in order to kind of show that it's technically possible. Yeah, I just need to know, is it just conditionally, yes. If it's okay, I mean, I don't need to try at this moment or at that moment. Maybe it also could be put at the end of this practice. We could call it practice, but whatever. So yes, and I wonder who else could help me with this project? Okay, Oleg, maybe somebody else. Who is, where should I raise questions and my progress and something else? So what do you think? Yeah, if you do this project, I believe it would be interesting for platform specialist group because it's window support and yeah, I think we can keep the same framework. So yeah, we have for this meeting several two weeks or maybe we could have additional meetings to sync up. Yeah, if you do 20 hours per week, probably one meeting per two weeks won't be enough. For sync ups, the gratin, all kinds of, so gratin cardameters, we can do community outreach. So for example, if we have, if we come to that paperwork or something we can technically do, we can contact Windows users in the Jenkins developer and in the platform and yeah, most likely we will be able to find somebody who's also interested at the same here. So we do service tracker. So yeah, even if it's a part of Jenkins. Can I still shine my screen? Yes, you are. Yeah, so yeah, it's not used only in Jenkins. So maybe by just for some issues here, like let's do it in YAML. Yeah, there are 157 watchers, et cetera. Yeah, maybe we will be able to find someone from outside the Jenkins community because if you want to keep a similar scope as it was proposed in your GSO application, there is some Jenkins part, but yeah, the most of the code is actually available here and it will be available for other projects as well. Yeah, so Alexander, I think either the Gitter channel for PlatformSig or the PlatformSig mailing list and they're, Alex Zerl and I are both interested in Windows. Oleg is now a Windows user. He may not be thrilled about being a Windows user, but he is a Windows user. So we have several of us who are on Windows and are so I'm confident we're happy to help if we can get past the other hurdles, you know, the formalities and any requirements there. We would love to have your contribution. Yeah, right. Yeah. Okay. Yeah, regarding your practice, what is the approximate timeline for this? So eight weeks during the summer. So when it usually starts? At the moment I still have an exam on six of June and after that I will be more or less three, but we could, it won't be, I mean, we could sign this paper at maybe the later moment, but I could start, I will continue this project now and spend time in order to receive some tangible results at the end of August, like Google summer of course students. So it will be some, it will be as well with some deliverables at the end of it. And based on this, we could continue to work maybe on the next year, but we will see. Yeah, it's something to discuss. Yeah, so far, yeah, one of the things, yeah, if you'll start working before June six, it's perfectly fine, but yeah, currently we cannot guarantee that this paper just is possible and then it will be possible to complete it by this time. So it's something to keep in mind because yeah, if you do it until this paperwork is confirmed that it's in a kind of non-binding state because yeah, we need to explore the options and right now I can say for sure that we can do it. Okay, okay, maybe we will sort things out and as a way in, it will be some. Yeah, so we have for the next basic meeting in two weeks. So it's approximately around June six, at least. Okay. Oh yeah, maybe we could come there. I have an action item. So once you provide the document samples, I will reach out to proper context. And yeah, I also see whether we can find mentors because for me, I'm personally interested in this project but yeah, I'm already heavily invested in JSOC and I have limited time. So I will try to find more people and if I'm successful then you should be able to do that. I just posted the documents on Gitter. Okay, cool. Yes. Okay. Yeah, that's cool. I need permission, but yeah. So yeah, if you need permission to me, Mark. Oh, okay, okay. Just a second. Oh, I don't make a share. Okay, just a second. So yeah, if you are not comfortable to share then is everybody is still something? No, it's okay, okay, okay. I think, wait a second, it's not this group, but okay. I think it will be different link. Yes, this one. It should have access to read as far as I, yes, as far as I understand. Okay, we will check it after the meeting and kind of the specialist will come over. Yeah. Yeah. And just one thing which I should especially mention, in this document it stated that the company should pay, but we should not treat it like that. I mean, it's okay for not to do in this as far as I understand. It might be a problem for us because you defer the state, so we will definitely need to run it through the delivery foundation legal advice. Because yeah, it might be not a problem for you personally, but it might be still a problem for the foundation. Oh, okay, okay, okay. Okay. So yeah, so this is something we will verify. But yeah. Yeah, if I need to raise additional questions with my university administration, please let me know as soon as possible. I will do it. Yeah, right. Yeah, so as a part of community bridge, we are technically able to do paid internships. But in such case, we would also need to confirm the budget. We will need to justify these budgets. We would need to confirm it at the governance meeting and other such things. For example, we do pay the internship without Rishi program. But we will, yeah, if it implies payments, it also complicates the things even more. So I believe that if there is a financial side, if there is a regular review required, we definitely won't be able to provide a response by June 6th or so. But no, I won't. Okay, okay. I mean, I don't need it, but as far as I know, at this moment, it's not obligatory. But I will double check this with my administration. The first question about this. Because for me, it's more important to make progress on this project. Yeah, and yes. Yeah, so community set is something that we definitely welcome you. We will try to find advisors, et cetera. Yeah, we're gonna promote it to site for practice. Yeah, we need to review whether it's possible. Okay, okay. Okay. Yes, thank you very much. Okay. Yeah, thank you too. And thanks for the interest. So yeah, if something doesn't work out here, we definitely have a Google Summer report next year. So whatever you explore now can contribute towards the future proposal. But yeah, let's see what we can do something further. Excellent, thank you. Thanks very much, Alexander. Thank you, Oleg. I think we have gone past our typical time. I'm prone to say, let's call an end to the meeting for now and meet again in two weeks. Any other topics we need to cover before we close the meeting? Not from my side. So yeah, we had custom work packaging on the agenda. But yeah, again, let's do it next time when we have more participants. Right, well, and we may switch to using Zoom or we may figure out, have me learn how to do YouTube live correctly. One way or the other, I've got two more weeks to fix my mistakes. Thanks, Oleg. It wasn't your fault. It doesn't work for me either right now. And it was working one hour ago, so. Okay, great. Okay, so yeah, thanks everybody. And thanks to...