 Hi, all. Thanks for joining me. Thanks for joining this video online. Today, we have a special session about Jenkins in Google Summer of Code. We will have an introduction to what the Google Summer of Code is, so what the Jenkins project is doing there, and then we will have presentations by potential mentors. So, potential mentors will present their projects and their project ideas which you can use for submissions. The target audience for these meetups are potential students. So, ones who would be interested to participate in Google Summer of Code, and we target this audience. If you're interested in mentoring, we have office hours and we can follow up after the meetup, but let's reserve all time for the discussion with students today. Oh, am I still online? Yes, I can hear you. Yeah, because I tried changing slide and they just load in screen. Okay, do you see it? We're seeing the same thing. It says loading on our on our view as well. Okay. Yeah, if you participate in Google Summer of Code, get ready to a lot of surprises while doing remote collaboration and such events. Okay, let's do this presentation mode then. If you join Jenkins online meetup first time, it's a community driven virtual event. So, we do presentations and discussions about any topic related to Jenkins, whether it's Jenkins usage, Jenkins administration or Jenkins development. And these meetups are quite relaxed. So, everybody is welcome to join, to participate and we encourage you to ask questions or to comment during the discussion. And we are constantly looking for speakers. So, there is advocacy and outreach special answers group. And if you're interested to present something, then the Jenkins online meetup just let us know and we will help to get it organized. Okay, if you have any questions during this meetup, please use Zoom chat or Jenkins Jason Gitter channel. It's our main Gitter channel we use for all kinds of communications during Google Summer of Code. So, feel free to join and ask them. And after the meetup, you can also use mailing please. We will share links later. And just in case you participate, please keep in mind that we have a code of conduct, but too long to treat, just be kind. That's our approach. Okay, now it works. Okay, today we talk about Google Summer of Code. Okay, I'll jump to PDF next time. So, today we talk about Google Summer of Code and I believe that almost everybody on the call is familiar with this program. We will have a quick introduction. Today's meetup is hosted by Jenkins Orkan main team. So, you can see the names, but you can't see photos. Interesting times. So, yeah, we have like me to prevent. I can also present. Well, I think it's related to Google Slides. And I'm not sure what happens. But yeah, I don't think I have too much content, which requires pictures. Let me just reload it. Okay, here we go. So, yeah, this meetup is hosted by Orkan means this year we have four condiments, Markey, Martin, Kara, who manages Jenkins X project and me. And if you have any questions, our Orkan team, you'll be happy to help you. Today's agenda, as we discussed, is just a quick introduction and project presentations. Maybe presentation about the works, please. Okay. So, if you have never heard about Google Summer of Code, it's the biggest open source mentorship outreach program. It operates across the world. 2016 years, 16th year for GSoc. And there are thousands of students and open source organizations who participate. And the idea that students just get internship in open source organizations. And these organizations provide mentors, provide project ideas and resources. So students work with open source organizations, study how community works, deliver some useful features. It's a win-win for everybody. In Jenkins, we started participating in 2016. It's our first year, sort of fourth year in GSoc. This year, we had around 20 project ideas. And this year, we have Jenkins and Jenkins X participating in the same organization. If you're interested to know more about Jenkins and GSoc, everything is available on our website. So it's Jenkins IO project, GSoc. If you go there, you can find a lot of resources, a lot of information and links to all materials. So, basically, what we present today, you can find everything on our website. And what are our goals for GSoc? We participated for a long time. And we find GSoc really helpful, firstly, for building bridges in the community, for supporting new people and finding contributors. And our main goal is to provide the best possible GSoc experience for students and for mentors. We do not target the quantity of projects. We usually have just less than five of them. Last year, we had seven. This year, maybe we will have five again. But we work closely as a community. We organize regular office hours. We stay in touch with students, with mentors, and we try to organize a lot of events during the GSoc period. If you take a look at our previous years, you can find links to dozens of meetups, blog posts, and other activities we try to find. What project types we usually have. So it's either key initiatives which target our main genesis goals. So, for example, Jenkins evolves towards configuration as code. We're interested to improve our infrastructure. We're interested to improve our documentation, etc. And we are interested to have Google Summer of Code projects which will be contributing towards these goals. Also, we want to invest into domain specific areas. Jenkins is an open source automation server, and it means that you can use it almost everywhere. For example, me and Martin, we came from an electronic design area, and we're interested in electronic design automation projects. We also have a project idea related to machine learning. We have project ideas related to specific technologies like Geet or GitHub integrations. We also have some cross-organization projects. So, this year, Jenkins X participates under the Jenkins umbrella. We also have effective collaboration with Free and Open Source Silicon Foundation. This year, we have a project idea from Open VRT organization, which is also related to Jenkins X. And this is also a kind of projects we want to do. And if you're a student, if you have something in mind, you're welcome to make a proposal. So, we are not limited to the project ideas we have right now. We are happy to consider other project ideas. So, just make it your proposal. If you're in, if you have experience with Jenkins or you have experience with other automation tools, it would be a great opportunity. Okay, before we proceed, any comments from other work admins? The only thing I will add is just thank you all for being here. It is very awesome to see such a large crowd. Yeah. That's for sure. Thank you. Okay. So, as I said, we have a number of project ideas listed here. We will cover some of these project ideas during the presentation. And we will also talk a bit about how to apply because we have some additions to application guidelines, which are designed to help students to establish contacts with our organizations and to be more efficient when they work on the proposals. Okay, since I spent some time on our JSO goals, you can take a look at the previous years. If you go to our website, you can find that there are archives. So, just in the bottom one, there are links for JSOC 2019, 2018 and so forth. And just take a look. There are links to projects, there are links to materials related to this year. So, you can find a lot of information. And there are some highlights for projects we are doing. For example, last year, we created the end use integration for GitLab SCM. We provide multi-range pipelines. We had a lot of improvements related to web UI tooling. And also, there were projects which got continuation this year. For example, plugin manager CLI tool, it was implemented last year. And this year, you have a project idea, which adds additional features for that. And as we said, JSOC is mostly online event, but we have some offline events. To be honest, I'm not sure about this year, but we keep our fingers crossed. And we had the students visiting Jenkins world in the United States and Lisbon. And we had mentors who traveled to JSOC Mentor Summit. And it's a great opportunity for everyone to participate and to become a part of the Jenkins community. If you're interested about specific channels for JSOC, we have a mailing list. So, our main recommendation for the project is to operate through mailing list. If you go there, you can find a lot of different threads related to various topics. And if you're interested, we recommend subscribing to this mailing list. Also, we have GitHub channel, which I presented. We have regular office hours. Today we have an online meetup, but during the same timeframe, every week, we have open office hours, so everyone can join, can ask questions. And we also have project specific channels. So if you go to project ideas, you may discover that some projects actually driven not by a JSOC team, but by special interest groups in Jenkins. For example, if you go to, let's take a look, for example, custom Jenkins distribution service, here you can see that the mailing list and charter they point to another location because it's handled by the platform special interest group, which you have worked on different integrations. And you are welcome to join these resources, you will find a community which is interested, particularly in this project, and they can become your stakeholder during the implementation. Same for Jenkins X, we have three projects related to Jenkins X this year, well, now four. So there are two projects related to Jenkins X core functionality. And here you can see that there is a link going to custom Jenkins X channels, because Jenkins X is a separate project now, but we have a lot of communication and prospering nation. And you can find that the channels there so you can just join them and have a discussion with the Jenkins X community. We have Kara and Marky on the call and they are active contributors to Jenkins X. So they will be also able to answer questions as needed. Okay, and one item which was mentioned this year, this year, we have not only Jenkins participating in Google Summer of Code, but we also have continuous delivery foundation. Jenkins joined continuous delivery foundation last year, same for Jenkins X. But this year, we decided that we keep operating as a separate JSOC organization, mostly because of the timing because CD Foundation joined the JSOC wait, we already had our documentation in place and the students working with us. So this year, there will be two organizations. And if you're interested in applying to Jenkins or Jenkins X, please apply to the Jenkins organization. And for all other projects like Tipton, Screwdriver, please use CD Foundation organization. We have our partners in the boss organization, so we will be able to help with something goes wrong. But we generally condition is to apply to Jenkins. If you want to find more information about Jenkins, we already presented the website. And we also keep track of recordings for previous meetings. Because we have Office Hours, we also had some project specific meetings, and you can find all the recordings on the YouTube channel. So we will share a link to the presentation and you can find a lot of information here. It may be additional for your applications and for your research regarding Jenkins community and specific projects. So just use it as a source of information. And we also have blog where we sometimes post something about the JSoc. So here if you open this hyperlink, there is a JSoc tag on the Jenkins website, and you can find a lot of materials related to Google, some of the Jenkins including success stories, including case studies, blog posts by our students, which can provide you information how we approach the projects and how we collaborate with students during evaluations and during after JSoc as well. So this is the basic information I wanted to provide about Jenkins organization. Sorry if it was a bit chaotic, and everybody's welcome to comment and provide more details. If you want to apply, I forgot to put a link here, but we have us, let's just imagine that we visit our online page. And here you can find information for students. Here, first thing that he is information and application guidelines for students. This guide extends Google Summer of Code student guide and provide some additional information, which might be helpful during the petition. So you can find a lot of information here. You can find 10 steps, but don't be afraid steps actually really easy. And you can just use them as a reference. What we really expect you to use to explore our project ideas we have. So we have quite a number of project ideas here. If you're interested in particular area or in particular technology, just research the topics, join the channel associated with this project ideas. For example, here, there is a mailing list, which related to platform seek and get your channel points to JSOC. I'm not sure why I change it. I will check it. But these channels, you should join and you're welcome to ask about this project and to ask for more details. And if you get comments, we'll be able to organize additional meetings and discussions in the background if time allows. So you can find these materials. Also, we ask you when you make a proposal. So JSOC team has an excellent guide about how to write proposals and what should be there. So if you go to the JSOC website, you can find writing a proposal section here. And this covers the most information. We have some additional tips for Jenkins students. But it's mostly based on the JSOC guide. In addition, we would like to have some insights about contribution, historical open source projects, if it exists. And also, we would like to know about your availability during the JSOC time frame, because we want to make it a good experience for everyone. So if there are exams scheduled or if you have some travel plans, we would like to adjust, we would like to ensure that mentors are available. And if you're over committed, we can also discuss it with you during the application time frame. We do block students who have some commitments from participating in JSOC, not at all. But we still want to ensure that students really have the capacity to work on our projects. And if you apply, if you have full time internship and the university study in parallel, for us, your career and your study is the first priority. And this, I keep it in mind when you apply to JSOC because JSOC is a huge commitment. And we want you to be successful. So sometimes it's better to not apply to JSOC and to postpone it to the next year if you already have too many commitments. Okay. And additional thing, we have a project proposal template. Again, it's template, it's non-binded, you are welcome to use your own project application template, but you can use it. And the main purpose for this template is to actually discuss project ideas with the community early. Because if you just submit your proposal to Google Summer of Code without getting feedback from potential mentors and from Genki's community, most likely there will be some gaps. And our recommendation is to actually submit your proposals for initial review before you apply. That's why we provide the links to mailing please and to other channels, because you can really work with our mentors and to beautify your ideas to get feedback so that your proposal becomes better. And we are happy to help you with that. Okay. That's all from me. Any questions or comments from Orkan means? Before we press it? Nothing for me. So far so good, Oleg. Okay, thank you. Any questions from the chat? I have a question. Sure. Yeah, so, yeah, so is there a number of students that Genki can't speak for Google Summer of Code? Is there a limit? It's, it will be discussed a bit later. If you open JSOC and you can see that there are multiple phases. And there will be a phase where organizations do project planning, discuss slots and request these slots. So right now, now we did request a bit. And we will be doing it later after processing code student applications. Any Google Summer of Code organization is guaranteed to get one slot. Is my video turned off? Okay, sorry. But if usually we request slots for all projects, we can see the feasible and if we believe that the project can be successful, if we are able to find a mentor team, we request a slot for them. And historically, we used to get as many slots as we requested. So, but right now, there is no guarantee for that. It depends on our manufacturers and basically it's Google, which makes this decision, not us. Anything else? I would like to add a little bit of information to what you said, Oleg, if I may. Yeah, sure. So, regarding the number of students we accept it, for us, it's based on our capacity to mentor the students. Historically, we have accepted anywhere between three to seven students. And it changes on it changes every year based on our capacity to mentor. And the other thing is that sometimes we make a request to Google say we want to request we request nine and they only give us, let's say six or seven. So some of it is within our control in terms of our capacity to mentor. And some of it is not within our control because Google may not give us the number of slots that we ask for. They may give us less. That's what I wanted to add. Thank you, Martin. And just to add, we actually have a lot of potential mentors. So keyword is potential, because we will be working with mentors during the project selection phase to make final decisions and to map teams. And if needed, we will be reaching out to other community members to find more mentors. So right now, our mentoring capacity is quite high. Obviously, it will depend on applications. But I believe that we can run many projects in parallel this year. So it mostly depends on what we get in applications. And we encourage all students who are interested to apply earlier, so that we can do initial planning and invite mentors early even before the student application phase ends. Okay, anything else before we press it? Okay. If not, we already discussed our project ideas. One thing which makes sense to mention because we were some students who were confused. In this table, we have three kinds of projects. One is accepted. Accepted means that it's a fully qualified project idea. What it means that it matches standards of the Jenkins community, because we expect all project ideas published to have quick start guidelines so that students can explore very quickly. And we also wanted them to have new befriending issues linked so that students could pick up something. Right now, we don't have so many new befriending issues left across the projects. We are trying to fix that. But still we expect that there are also draft project ideas. And draft project ideas are also fun to apply to. So if you're interested in any project idea in this list, please feel free to apply the ready mentors behind them. But the scope may change during the discussions. For the record, it doesn't mean discussions during the student application. It also means discussions during community bonding, and maybe even during the just coding phase. So what it means that these projects have basically wide open expectations. And as a student here, welcome to come up with proposal which would narrow it down and something which you would like to implement. It also applies to these project ideas. These project ideas are really ideas. We don't have strict guidelines. And in many cases, we deliberately leave a lot of options for students to choose. So for example, if you open, let's say it's done up in the print storage project idea. It's in Google Doc. Here you can see that there are some items which we expect to be included and some items which could be included if a student is interested. So you as a student have full freedom to explore their areas, propose something from additional least, or even something which is not proposed in this project idea at all. It's really up to you as a student because you submit the final application and the final proposal. And we also have discussion category. It's just in the bottom. But this project ideas may or may not happen, depending on available mentors and on the discussion outcomes. So right now we don't have strong guarantee that we will have mentors. And if you're interested in one of these projects, just let us know you will try to help. But my recommendation in the current state because we have only two weeks left, focus on draft and accepted project ideas because they provide a lot of information and we are really ready to integrate them. I have one question. As a student, so what the time lapse when I should start to work on on any project and I as I understand is as soon as possible? Let's define what work means. So Google summer of code is about code. And here you can see that coding officially begins from my agents. So it means that by this time, we don't expect you to produce any production ready code on your code, which would go into your final release. But at the same time, right now, your goal is to work on the proposals. So for example, here, deadline for applications much 31st, and the applications have already opened. Some students have reached out to us three or four months ago. But the idea here is to work on your application. So to create project proposal, which would be evaluate by mentors, which would include explicitly stop deliverables, project plan, which we would consider is feasible. And this is your main priority right now. If coding helps to achieve that, you're welcome to do so. You're doing some contributions and exploring community helps. Please feel free to do so. But right now, the main objective is proposal, you don't expect any production code to be delivered by mid-May. Okay, and the second question. Should I become upset if I see that someone started do that project and start making contributions to that idea that I want to participate in? So Jenkins is about open source community. It may happen that some activities happen in parallel. You can be upset, of course, but there are other ways. For example, you can reach out to this student, you could find ways to submit projects which would be in the same area, but the issue don't conflict with each other. We had such cases and it's totally possible because again, these are project ideas. And you can also submit your own proposal because it's not something like we accept the first project and the most the student who reached out to us earlier. We make our decision based on the proposal quality and on the chances of their project succeed, which consists of multiple factors, not just on the time when a student contacted the community. So having other students exploring project ideas is not a blocker. Okay, good. Got it. Thanks. Okay. So we have 25 minutes left. I suggest we proceed with project presentations. And if we have some time after that, we can answer more questions. And if you have any other questions, please feel free to ask them in a sync mode so that we answer them while mentors do the presentations. Okay, Mark, you are first in the list. Would you like to share your screen or would you like to need to do that? Your screen is great, Oleg, if you really go to the next slide, that's perfect. So the get plug in project ideas are related to first performance improvement based on benchmarks and second repository caching on agents. The concept with the performance improvement based on benchmarks is that we think there are benefits to be gained by applying a systematic benchmarking process to the get plug in. It has two implementations inside of it, one for JGit and one for command line Git. And we think there will be times when one one implementation is faster than the other and should be recommended. And we could benefit users last year's GSOC provided the Java microbenchmark harness. And we think we'd like that this project idea would take the Java microbenchmark harness and use it to apply it to the get plug in. First idea, second was that repository caching on agents is to take the concept that agents can benefit significantly if we could put a copy of the Git repository local to that agent that multiple workspaces could use as a cache. The concept already exists on the master but is not widely used. So this would be a benefit there. Oh, like I think given our short time, I'd like to leave that as my total. Is that okay? Or is there more that I should say? That's perfectly fine. For all projects we organize special sessions. So if you're interested to know more, there is a GitHub channel specifically for Git plugin project idea. You can ask questions there. And just to explain why this is important. If you go to plug in string cell, it's our plug inside, you can see a number of solutions for the Git plugin. It's 250,000. Well, basically 80% or 90% of instances which submit statistics. So for us, Git is really too critical. And it's also critical for Jenkins users. Because here you actually address millions of Jenkins users. And it applies to many other projects. So Jenkins is widely used. And there is a lot of opportunities to contribute to such large scale projects. Thanks. Good explanation. Okay, thank you. Okay, well, let's move on. Jenkins X. Kara, are you online? Hi, just need to send me. So Jenkins X. First of all, we'll just say that Jenkins X is not Jenkins. And I say this because this is my most common question that I can ask. It was however, started as a Jenkins sub project. But it has a completely new code base written in Go from scratch from the roundup. There's zero code from the Jenkins project in Jenkins X. And it's an entirely different architecture. And in fact, it solves different problems in different ways. So we can go to the next slide. So it's a cloud native CI CD platform for Kubernetes. So its use case is much more narrow than for Jenkins. And to go back with it being originally Jenkins sub project, Jenkins X used static Jenkins masters to power its pipelines initially, but that's no longer the case. Now tecton, which is an open source project within the CDF, the continuous delivery foundation, that is now the pipeline engine for Jenkins X. And Jenkins X, to reiterate was designed from the ground up to be a Kubernetes native platform for CI CD, and enables developers to take advantage of the full power of Kubernetes. And what this means in practice is that it has a it's a different developer experience. So it is extensible in the same way that Jenkins is, but it is much more opinionated. And it really gives you an opinionated workflow based on GitOps. So it has certain best practices which are very good for developers to follow. And such as your single source of truth for all your code, including for your infrastructure, everything is in Git. And environment changes are made via pull request, which trigger your pipelines to execute changes. And that enables you to test and collaborate on changes more transparently, because one of the ways in which Jenkins X leverages Kubernetes is that it develops identical environments for your development, your production and your staging environments. And these enable you to promote through these stages stages with parity and making real back simple. And at the very end of your staging environment, when all your CI CD tests pass, we will spin up by default a preview environment, and that enables you to see like a live a live version of your changes. And this enables more transparent feedback among your team. I mean, for yourself as well, but really enables faster feedback from your team, faster code reviews, and enables you as a team to have shorter lived branches, which again, is a very nice best practice. And, and then once you manually promote, our default is that you man and they promote to production, but you can also do that automated if you wish to. And the automation aspect of that is that enables you to start doing progressive delivery, you can do canary deployments, you can do a B testing, these sort of things are are much much like Jenkins X. Yep, so you can roll back and recover from your changes easily if you need to, because of the way in which all changes are in git, and they're audited, you can roll back the changes if you need to, which is a nice fast recovery to that says you a little bit about Jenkins X. If you have any, does anyone have any questions on Jenkins X? And then I'll speak briefly about the project proposals. Maybe it's better to take detailed discussion offline, just because the agenda, but if somebody asks in chat, I will be able to answer in parallel with other discussions. Okay, that sounds very good. So we have two proposals which have gone beyond the draft stage. And that is they both relate to the way in which Jenkins X handles extensibility. So we have currently both apps and add ons. This is a little bit confusing and it's nomenclature. So we would like to consolidate that, but it's also confusing in how the CLI handles them. So it's a little bit of a UI design challenge, although we know the direction which we would like it to go. But it's also very much a coding project in that we would like the commands themselves to be consolidated. And both these extensibility frameworks enable Jenkins X to use all sorts of like best in breed open source tools that are Kubernetes native themselves. So like SEO or Knative or nginx, things like that, just or flagger or things like that. It enables extensibility with nginx. So it's a really nice project to work on. The second one also has to do with Jenkins X extensibility. In that now we want to consolidate on using apps as our nomenclature, but we would also like those apps to be able to use in any to be able to be booted basically in any namespace. So currently, I believe the way in which the apps work, they only work in one namespace. But the idea is we would like them to be more flexible. And we would like them to be able to work with our new and the way in which to Jenkins X pipelines are booted themselves is JX boot. This is a new way of doing it. So it's a pipeline to boot the pipeline. And what we would like is for the apps themselves to integrate well with that initial boot process. So this is as I guess scrolling through this tells you a little bit more about that project. And if you have any questions, please do ask them on our Jenkins X Slack channels. So I put a link in the slides that you all have, which and it's also on these project pages, but that tells you how to join our slacks. We're part of the community slack, but the Jenkins X Dev and the Jenkins X user, you can jump on there and ask any questions you have. They're very active Slack channels and people are quick to answer. Thank you. Okay, what's next in our list? Oh, actually, it's me. Okay, I'll just do want to be in the pitch. So Mark has talked about Java related projects. And the most of the Jenkins ecosystem is built around Java, Groovy, and basically Java virtual machine or web UI, we adopt JavaScript. But if you want to try other technologies, we also have opportunities. For example, Windows Services, it's a project which is based on dotnet ecosystem. So here, if you go to skills, basically, we have a project which is written on C sharp, which is powered by dotnet. And right now we use both recent dotnet framework versions and dotnet core. And obviously, it targets Windows. So if you're interested in Windows ecosystem, it might be an interesting project for you. Why it's important, we still have a big number of users running cankines integration with Windows. And it's important for ones who want to deliver software or hardware, whatever, which would include Windows components, or which requires specific development tools available on Windows. And Windows Service wrapper is used for running Jenkins agents as services or Jenkins master itself as a service. It's a standalone project. It starts as a part of Jenkins. Now, it's hosted on a separate organization. We are planning to move with two dotnet foundation. Sooner or later, there are some groundwork for that. It's quite popular, not only for Jenkins actually, it's been used in numerous projects outside. And you can see that there's 900,000 downloads since GitHub releases was introduced three years ago. So it gets adopted quite well. It has some historical issues, because it was created a long ago. And current configuration format is complicated because it uses XML. YAML is quite popular now, especially if you talk about Kubernetes access system like Jenkins X, YAML is everywhere. And you would be interested to also have support of YAML and maybe support of verification of configurations. So this is what the project is about. But basically, you can come up with other proposals. You can see that there are 150 issues, some of them related to specific technologies, for example, for dotnet core. So if you want to study something, it's also an opportunity. So you can check out this project, try it out and submit your application. And then you can integrate it into Jenkins because we use components which use this Windows Service wrapper. So any feature which is delivered there will help a Jenkins user to sell out. So that's why we hold this project under the Jenkins umbrella and you're welcome to participate in that. Just let us know. Okay. Can you just open the slides, please? Okay. The next 24. Okay, this one. Yeah, okay. My project is about the GitHub checks integration in Jenkins. So in order to understand what you're required to do here is currently all pull requests for Jenkins plug-ins and for Jenkins core are automatically built within Jenkins. And the current state is that Jenkins reports the success of the bills in each pull request with a simple status line as you see here in the image. So current for instance, this is a pull request of one of my plug-ins and you see a GitHub actions. Everything is working fine. And in Jenkins, some problem has been occurred. And now in order to see what actually is the problem, you need to open Jenkins and navigate to the details. For instance, look if a test has been failed or if a warning has occurred. And that's a little bit cumbersome. So the idea would be we don't want to see the results in Jenkins. Yes, thanks. We want to see the results directly in GitHub. And I have shown you an example how this could look. This is from another tool it's called coder C coder C is reviewing a pull request with check style and find bugs in server application. And after the review is ready, they report the results back to GitHub. So you directly see that here, I have used the number five, which is not good, and it should be replaced. So the idea is that we have in Jenkins the possibility to provide an API for plug-ins. So that if Jenkins reports a test failure or a warning or something else, one can call this API and then it will automatically generate a link in GitHub. Yeah, that's the idea behind it. And maybe you can switch to the next slide. We have a project documentation on the web. And I just put the milestones here on this slide. So the idea is so one step is you need to know what is the GitHub API, a GitHub checks API, what is what do you what can you do with it? What kind of API possibilities do you have? Then an idea would be to provide that API in a general way in Jenkins. And then it would be good to have one example so we can for instant create warnings from Jenkins in GitHub. So this is so the basic idea of our GitHub checks integration within Jenkins. There are more details on the web page. I think it makes sense that you read this small project proposal. And maybe we can chat afterwards about some details about this project. Yeah, I thought we have a meeting on Friday. Yes, of course. So if you're interested, we organize some meetings specifically to discuss projects, you can find them in Jenkins event calendar. Yeah, and here, for example, it's in Mitre zone. Here, you can discover that there are some meetings planned. So for example, we have a fingerprint storage discussion tomorrow. And we have for checks API discussion on Friday. And I guess, we will have a discussion for pipeline as YAML project, which we are yet to discuss at pipeline altering C. So feel free to join us. And we are happy to organize additional sessions if you need clarification about the project ideas. Okay, thanks. That's for me, everything. Thank you. Okay. Oh, Marcus, sorry, I missed you in the list. It's quite all right. It's quite all right. I'd like Rick to be able to go ahead and go first. I don't have a slide prepared. I was just going to give a brief overview. But I'd like Rick to be able to go first. Okay. I didn't have a slide that also I can share my screen. Okay, if you want to do so, just do it. So I believe you can see my screen. Yes, we can. Okay. I may know if a user just downloaded Jenkins, the Jenkins cannot do anything if they don't install any plugins. So people usually will install a lot of plugins that configure them. For a new user, it might be a little bit difficult for a user who is very familiar with Jenkins. It's very boring. So this program will improve this experience. Like if we have a website or for the customer.tickets.l, then people can just choose the Jenkins code, choose the plugins. Maybe we can also provide the configuration that could use a password or after central or RSS. Second, people use Jenkins for some specific areas like some user just use Jenkins in the Kubernetes or other user cases. So I believe we can build up some different, I mean, user cases. So we can have like I called it formula. I have another project to do some research like I called it formula. It's formula is out of the box, like a one formula. It contains configuration as code under some Chinese localization. So this project can build the top image automatically. Then another formula might be a configure that code plus pipeline plus Kubernetes, then people can use this top image. They don't need to install all these plugins and they also can get an initial configuration of the Jenkins. So I believe people can benefit from this maybe a lot. So this project is practically to have a backend in front of project. Thanks to the custom world, a package of Jenkins, this project did a lot of work for us. So I believe this might sort out both this proposal. You can get some information from the other projects like a springboard documentation. And you believe from friendly users. And also you can check out my project project to get some ideas. I think that's all I want to explanation. Thank you. Thank you too for the presentation. And the next project idea we have in the list is one by Markey about machine learning. You may go over time maybe five to ten minutes. But yeah, I think that you have enough time. Okay, cool. Well, thank you everybody. I am one of the potential mentors for the machine learning project. There is also another mentor on the call, Jonas. And essentially what we're going to what we're proposing is everybody is aware that there is the Jupyter notebooks and they basically are Python and they're interactive computational notebooks like Jupyter and Zeppelin. And what we are proposing is to build a Jenkins plugin that allows the integration of existing polygot notebook kernels to support notebooks like computation such as Jenkins. So essentially building a data pipeline or a machine learning pipeline and using this plugin to allow to extend to these notebooks. It really will basically unlock a lot of the back end type of kernel computational stuff that is being utilized. That is in a nutshell there's a lot more to go into. We do have a Gitter channel and we do a lot of talking in there. We are doing the current student proposals right now. This project requires you have a knowledge of Python because you'll be extending the Jupyter notebooks via Python in a plugin. I know that was a little bit, I was a little unprepared to do this so I apologize for seeming like I have absolutely no idea what I'm talking about. Is there anybody that has any questions? I think there is, but maybe not. Maybe not. If you have any questions don't hesitate to ask in Zoom chat or gain our Gitter chat or for this purpose maybe JSOC machine learning project. I do think we have a question in chat. Rahim do you have a question? If you do you are on mute. Yeah you can sit chat right now. Rahim I'm going to unmute you. Actually I can. I don't see you have a microphone connected. If you'd like Rahim you could reach out to us in the machine learning channel and I'll be happy. If you don't feel comfortable asking in there please do feel free to reach out to me directly or one of the other potential mentors which is Bruno. You know Ness we're happy to help in any way. Let's see I'm the question is I'm fluent in R and not in Python. Am I welcome? Yes you are. JSOC is an opportunity to study so you don't have to be an expert in technology in the district here. It's a skills to study improve. So somebody which is of course required to get you started but you can get deeper knowledge during JSOC and it's one of the main purposes of its learning. We will be hosting an office hours for the machine learning project in the coming days. Look forward look for look for that sorry look for that in I'll actually make a note in our Gitter channel and then we will tweet it out. I will like to add one other thing this coming Saturday. I will be I will be part of a panel that will be discussing how to write student proposals. I will put a link to that notification in the in the zoom chat if you have it if you'd like to join that. That's all for me thank you. Thank you so we could spend maybe a few extra minutes so next in our agenda is Jenkins pipeline is YAML. Hello thank you for the time so I would like to say a few things about this project Jenkins pipeline is YAML. So for the ones who are not so familiar with Jenkins pipelines it's a special domain specific language where we can store our pipelines in our favorite version control systems and Jenkins has the ability to run the pipelines from these files specifically written in a specific domain specific language. So the idea of the project is to create a plugin where we can define our Jenkins pipelines as YAML definitions or as YAML is very popular right now and also well known. So the idea is the plugin to be able to provide a solution for defining our pipelines as YAML. So this is the very overview if you guys have any questions or things you can always ask. Thank you for the time. Thank you for the quick introduction and just for some information. Jenkins is a part of continuous delivery foundation. We also work with Jenkins X in these other projects so one thing you could consider is for example doing syntax which will be close to Jenkins X pipeline or for example doing support of other syntaxes like tecton as one of potential opportunities or maybe just creating a fully original format depending on what is your view for that and you are welcome to make all kinds of such proposals. We will review them and we will be happy to provide feedback. I guess Ayutun has recent project started which is pipeline as YAML so you can also check it out for some insights and examples how it could be implemented. So if you consider this project please be sure to study it and try it out. Thank you. So I guess that's all from our list. Just in case are there any mentors who want to say a few words about their projects or should we close down or so question to students are there any questions? I have one question. I'm currently working on the checks API project and I wrote a demo for it and just I just found some flaws in my design and I have listed them on my proposal. I just want to know whether it is okay to include those flaws in my proposal and submit my or should I just delete those that did the same by submitting my proposal? I would say to leave them in. I would leave them in personally. I've appreciated personally discovering mistakes when a google summer of code exploring student has disclosed oh look here's this problem I found in the Git client plugin or the Git plugin it's very valuable so much appreciated and commendable. Again all my objective is to find project ideas and project proposals which have the highest chance of success and if you do any research a negative result is a result and please put it in your proposal so we can see that you did some exploration in this area and it can be a basis for us when we do project planning during community bonding and next phases and yeah it's really important for us. Okay anything else for today? I guess not. So again if you have any questions git or channel it's quite active and the same goes to mainly please so just use any of these channels whatever you prefer to ask questions maybe we have something in the list not yet but yeah just ask and have a great google summer of code again thanks a lot for your interest we know that google summer of code is a big commitment by students and if you participate in the Jenkins project we hope to make it a great experience for everyone so looking forward to get your proposals and to work with you during the next phases so let's stop the recording then. Good luck everybody. Yeah good luck. We will publish this video within several hours. Thank you all. Okay thank you bye bye.