 Hello, welcome to the Jenkins Online Meetup. Today we have a discussion about the DevOps World Community Agenda and call for playbooks. So, DevOps World is one of the biggest events related to DevOps. It's a conference which this year happens online and free to attend for everyone. There is a strong community agenda there. The Jenkins project has been a part of this conference since the very beginning. Hence, we do this presentation today so that we can discuss all the matters. Let's continue. Again, it will be quite a relaxed presentation. If you have any questions, please feel free to ask. First of all, I would like to welcome our new Meetup host, Rick. A few weeks ago, we made a call in the community that we are looking for more contributors who want to help us with online events. It's really important because community is not just about submitting code. Jenkins community needs all kinds of contributions, including helping with organizing events, spreading the word. We have multiple contributors who followed up. Today we first meet up with new participants. Rick, would you like to quickly introduce yourself? Okay. Hello, I'm Rick. I'm from China. I love Jenkins very much, not because the open source projector, because the most important Jenkins community is very friendly for everyone who is interested in open source. When I tried to promote Jenkins in China, actually, the history of Jenkins is larger than my personal work experience. A lot of people, Chinese people are using Jenkins, but I did something to promote it. English is our second language. I translate a lot of documents and do some localization in China to make it much easier for Chinese users. As we know, social media is also very important, so we have a WeChat group, WeChat account. It's very similar with Twitter. We have a lot of followers, like 15,000 followers of Jenkins, WeChat account. The second thing I want to mention is Jenkins there. I wrote it in Golan, because it will be much easier for users who want to install it. As we know, Java always needs a JVM, so it might be not very handy sometimes. The third thing I want to do is KubeSphere. KubeSphere is an open source projector. Jenkins is the core engine of the Delfts module. I think my colleague can have much more introduction about KubeSphere in case someone might be interested in this. Mr. Pan, do you want to introduce KubeSphere for us? Maybe a few minutes. Can you submit up? Maybe just a brief introduction of what is KubeSphere. Let me briefly introduce what is KubeSphere. KubeSphere is a distributed operating system managing cloud native applications with Kubernetes as its kernel, and KubeSphere has developed a CSE platform based on Jenkins. KubeSphere provides a plug and play architecture for a third-party application, similar to integration into its ecosystem. You can position KubeSphere as an open source container platform to deploy and manage your cloud native applications, you know, Helm charts, or Docker containers, or any kind of cloud native applications. I will have a presentation in this month or next month to introduce how to use Jenkins in KubeSphere, basically something like how to use Jenkins in Kubernetes. Okay, that's all good. Thank you. Yeah, so if you want to discuss more stay until the end of the meet-up, we can discuss more KubeSphere. Mandre, would you like to introduce yourself? Yeah, definitely. My name is Dimathri and I'm from India. I love open source a lot. I started my career learning from the open source, contributing to the open source a lot. And recently, the main background of mine is in the development field as well. Recently joined Jenkins, and it's a very interesting open group of open source contributors, talented people. And I would love to contribute whatever way I can as much as I can. So that's it from my side. Yeah, thank you. And we also have two DevOpsVolta program committee members today. So Victor and me. Victor, would you like to introduce yourself? Hi everyone. So I'm Victor Martinez. So I've been probably, as you already know me, in a few places. I've been a contributor for Jenkins for a long period of time. I'm happy this year to be in the program committee for review of the call for paper. So happy to do my best there. Yeah, that's pretty much me. So I'll follow Victor for more information about Sikeslink. Okay, and yeah, I'm Jenkins, board member. I'm also acting events officer. So this role in the project was responsible for organizing various events and cardinic thing them. Yeah, I'm quite active Jenkins contributor at the moment. So let's continue to the main part. We spent quite a long time today on the introductions, but yeah, my plan is to actually do a really quick introduction to what is DevOpsVolta and then we will discuss how call for papers work. And then we will just have a Q&A here where we will be able to answer any kinds of questions related to DevOpsVolta agenda, community booth, or whatever, whatever. Okay, if you have any questions during the presentation, please use Zoom Q&A. Everyone has a button for that. And also after the meet up, after the main part, we will stop the recording. And everyone will be able to ask any kinds of questions of the record, we will grant voice permissions. And if you want to stay to talk, for example, about CFP to discuss your particular ideas, or just to talk about what cubes here, we can stay after the meet up for additional 30 minutes and discuss all of that. For all final questions, we have a channel started in the CDF workspace called DevOpsVolta call for papers. So if you want to, you can use this chart to ask questions about the applications. And you can join this Slack workspace by following the guidelines here. So maybe somebody from the audience could share a link to this presentation so that you can just open that and follow all the links. And yeah, thanks to the Continuous Liberty Foundation and CalVis for sponsoring the meet up platform and for sponsoring meet ups because without them, it would be quite different, difficult to organize a little bit. Okay, let's start from the conference. Okay, so yeah, let's continue. So yeah, what is DevOpsVolta? Actually, this conference had started in 2011. It started as Jenkins user conference. It was firstly a small event where there were around 100 participants and then the conference room. And for example, last year, we had 25,000 registrations and more than 3000 participants on the conference. It's an online event. And the most recent offline event in San Francisco was also about 3000 participants. So you may have heard about this event as Jenkins World also. But it evolved and now it focuses on all the areas related to DevOps as a culture, as tooling ecosystem. It also covers topics like leadership. It invites a lot of practitioners to take their stories. And there is also community representation. So all open source projects are welcome DevOpsVolta whether they're a member of the Continuous Liberty Foundation or not. So yeah, this is a quite big community event. What we still have quite strong Jenkins representation there. And Jenkins is still considered as a major community event. And let's talk why. So firstly, Jenkins is represented at Keynotes. We use this event to do major announcements when feasible. We also do that to talk about the direction for the project and the initiatives happening there. So here, for example, you can see KK founder of Jenkins talking about 15 years of Jenkins. We celebrated this three years ago. So yeah, and we use conferences for that. Also, yeah, there is a lot of Jenkins talks. So Jenkins agenda is about 20 to 30% of DevOpsVolta agenda at the moment. So it's about dozens of talks. There are many key contributors presenting. For example, here you can see Mark Wade, he's the author of the Git plugin, leader of the platform CIC. And he's Lim Neumann, who is one of the major contributors to the Jenkins pipeline ecosystem. And from what I can see, Lim is doing whatever presentation about Jenkins pipeline. And yeah, again, you can meet any contributors. And we actually welcome all kinds of talks, including hardcore talks by developers, like for example, I did a presentation about the remote internals, its communication layer in Jenkins. Also newcomer talks are welcome, so that if you want to present a particular feature or show your story about how you use Jenkins, you can also participate in this event. Then it's not about talks, we also have a community booth. And this community booth is actually a center where we have a community gathering and hanging out. So if you have ever participated in an event like FOSDEM or scale, community booth is basically our representation of community at DevOpsVolta. There are always contributors hanging out there from different companies, from different projects. And we also use them to organize various live demos. So for example, here you can see Abhudeh Sharma, he's one of GSOC 2019 students. He was working on no-strategy performance improvements. And yeah, he or as many other students visited DevOpsVolta to present. And he's also a GSOC team, but at another conference in the United States, this one in Lisbon. And yeah, we also organize Ask the Experts booth, so any Jenkins user can come and ask questions from expert contributors and get the answers. So we usually have a really high traffic in the community booth. And yeah, it's not just about stickers. At online events, we also have a booth. Another thing we have at DevOpsVolta and the JenkinsVolta tradition is contributor summit. So what it means, it's a full day event where we talk about Jenkins as contributors, advanced user cells invited to participate, especially if they're interested in contributing to the project. But the main goal is to talk about Jenkins future and key initiatives. So basically, it's organized as a conference with several tracks. For example, there we talked about things like joining continuous liver foundation, pluggable storage for Jenkins. Or when Jenkins X started again, we had a huge brainstorming about how we would like to see Jenkins as a cloud native application. So it was one of initial discussions for Jenkins X. And again, it's a conference. So the agenda depends on what actually happens. Also, in another photo from contributor summit, so now we are not just celebrating, we actually have a lot of talks. We also used to run community awards at DevOpsVolta. So here you can see a real course, currently Jenkins governance board member and major contributor to the configuration as code plugin. So currently community awards will be happening at the CDCon. So it's another conference scheduled for June 25. And the Alliance for Nominations is actually this week, Friday. So if you want to nominate someone, there is still opportunity. And yeah, but there will be no community awards at DevOpsVolta this year, at least in the current plan. We also have a lot of community bonnets events, including going to the bar after the event, hanging somewhere in the hotel. Well, when the event person is in person or just staying at various happy hours, etc., the event is remote. And yeah, when we had 15 years of Jenkins, we also had multiple kicks at conferences, again in the community booths. It was a fun time. And last but not least, we also organized hackathons during the conference. So it's, let's say, limited events. We invite something like 20 to 30 contributors from different areas to work together and to just hug particular projects. For example, we worked on Java 11 support. We also worked on new security scanning engines. We have created significant parts of a new one, CNG plugin together with other contributors during this hackathon. So yeah, again, it's a community event which you can join. And now since it's online, I'm not sure whether we will be organizing that to be seen. Okay, so this is a community agenda. And again, it's not just about talks. There are many other things to do. Do we have any questions so far? No, no questions. Okay, so if you have any questions, please do not hesitate to use Kone. And yeah, now we will go to real content. And the real content is actually about call for papers. And yeah, there will be less photos in this part. So yeah, first of all, yeah, this year the conference will happen in September from 28th to 30th. There might be also satellite events before and after the conference. It's yet to be decided. This conference will be absolutely free to participate, except particular workshops. But yeah, the main conference including call trucks, community truck, et cetera, it's available. The registration is yet to be published. But yeah, it will be available. And the conference is fully virtual. So it will happen remotely. Again, time zones, et cetera, to be different, determine how it will happen. The landing site for the event is here, DevOps world. So yeah, basically you can explore all the information here and you can sign up for notifications when the registration opens. Which is something good thing to do for me. Okay, so what else? Yeah, the current plan, again, it's yet to be announced. We will have two days of conference with main tracks, and there are multiple tracks to be available. So the first list community track, it's fully focused on open source projects and on open source communities, including how to build to the DevOps community or just presented particular areas. There will be a practitioner track, which is focused on basically user stories. And again, Jenkins has historically represented that quite well. There will be the continuous Liberty Foundation track. Basically, it's another site of community track where the continuous Liberty Foundation focuses on its member projects, special interest groups, and also all open source projects invited. Historically, there are also some representation of CDF member companies. And yeah, but still, this is quite a good agenda. On day zero, there will be workshops. Maybe there will be something else. Yeah, all of that is to be decided. And for contributor summit, we tend to discuss doing it after the event on October 1st. So if you won't collide with the main agenda, but you want to do it this time after the event, because in this case, we will be able to mean discuss recent development, presentation, ideas we got during the conference. And it seems to be a better format than we used to do before, because before we historically were doing it in parallel with workshops. And yeah, the plan is a bit different. Again, it's all to be announced. Okay, what else do we have confirmed? So we will have two community workshops on September 28th. One workshop will be related to contributing to Jenkins and onboarding. Another one will be likely related to something about Jenkins pipeline. The community track, other tracks, keynote is to be decided. But yeah, likely they will be keynote by the continuous Liberty Foundation, and there will be Jenkins representation there. So if you have any major announcements to make, we will use this opportunity. And also, yeah, expert hall, it will likely happen. And contributor summit, it will likely happen. So it's going to be decided. And for CDCon, again, June 25th, another conference. And again, everyone is welcome. The registration is already open. Okay. So for community track, there is some information from Alisa. But basically, what I discussed, we talk about open source projects, various tooling methodologies, again, stories from end users. If they get submitted to this track or to practice the engineer's track, as a program committee will be balancing them. Because yeah, these tracks are always fictional in the moment. We will also talk about use cases. This year, there will be significant focus on security and compliance, because many CDF project members actually prioritize security this year, including Jenkins. So likely there will be more representation for security topics in software delivery than usual. Okay. If you can see the speaking about Jenkins, what you can present actually anything related to Jenkins. So it might be about various integrations about your success stories. If your Jenkins contributor, you can talk about new features, show some live demos, you can also show your experience, for example, about developer pipeline libraries, how you deliver to this pipeline libraries, how you deliver your projects with Jenkins. And if you want to share your insights about how the project involves what you would like to see, all of that can be submitted. So yeah, the expectation, especially for the community track, if you talk about Jenkins, then yeah, then it should be about Jenkins. So pure marketing talks are not exactly welcome at the conference. Though for technical talks, again, you can do whatever you want. And yeah, it's not about Jenkins. So if you work on other projects like CoupSphere, Tecton, Jenkins, Spinnaker, etc., you are also welcome to submit your applications. And really, as a program committee, we'll be balancing the agenda so that there will be a presentation for white technology area. Victor, Rik, would you like to add something? As well as experienced DevOps world participants and the program committee members? Sure. For me, I doubt that you have been in the two huts, given a talk and also doing the review of the talks. So I just encourage people to get out of the comfort zone and talk about what they do and how they use. It's always interesting to see other people's way of working with Jenkins and what other things they've been building. Because the way they can teach us what are the troubleshoots or the problem they try to solve with Jenkins or what are the experience they got using it, it will help others to understand how they can use that as well. So I really encourage people to use that. From the review point of view, there's always a trick like you might be interesting to talk about something, but it's also interesting like you might provide different perspectives for the same talk. So I also encourage you to don't just submit one call for paper, you can submit two or three, talking about similar but with some minor differences, because that's the way you might have more chances to be accepted from the point of view of the talk. That's for me the true hint. Would you like to add something? I didn't have something. I'm not sure if you have you participated in the DevOps world before? No. Okay, so looking forward to meet you in September. Okay, yeah, so just to show you a few tips and again I messed up animation on this slide. So yeah, there are some events happening in Jenkins and there are various technologies, so for example, pipeline as code, configuration as code, there are new plugins and integrations happening here and there. There is more than part of the packaging being introduced, for example, Jenkins for Docker, for Kubernetes, there are various operator projects. Also, there is execution for cloud like AWS, Google Cloud, Asia, and again, if you present a DevOps world, if you want to share something, the main objective is to actually communicate information to users and to provide something they could adopt and could follow up on. So if you talk about Jenkins, how it could be used in modern way, how this use of existing recent technologies is definitely something interesting for a big audience. You can also take various specific topics, but again, narrow topics is harder to get audience for that. But at the same time, you can get less participants, but more interested in particular topic. So yeah, there are many areas of welcome. And if you're interested, there is Jenkins roadmap published here. This roadmap actually needs some updates. There are discussions in the developer mailing list, but you can see that there are multiple areas here, including current preview features, ongoing projects, and recently released events. So it could be one of sources of ideas for you if you want to explore something and present a DevOps world. So it's just a hint. Again, you're not limited to what's listed here, not in any means. One particular area I would like to highlight is interoperability with other projects because it includes two integrations, it also includes integration with other projects. For example, a few days ago, we had an announcement for Tecton client plugin for Jenkins 1.0 release. You can also see examples here, for example, how to reuse Tecton and Jenkins X from Jenkins. So such interoperability topics become more and more popular in these years. So if you want to talk about how you integrate Jenkins with other tools in the software delivery pipeline, then it could be a good opportunity. And another good opportunity is, of course, everything security related, because again, there are two parts. Firstly, how you create secure Jenkins if you're a contributor, how you deliver components, and if you're a user, how you secure your own products with Jenkins. So how you secure your delivery pipelines, how you verify your products, etc. And all these talks could be very interesting to the audience. So you can take a look at it. Any comments before we move on? We'll click through this information as well. Okay, call for papers. Some key dates. So the call for papers closes in a bit more than two weeks on May 20. So we highly encourage everyone to submit the applications by this date. And yeah, a few tips. So firstly, when you make an application, just be concise, stay with key points because when reviewers review the applications, last year we got almost 500 proposals to the community track if I recall correctly. So basically, it's competitive application and the program committee and reviewers have limited time to process them. So they start from basically looking at your elevator pitch and the abstract, they do initial filtering, then they start deep diving. But if you want to be selected, it's important to represent the idea of the talk and to show what would be the takeaways for the main audience in your abstract. And it's important to think. So if you create a better abstract, it's quite probable that nobody will go, for example, to the GitHub link you attached to deeply investigate your project and try it out and say that it's cool. We would be happy to do that, but we have a very limited time to process the applications and also you focus on users and on your target audience. So whatever is your target audience, it may be anything is user, it may be just a particular set of users and contributors. But when you work on proposal, just think about what is your target audience and create basically talk for them. So you do not have to, for example, if you talk about Canadian delivery with Kubernetes, you can just have a Kubernetes and focus on what are the details you don't want, you don't need to provide introduction about what is Kubernetes. Yeah, there are other talks, there might be references for that unless you want to do exactly the introductory talk, which can be also an option. So just think about that, complexity is fine. And we can, as a program committee, we are responsible to somehow balance these talks. It's always an interesting challenge, but we will do our best to do that. So there are also news about speaker training. So this year, called this will be offering training sessions for speakers. This is the first year when it happens, the details are to be announced. But yeah, the fact that it will happen. So if you want to participate in such trainings as a speaker, you will be eligible to. And yeah, one thing, yeah, I mentioned the program committee multiple times. So currently the program committee is still being finalized. We have several contributors who have already agreed to be a part. So Victor and me, also we have Alexio, Victor Farsiq, Alyssa, Carlos Sanchez, likely there will be more contributors who join before the end of the call for papers. So this is the committee of contributors who will be reviewing the proposals for the community tracks. For other tracks, there will be rather other reviewer teams. But the community tracks, we specifically focus on the tracks, the applications being reviewed by the community. And yeah, thanks for inviting contributors to participate. Any questions so far? There is a question from Vikas. So he is asking that to work on Jenkins add-ons development, do we need our own setup or some cloud setup can be given from two? I suggest they discuss and quit after the presentation because it's not strictly related to the subject of the event. But I'm happy to answer this question and share the links. But yeah, thanks for the question. So we will definitely answer that. Okay, so if you have any questions, so we had one session last week, we have a session today. You can see that this slide hasn't been updated, sorry about that. And as I mentioned in the beginning, there is a Slack channel on the CDF workspace, which you can use to join and ask any questions. So you just navigate to this page. It's on Jenkins Community website. And here you can follow the link how to join the CDF Slack, how to automatically request the invite and join this channel. And once you join, you can ask any questions in the chat. We have another question from Mike. How to get speaker training? So there will be communications after you get a notification of acceptance. So right now, I don't know what will be the details. So I know that CloudBees is arranging that. But the details will be communicated in June or July. So if you want to practice presenting, what I can offer, we have Jenkins Online Meetup. And there, for example, if you want to present this Meetup, you can go to this page and there is speaking section. So you can follow this guide if you want to apply to Jenkins Online Meetup and present again anything about Jenkins. And for speakers, what we also offer, we provide the reviews of the application of abstract, of slide decks when they want. We also do rehearsals before the Meetup. I mean, if the speakers are interested too. So if you want to practice it a bit, you can join us for Jenkins Online Meetup and we will be happy to help. So it's a good opportunity. Be sure that it's something you can use as a practice. So is that possible to talk the same topic between the online Meetup and the DevOps world? That's a good question. So I cannot say yes or no because it really depends on the agenda. At the same time, if there is already a public recording of the talk in the Jenkins Coming Meetup, then let's say it will be less interesting than having a new talk because having a new talk is giving an opportunity to somebody else to present their story and to make this story visible. So we commonly... So sometimes there are talks being repeated, but again, since everything is online these days, there is no particular point in repeating the same talk again in the same form. So you can submit the same talk. It might be accepted, but yes, Program Committee, I think that we will be focusing on giving capacity to more speakers and presenters. I guess online Meetup is just a good place to practice. Yeah, that's right. So it's not the best place to practice the same talk. That's for sure. But for example, if you want to practice the talk, every one of us works for a company and for example, you could do an internal Meetup and present the same talk. It could be a good opportunity to get some feedback. Also, there are other Meetup groups, etc. Yeah, you can apply there. Well, actually, a good practice is to let organizers of a conference know when you submit to multiple conferences so that they again can balance the agenda. But in particular cases, it's possible to do presentations especially in countries where offline Meetups are allowed at the moment. You can also consider doing offline Meetups. In the Jenkins community, we do encourage offline Meetups at the moment. But yeah, other communities are doing them. Okay. Any more questions about that? Okay, some takeaways before if you have any questions, just drop them in the chat or in the Q&A. We will still answer them. So key takeaways. Firstly, the DevOps world, we have a really strong community agenda. This agenda isn't really related to Jenkins, but Jenkins is still heavily represented there. And we invite talks about Jenkins integrations with other tools, various community use cases, developer risk cases, and basically it can be a practitioner discussion or it can be discussion about, let's say, digital transformation in your company. So yeah, various of topics is quite wide. DevOps world, I'm not sure how many tracks there will be finding this here, maybe something like eight or so. So this is a good opportunity. Okay. Then, yeah, if you want to apply, you don't have to be a Jenkins expert. There is a lot of opportunities for practitioner talks, for newcomer talks, et cetera. And you can do that. Also, we will try to give some opportunity for presenting at the Jenkins contributor summit. And even if your talk doesn't get accepted, for example, you can do this talk at the Jenkins online meetup. So again, if you are interested in presenting in the Jenkins community, there are many ways to present, not just the DevOps world. And we can work on that. So we encourage you to submit the applications. The deadline is May 20th. So there is a bit more than one week left. I'm not sure whether the deadline will be moved this year. I recommend to not expect that and to submit earlier. Thanks for your time. And again, we welcome all the applications and we would be happy to review them. If you have any questions, we have this CDF Slack channel. The entire program committee is there. And we also have limited availability, but we will do our best to answer any questions you have in this Slack room. So any other questions? I have a few references, actually. So in the last slide, you can see DevOps world, advocacy analysis. It's actually another group which helps to organize events. It says if you want to present outside of DevOps world, then there is Slack channel for any kinds of pony. And yeah, there are also recordings of previous sessions. You can find them on YouTube. And for 2020, there is this site. So yeah, if you are looking for some inspiration, for experience about how to present and what to present, go to this event. 2020 was also a virtual event. So the experience of the format is quite close to what we will be doing for 2021. And you can see that there is a lot of Jenkins topics there. Again, of course, complexity, of course, angle. So take a look and you can find something interesting. And I believe that weeks are presented last autumn, right? Yeah, the search here is not exactly the best thing. But yeah, you can find Victor's talk. You can also find my talk, but yeah, please don't watch that. But Victor's talk was really good. Okay. So do we have any other questions? One question is about a Meetup host. And we ask if you want to host Meetup in terms of what roadmap you can pull? Okay. So yeah, just to provide you some more tips, how we organize that. So in the Jenkins project, there is a sub-project related to Meetups called CACD and Jenkins-Siri Meetups. So we originally started a series of Jenkins-Siri Meetups around the world. We had around 80 active Meetups at once at some point. Then there are also CACD Meetups, which are basically Meetups under the umbrella of the Continuous Delivery Foundation. So currently Jenkins Meetups are welcome to rename to CACD Meetups. And other CACD Meetups are welcome to join. And yeah, we together with the Continuous Delivery Foundation have a platform which is based on Meetup.com. So many of you registered using Meetup.com link. And yeah, you can also get the list of Meetups by just following to our Pro account. So it's Meetup.com, Pro, CACD, CDF. And there you can see currently active Meetups, or at least currently registered Meetups, because here with coronavirus, the most of these Meetups are not actually active at the moment. So here, for example, let's go to Toronto. I'm not sure whether we have registered Meetup at the moment. And we have a Meetup, which is called Toronto Jenkins-Siri Meetup. So I'm just following the question. It's an example. I don't know exactly what's the state. So last Meetup, I mean, real Meetup was organized before the coronavirus. There is a good assumption that this Meetup is rather unhauled at the moment. So there are multiple ways. Firstly, you can see the list of organizers here. And the list of organizers, let's see who is here. So Continuous Delivery Foundation, then Scholar and Maxwell, the managers of the Jenkins Meetups program when it was managed by CloudBees. And there are also local organizers, so Kevin and Greg. I don't know them personally, but this could be your points of contact. So first of the things, if you want to organize a Meetup, again, it can be Toronto online Meetup, or whatever. We don't encourage face-to-face Meetups at the moment. But anyway, you can reach the organizers and say that, hey, I would like to speak about Jenkins. I would like to organize Meetup and let's do something. Then if they're available, if they're interested, you can just collaborate on organizing. If they're not available, if they have already moved on to something else, then we can transition this Meetup to you if you want to become a new organizer. Because again, these Meetups are sponsored by the Continuous Delivery Foundation. And yeah, I can't provide the exact numbers, but let's say that this Meetup.com program is quite expensive. And we are interested to actually get the most of that in terms of active communities and cities. Okay, does it answer the question? Another question from Mike. Need to attach the detailed PPT or just the outline, will it be okay to submit the topic? Okay, so definitely you don't have to attach the slides. I'm not sure what is the exact application form for now. I'm guilty. I still haven't submitted my application. Yeah, I tried it once just to test, but you submit the abstract and some details. So let's try to see it together. So we are using Submitable as a platform. So and key, you can see that there are some descriptions, etc. Basically, what we discussed, you can also create your account. Let's see what I can do that quickly. I'll change it anyway. Please don't submit talks on my behalf if you're watching the recording. So, yeah, so, for example, I have no idea. So here we get the call for papers to a platform. And then what we do is, yeah, here's the form we need to submit. Yeah, please be aware of code of conduct, etc. But code of conduct there is, please be nice. Yeah. And here you submit session name, you provide the abstract. So basically, this is a key field and it looks like user experience is going to be great for this field. But yeah, probably it supports more markdown. I'm not sure. And yeah, you can submit here, you can see the limit 6600 characters. So it's not an extended abstract. It's just a few paragraphs of the description. Then you define a technical level, target audience. Again, this target audience on the white level. For you, you can define a monorail audience if you want. And yeah, discussion about whether you presented this topic. Yes, no session type. So you can see that currently the sessions are going to be quite short. Again, talk about the big agenda and to respond to our experience from the previous events when the big talks are not really well followed because it's hard to stay focused during the big online talks. So we focus on short ones. And yeah, basically this is the options we have and also tracks, which apparently listed. So when you apply again, you find to which track you submit. But yeah, this track isn't something you sign with your blood because the program committee can then make adjustments if needed. And yeah, also topic category, industry focus. So since the event is organized by Cloudbees, you also invited to list projects, your products you're using from Cloudbees. But if you're using just chink pieces, as you can see, non applicable. And then you can talk about use cases specifically. Then speaker info. Yes, again, speaker training. So that was a question. If you're interested, you say yes. And then somebody will contact you if you want to get schwach, of course, say yes there. And yeah, she can call us if you need that. Yeah, various information. Yeah, the form is quite long. But yeah, I think that it's quite straightforward. You just fill in the fields and then submit. And once you submit, then the program committee will receive the application. It will be a partially blind review. So what it means, we don't know the name of the submitter. But if you say that I'm a leader, let's say, of Qoops Fair project in your application, then yeah, it won't be that anonymous. So yeah, it's up to you. But yeah, generally, we try to do balance reviews. And that's why we have many community members representing different companies and different industries so that we can build the most diverse track. Okay. So any other questions? Yeah, there is another question from by Vub. He's saying that what is the difference between show and panel? Okay, so it's here. So breakout session is basically a common presentation. You do the talk, then you do Qoonee. Technology show and tell it's a short demo. So basically, let's say you turn on Jenkins and show whatever particular feature or just show how is your pipeline implemented. Lightning talk. Yeah, it's the same as breakout session but shorter. It's 15 minutes. So usually the difference is high because breakout sessions is something like 45 minutes, lightning talks 10 minutes. But yeah, this is 25 and 15. So the difference is not that high. Ask me anything is basically Qoonee. So you don't have slides, but you just say that, okay, I'm a Jenkins core maintainer. I have expertise there. Ask me anything. Or Victor Martinez can do the same. For example, about elastic together with the team. So they could apply and say that whatever elastic tools and continuous delivery, let's talk and ask us. So it could be a session panel is rather moderated discussion. So there are multiple contributors participating and there is discussion moderated by someone on particular topic. So for example, we could do panel discussion, let's say future of Jenkins together with Jenkins governance board members or something like that. Again, I'm just making up things though it might happen. And it is a panel session and workshop is just several hours events where you do presentation and the way you also show people how to do something. Again, we would like to have a free workshop for contributing to Jenkins and a free workshop for something about Jenkins pipeline. But it's yet to be announced. Okay. Victor, Rick, would you like to add something? Nothing from me? Yes, sorry, I'm talking too much today. There's nothing to highlight in my end. There was only one more question that someone was asking about to work on Jenkins add-ons development. I don't remember if we answer this question, but the question will be really set up or some cloud setup can be given from group. Okay. Yeah, let's answer that. So for Jenkins development, we have documentation. So if you go to the Jenkins site or website, I'm just going to the root. So here you can see that there is the documentation page and there is user guide, solution pages, tutorials, and developer guide. So if you want to participate, you click on the developer guide and there are tutorials which show how to get started. There is also reference documentation for details, various information for advanced developers like index of extension points, because Jenkins is built all around extension points. It's a tunational framework. So there are millions of them. But yeah, this advanced documentation. If you really want to get started, yeah, there is tutorial which shows how to create a simple plugin in a few steps using standard tools. So for developing Jenkins plugins, there are multiple stacks available. We usually recommend Java plus Maven or plus Gradle. For Maven and Gradle, we provide our parent forms. And here you can just follow these steps in order to set up your environment. So it's basically a step-by-step guide. Install JDK, install Maven, set up your environment, NLBeans, IntelliHID, Eclipse, and then going step-by-step, you create a simple plugin. Really, if it's something like hello world plugin with some configuration, et cetera. And after that, here, for example, you get a say hello world form parameter by using this plugin. And you follow this guide to create your first plugin. Then you can go to the reference documentation. You can see that the list is a bit longer. This list covers various topics, including, for example, how to develop plugins, for example, how to handle security, how to handle requests in Jenkins framework, how to develop web UI, including various configuration form, how to localize your plugins if needed. Then there are general guidelines about how everything works. Again, all this is living documentation maintained by contributors. So if you see any issues, you can just report them. So, for example, on any page, you can see report the problem button. So if you see something missing, something confusing, I clicked this button and I've got a new issue dialogue just on GitHub. You sling to the page and you're welcome to just provide some context. And then it will be trashed by the documentation specialist group. And maybe they will be contributor who will adjust it. And if you want to improve this page, again, you click improve. And here you enter editor on GitHub and you can just write it. So this particular page is not fun because it uses Hamel. So basically, it's auto-generated. But for example, some pages, let's say, like, let's say plugin site. This is the site we use for posting and policing the plugins. You can improve this page and you get this page in GitHub editor. And here, for example, you can just click preview and see the current contact because it's ASCII. We use documentation as code for the entire website and for the most of other components and links. So follow this guidelines. If you have any questions, so there is another page called Jenkins.io participate. It's basically landing for contributors. And here there is code section which provides some links, references for those who want to start development plugins or want to contribute to existing plugins. You can follow these guidelines and it needed the results, say, channel for newcomer contributors. So it's actually called newcomer contributors. You can join this channel and basically ask literally any question about anything related to Jenkins development. And then we either answer this question or root you to the proper channels. Because your channels in Jenkins might be a bit confusing at the moment. We have so many HRs, so many mailing lists because of specialist jobs, et cetera. But as a newcomer contributor, just use this channel as an entry point and we will be happy to help you. So there is another question from Vikash. He is asking that if my plugin works in my Jenkins, it will be published by Jenkins growth if it is visible? Okay, so dance is a bit more complicated. So we have plugin index basically released the most of Jenkins plugins, which are open source ones. We provide our own update centers. So when you go to Jenkins, click install plugins. If you haven't reconfigured your instance, then you will be using the default update center hosted by the Jenkins community. You can also use company internal update centers, et cetera, if you need, there are options for that. But by default, you use the Jenkins one. And if you want to host the plugin there, there is also reference documentation. And there is information about publishing plugins, which provides information on how to actually get the things hosted, how to configure this plugin, how to submit the application, and you can go just through this guideline in order to get the information. So yeah, we're about to rework on that because right now it's a bit complicated to find these common questions and give any feedback and reactions to the documentations are welcome. Yeah, we try to improve the documentation over time. Yeah, thanks for the links. Okay, anything else we would like to discuss today? If not, I will stop the recording and we can just do whatever free discussion of the record. So thanks to everyone who participated in the meetup and thanks for any questions. Looking forward to meet you at the Vops world or in the community channels. And if you have any questions, again, we have a Slack channel and please follow up synchronously. So thanks all and stay online if you want to continue the discussion.