 I thought it was automatic, like with the CDF window. Yeah, it's, it's, it would be except sometimes we start meetings with private conversations and don't want to record it. Okay, so, so, Neil, this was one where where for me this project ideas is a good example of, hey, get started by cloning it and running the tests do some experiments and, and this page. Installing Docker is actually already using plugin installation manager and gives you a good experiment that you can run. So it's, oh, hey, look, I, I, I started with the base image, and you and I can ignore these things this stuff is all magic needed for tutorials. The second line on now I have all these plugins ready and a Docker image that I can use to build it to experiment. So that's, that's the that gives you a hint of what this could be. Can you please put the link to the channel of that. Yeah, you bet. Absolutely. So chat to the Gitter, to the Gitter channel, if. Okay, thank you so much. You're welcome and, and that is a good place to ask questions as you develop your proposal, as well as attending these office hours and our Slack channels. So people are definitely willing to help you. And yeah, we're very excited about G sock and and our number of very good developers who will more than happy to help mentor you through the proposal stage as well. Now, now one of the one of the interesting challenges of this particular, this particular project is this, how can we use other update centers and there is, there is, at least for me some very, very important information that you need to learn about how does Jenkins do downloads and how does it check an update center. And, and how does it use the data from the update center so, for instance, there's this site updates dot Jenkins that I owe that is is the introduction to the Jenkins update site. And this thing gives you the be the starting point to learn more about how Jenkins performs updates because there are 200 over 250,000 Jenkins installations updating plugins and Jenkins checks sites that are globally distributed and does interesting and fascinating things with trying to assure that it doesn't overload any single server so update center is is good. And I'm posting the link to that as well. Okay. Can I ask another question. Yes, please. After now I have done is what I have done is install the Jenkins and some experiments. So is there any easy way to easily engage with this project. I mean, is it essential to have a good deep knowledge about Jenkins store. No, no, actually it's not. So, at least I started contributed to Jenkins because I was interested, and I didn't have any particular skills other than I was interested. So if you're interested. Now Kara maybe you can offer additional insights there on on what it's like to be a newcomer. Indeed, I've just joined the Jenkins project from from a different project and it is an on ramp but we do have a lot of documentation on getting starting to use Jenkins and learning more about how it works and also again contacting people on the Gitter channels or the side channels is really helpful. In addition, one of the nice things to do when you're engaging with learning about Jenkins for the first time and how it works. If at any point the documentation isn't clear to you or even if you find it's incorrect, like, it's a great moment to start making your first PRs and contributing to the project like that's, you know, fantastic way and always appreciated. So that's a nice engagement. Thank you. My voice is audible. Yes, how are you. Hi, hi, I'm good. Hello everyone. So, from last week, I learned about Jenkins and made my first plug in and extended it, and I have a question like there is one project idea in the project list for regarding rest API, which is I guess being continued from the last talk, but as like this year, the, the G shock timeline is like cut down to half. So is the project is the same. Yeah, this one automatic specification generator. So I mean, I read, I read this project idea twice or twice but I don't get much about it. I don't know but I'm just learning about Jenkins. Yeah. Yeah, contribute. And that's, go ahead, Kara. No, this is going to say, um, we don't, we don't expect you to come into this project with a huge amount of Jenkins prior knowledge so that's absolutely fine that you're learning that is the point of Google summer of code. So part of your time now as you prepare for your application is actually to take these project proposals and and or this project ideas and to formulate them as proposals so to engage with the material. And in many ways kind of form your own project proposal so the, the part of this idea that interests you the most or that you feel would be good for you for the time of Google summer of code. And that is what you apply to Google summer code with that proposal that you've crafted yourself, but this isn't something that we expect you to do alone you're more than welcome to come to these office hours in addition. So we have a link to our GSOC Gator channel, so that it's a really good place to ask questions and responses tend to be very quick so and very helpful. As well we have Slack channels for Jenkins, which are also good. Good to hear. Yeah. So that link to the Gator channel is in the GSOC. Yes. Can you see that link is sometimes with zoom. If someone's put a link in before you join those prior links are visible. No, I can't know. Okay, I'll repaste it. That happens. Okay. I'm already in this group I guess yeah. Excellent. The team is helping me a lot to setting up my first plug. Yeah. Very good. Well, and you expressed interest in this rest API. The, the Jenkins rest API is rich and very, very deep, but is also not fundamentally documented in a general consumable way. And I think that this open API specification concept would allow us to more correctly describe and more thoroughly describe the rest APIs that are available in Jenkins so the project is, is fascinating to me because what it's, its goal is to is to to see if there is a way to automatically extract rest API documentation from Jenkins, based on its source code or based on its Java classes. And if not identify what we would need to do to encourage people to create rest better rest API documentation as they're creating new content as they're creating new components. Okay, so basically like regarding like rest API so someone is using rest API like in the Jenkins so what this project what this task is going to do is going to create a documentation for that rest API is that using open API right. Correct. That's that's the goal here and and Jenkins Jenkins has a rest API. Right. Let's let me just bring up the rest API so let's on any Jenkins page if you append the suffix slash API to it. You'll see a description of the rest API and how it can be used with XML or JSON or Python and and there's good guidance there and and that works truly on any location so if I navigate to a particular job and go look at that particular job and look even at one run of that job now I can say slash API and the API is specific to that job. So, so the rest API is quite rich, but that richness is not backed by good documentation, which is what this this proposal is offering is that having a rich API is great but having a documented rich API is even better. I see, I see. Yeah, now I understand I guess. Okay, yeah. Okay, I will look into this like like I want to work with rest API so that's why it's also fascinating to me. Yeah. Well, and, and this this is for me I find it interesting because Jenkins rest APIs are contributed by plugins and because they're contributed by plugins. It's not it's not that you can just read the core and and generate the entire rest API. The rest API comes from from each plugin that contributes may also contribute rest API endpoints. So, Sagar, did that. Do you feel like that will help you get started exploring your interest in rest API. Yeah, I guess somewhere I will get started with this now. Yeah, I mean, I will explore about this API more and if I have any question I will leave within the SIG. Yeah, great. All right, so far I have a lot of time to work on it. So maybe I guess, yeah, I will work on it. Yeah. Yeah, no, no, I like how how this how Oleg has phrased this one that the student is expected to make a few projects for a few proposals on how to specify and generate. That word, a few, the intent is that not all of them will be accepted. In fact, each of them will be used as a way to tune the, what should the final project plan look like. So the sooner people start discussing the healthier it is in those discussions. Oh, I think this is a good idea I think we should try that. But don't be, don't be, don't hesitate to offer the proposals, because it helps helps you learn and it helps others give guidance so that your learning can be directed more effectively. Yeah, okay, yeah, I guess, yeah, okay. Okay, great. So I just want to repeat so that I don't miss anything. So basically, so currently there are APIs for in the Jenkins but there are no not well documented so in this project we are going to document those APIs, not all of them because there are a lot of plugins also that are integrated with them but at least few of them to just have a, at least architecture of getting started with this project I guess proposal. So I would add one important word there. And that is the automated rest API documentation because this project idea is not actually an exercise in creating documentation. It's an exercise in creating the program that would extract the documentation that that already exists in Java dot comments or in the API signatures. So the challenge here is just truly a programming exercise now the documentation exercise. Yeah using swagger or whatever open API right. Exactly. Good, right. So, so just wanted to be sure we've we've also participated in Google season of docs where we focused on documentation but this is a coding exercise now the documentation Yeah, yeah, yeah, I already read about this little bit of yeah, yeah, swagger. Yeah, so I will look into its first I will try to understand the swagger and then I will look into the API stuff. Yeah. Great. And I mean previously what you like talked about like docker and I will and is there is a recording of this meeting we I can access after this. There will be yes so well okay there will be after the initial roughly 10 minutes where I had forgotten to turn on the recording. Yes, yes we will post the recording and the recording will be available. Yeah, that's great then because I will refer this later on if I forget something. Super. Yeah. Okay. Let's see and there were so we've we've talked today about two of them. specification to have the project ideas. We could go into remoting monitoring or Rahul you've you've been relatively quiet. Was there any question that you specifically had. Hi, everyone. Hi. Right, so actually there were a lot of people in my room earlier so I couldn't turn my mic on. Right, so actually I am relatively new to this field. I mean I have been sort of dabbling in programming but I haven't really gone very far. So I'm pretty new to this and saga basically forced me to apply. So actually, as of now I'm very few less as to what Jenkins is as to what this API is. So I'm just trying to sort of keep up with what you guys are saying right now. No problem welcome welcome just like all of us we all start start at the beginning so that's great delighted to have you. There are many very effective tutorials on how to use Jenkins on the Jenkins site. So for example, if we go to the documentation here tutorials, the ones that that I've used with Docker I like a lot but using build tools because I cared about compiling software and in my case I tend to be a Java developer first and a Python developer so those two have been mine that I've used. If you're a JavaScript coder you might want to try the Node.js tutorial. But they're they're all usable on Windows, Mac, or Linux, and they need a Docker installation for these so they'll give you good experience with Docker as well. Ask. So right now I'm a first year student in my university so we have got Python in our syllabus and I was trying a couple days ago to write a Google Apps script so I picked a few things up in JavaScript but aside from them I don't really know anything about JavaScript as well. So I'll check out what the Python app is. And that's a that's a good tutorial. And you have you have chosen the right language for Kara and for me we are both devouted devoted Python bigots, and we love Python so that's great. All right. Kara we generally only go for about 30 minutes. Are there other questions that people had. I'd like us to know that he loves Java. I think Mark loves Java too so you're in good company and actually, yes, many, many of the developers involved with Jenkins Java. Well, and most of Jenkins is Java and therefore most of my production code that I maintain is Java. Absolutely. So, so yes, no, no question that Java is Java is a great choice. Excellent. I just wanted to make sure that you are aware we have a Gitter channel for G so it's in the chat, you can. Yes, I've already joined detection. Awesome. Perfect. So good. And then we also have Slack channels for our community in general both those places are really good areas to ask questions and get informed responses. Can you share the general please. Sure, share which channels are links to this Slack channel. Yeah, so Kara, I'm not aware of an active Slack channel for Jenkins users. I thought we were. Okay, sorry. It's all get her. I am incorrect. Well, no, there, there probably are active Jenkins Slack conversations going on in the, in the Kubernetes Slack channels for instance. I don't actively monitor them so get her and get her and IRC are the two places where I tend to monitor. Okay, yeah. Yeah, that's great as team is so helpful to me he's always helping me with my even dumb doubts also. I just want to say like, I don't know much about Docker. So should I first learn about Docker and Kubernetes before jumping into the swagger and rest API stuff because I found whatever your learning style is is great, but for me I find it easier to have something that motivates my learning. And therefore I started learning Docker because I needed it for Jenkins and I used it by working with Jenkins and Docker. But that was because I cared about Jenkins. And so if there's something that matters to you where, hey, I'd like to learn this. I think you can learn Docker and Jenkins together, almost as readily as you would learn them separately. Okay, then I will look into Docker also. Yeah. Any, any other topics. Okay, I think we're set then car. Are you okay if we close the session and. Yeah, sounds excellent. Great. See you all in just get on and this meeting if you have any more questions. And where we can get this recording link. I'll post it in the Gitter channel. Okay, okay. Yeah, thank you. Bye. All right, thank you. Thank you. Thank you.