 Hello, welcome to the Jenkins UI UX at first opening session. Just to clarify, it's not a grand kickoff. We want the 1 PM UTC. It's a small opening session. We are doing, well, on the morning in my time zone, just to prepare to answer questions and communicate with those who are not able to participate in the main session. And yeah, thanks to everyone who joined this meeting. So I will do a quick introduction to the Hackfest, and then we will talk about how to contribute. So we run this meetup on the Jenkins online meetup platform. And basically the idea is to just provide content for contributors, by contributors. So we won't have so many slides during this session, and probably no slides at all during some other sessions scheduled for this week. The whole purpose is to have discussions, to show a particular few cases, to do live demos. And everyone is welcome to participate. So you can just submit your own session proposal, or you can join the discussion in the chat or the meeting. You're more than welcome to contribute. So yeah, I will move the slides later. OK, if you have any questions, this time just ask in the chat. If you're doing the main kickoff session, you will be doing Koini in Zoom. And we have a regular channel, which is an official channel for this Hackfest. So if you have any questions, you can just go here and ask. And we are getting more and more participants in the chat here. OK, so let's talk about the event itself. You have seen some announcements because we are heavily using Jenkins media for that. So it's a one week long UIX Hackfest, and we invite all contributors to participate and to improve the Jenkins user experience together. Why it's important? Yeah, Jenkins user experience is one of the top items we get as a feedback from Jenkins users, scenario which we could improve so that Jenkins looks modern and we make it easy to use for Jenkins users who are not experts in the system. And we have a number of items related to Jenkins user experience on our roadmap. So as you may see, I will be switching between windows quite often today. So we have a work on progress roadmap and many topics on the list are related to user experience or user interface. So there are new features in common, but also there are areas related to Jenkins look and feel, to front end, and to Jenkins documentation. So when we were discussing what we could do for this hackathon, we thought that we could focus on two main topics, is improving user interface and improving user documentation. We are well aware of that user experience is a much wider topic. If you have other ideas in mind, you are welcome to participate in this service. We also invite you to spread the word about Jenkins. For example, if you participate in this event, just share your experiences or share your experiences about Jenkins or contributing to Jenkins, or if you are interested in particular features if you want to share it. Just for example, write a blog post, create an article or record a video with a session for that. It all counts because it helps users to get more information about Jenkins and hopefully to improve their user experience. Also good news that thanks to our sponsors, we can offer some Schwag and prizes to contributors. I don't have it on my slide there, but I have them here. So you'll have a point here. Jenkins is the way it teaches. We will have socks and some stickers and probably something more. So we are still working on that. But yeah, thanks to everybody who contributes and hopefully we'll be able to distribute some cool stuff after the event. OK, let's talk a bit about the format. So we call it Hackfest. It's not a hackathon. Hackathon is usually perceived as something when a lot of hackers gather together, just stay indoors for 24 hours, 48 hours. Sometimes they get some sleep, not that often though. It's not how we are going to set this event. Actually, the idea is to do an online event where everybody can contribute regardless of your Jenkins development experience, regardless of your time. So if you have a few hours, it's fine. If you have a day you could dedicate, it's awesome. But generally, as much time you could dedicate, everything is appreciated. And we want to mostly focus on learning, sharing experiences. Of course, we want to have some fun during the event. So we'll just focus on topics which are important to you, topics you want to discover. And of course, if you have any user experience issues with Jenkins, focus on them. Before the event, we did a survey as a part of a SVP where we asked the users to provide some insights about the main issues with Jenkins user experience. And we will be processing this information. Thanks to everybody for responses. And the additional thing that this event is actually a newcomer friendly. So if you have no experience with Jenkins development, this contribution to Jenkins, you have some newcomer friendly issues for you. We also have learning materials. And we are happy to help you. So if you want to participate but have no experience, it's totally possible. OK, before I press it, I would like to thank the ORC team, which helped to assemble this event. So thanks to Mark Waite, Tracy, Tim Jalhamp, Mark Jackson, and Lisa Tonk. They helped a lot with different aspects of this event. And also thanks to special interest group members who helped with reviewing stories, preparing project ideas, et cetera. There was a lot of groundwork before this day. And we much appreciate that. I also want to thank our sponsors. Thanks to Cloudbees. Thanks to Continuous Delivery Foundation. Thanks to them, we have Schwag. We have a platform for online meetups. And we have for event organizers so that we can actually run this event. So thanks to them. OK, before we press it to the next section, do you have any questions? OK, then let's move on. So let's talk a bit about participating to this event. So it's quite easy. And there are just a few steps. And we will go through this step. So the first step, if you haven't done it yet, you need to register to the event. So why it's important? We want to distribute Schwag. And in order to do that, we need to contact there somehow. So we actually asked you to submit a short Google forum with some details. You can see an example of my forum, for example. And basically, we need some information to trace your contributions, to display on the website. And you also collect some information. For example, there is a question of what are the top three things we could change in Jenkins. Again, it's just for our information. And well, you can see what I answered. I didn't think too much about that, but this is my answer. And yeah, this information will be used later. So if you haven't registered, please do so. Because that's what we need in order to track that. Then please join our Gitter channel. So this Gitter channel will be used for communications and announcements during this event. Yeah, before we started this meeting, you may have noticed that we had some issues with the community use proper video channel. So yeah, issues like that will result in this chat. So it's good to follow that if something goes wrong. And yeah, join or watch our kickoff meeting. So basically, this is what we record now. And it will be published on YouTube. And later today, we will have a full session with more content. So stay tuned for that. And after that, you will need to think about the projects you would like to work on. You can just choose something and start contributing. Basically, that's it. I will talk a bit about choosing the projects later. One of the questions we usually get from users is how to contribute. For that, during the previous months, we invested a lot of time in creating new contributing guidance. So we have them on jengisai.io slash participate. And you can find various stories. Many of the stories are actually user experience, if not all of them. So for example, if you want to code, you'll go here and you can find links to materials. You can find links to locations of organizations. And if you want to find new camera, you can also find some here. So for example, I can go to GitHub or jengisjira. And I guess there will be quite a number of issues right now. So you can just take something like that. Pretty much the same for documentation, for design, everywhere you have some guidance and some pointers to locations where you could contribute. What you could do during this hard test specifically. So jengis is a diverse project. We have a lot of technologies under the hood. So for example, if you're a Java developer, if you're a JavaScript developer, or if you want to learn a goal, there is something you could work on. And basically, there are many languages and technologies available. Same for documentation. We mostly use the commutation as code, markdown and askdog. So it would be likely something of that. You're also welcome to contribute to testing and specifically to use that experience testing. So for example, testing for installation guidance, tutorials or new features we are working on. Also, coding documentation reviews. In this test, we can't not only code contributions, but also any other kind of contributions. So you're welcome to help in any area. And as we talked before, you can also create various content or just help others. All of that would count as a contribution and we will much appreciate that. For this event, we split all the topics to three tracks. So one is dedicated to user interface of Jenkins. So we have some stories for improving look and feel, improving accessibility, creating read-only UI, themes, et cetera, et cetera. We also have user documentation track, mostly focused on documentation and on Jenkins.io. And we have a track which could rather focus on creating additional learning materials and sharing stories, which is called spread the word. So these are three main tracks. But for example, user interface track also includes documentation because when we create new features, we need to document them, creating tutorials, demos would be much appreciated. Same for user documentation. Yeah, you may see that there is a lot of documentation, but at the same time, for example, we want to make our website mobile-friendly and definitely implies a lot of coding. For example, in JavaScript, patching CSS, et cetera. So if you are not a tech writer, you can definitely find something in user documentation track as well. So if you want to find more information about projects and project ideas, we have prepared a website for you. Actually, this is our main page, your UX hack first. And here you can see that all the information we talked about and much more other information, it's actually listed here. And for the tracks, we also have project ideas which provide some information, some links to the tasks. You can basically pick one of those and start contributing to this area. So yeah, this is what we have. Common question we get is, what about user experience contributions to the areas which are not listed? So for example, here, yes, we have a number of projects to user interface, but these projects are rather focused on a particular topic. What if you want to improve a particular plugin? Yes, it's possible. If you are maintaining that of Jenkins plugin, you can also work on your plugin if you want. If you wanted to address other area of user experience, for example, working on better localizations, creating some designs, et cetera, or even creating some artwork, it's also possible. So we do not list it on the tracks, but if you feel strong and want to work on this area, you're more than welcome to do that. If you want to invite others to work on this area, and if you want to champion that, you're more than welcome to do that. You can just propose a patch for this site and your project idea here. So for example, here, you can just click improve this page and edit this page directly in your browser and suggest a public request. I won't be doing it right now, but it's quite handy. Okay, so how to record contributions? As I said, we count not only code contributions, but also all kinds of other contributions. Jenkins is a huge project and whatever helps user experience help the project. I appreciate that. Two track contributions, we created a mini site on GitHub, and this mini site will be actually used for tracking contributions. We can discover your pull requests, et cetera, by using the GitHub IDs. But for example, if you post a video or whatever, it's definitely required to post an event here. So we have some examples. For example, Raihan, one of contributors. They will already get some patches. For example, this is a sample. So basically just a short summary and links, and we use GitHub issues for that. Well, why we use GitHub issues? Because everyone can create them, and we can easily aggregate them into reports later. So for example, if I want to record a contribution, today we have a video. So I guess it sounds a spread of words. So I say that, okay. Yeah, I'll say Huckfest kickoff session, for example. So links, do we have something? I have slides, for example. Well, let's link them from there. Slides, so just let's create a bit, yeah. I think it's not as strong as you think. Okay, so screenshots. Yeah, I don't think we really need something. So I will just add a bit. So here's my contribution, and then this contribution builds the process by the team and the edit to the list. So on the main site, you can see that we have a number of contributors here, and we will be extending this list based on contributing to reports. So for example, I know for sure that submit has already submitted a contribution here, right? So a documentation on using incrementals. So let's just add submit to the list. The documentation, actually it's also show where the tools are supported. So let's check. We are using a standard code called contributors for that. So let's see. Yeah, they have tools. So, okay. So let's just comment. And after that, in a few seconds, we should create a pull request. They might have, but yeah. So we have a pull request from the bot, and we will just merge it. And voila, now we have submit on the list. So congrats. And yeah, this is how it works. So we will be recording that. And after that, we will be processing all the report of issues in order to create reports. And you can ask to submit reports here, even if you create code. You don't have to submit such reports for any contribution. For example, if you work on a particular area, like improving system read permission, you can just submit, for example, a daily report with a number of issues that are heavily related. So it's totally up to you how you report that. I'll give you the way I should now close this issue. Okay. So yeah, that's the plan. And we will keep working like that and everybody is welcome to just submit the contributions. Another important topic is about communication channels. So here you can see the number of channels. We have already discussed the main, sorry, the literature. We also have a number of mailing lists. Basically, all our content is created by special interest groups, user experience documentation on advocacy and outreach. And each of these special interest groups has its own mailing list. So if you have a question about particular topic, you can just go there and ask all these mailing lists to the public. So you can see that one panic message is here. Don't worry, this message is a spam. But yeah, that's the idea. So we can go here and you can also report something in the developer mailing list. In addition to that, we will have office hours. I will talk about them later, but you are welcome to join any of them. So when you communicate, please keep in mind our code of conduct. We have one. So Jenkins code of conduct is based on a contributor covenant. We use version 1.3. But yeah, if you're afraid about that, basically it says be nice. So please respect all the contributors regardless of their experience, et cetera. All of us want to improve the project and let's help together to make this event a great experience for everybody. So yeah, that's a summary of the code of conduct. Just this follow-up. In addition to the communication channels, yeah, I already talked about office hours and we have a number of other events. So if you want to access these events, you can find links on our main website. At least for some events, you can see for example, we have a hard-pressed session at 1PM UTC. If you click at the sleepy here, you can find it on the Jenkins online meetup platform. So this is our main session in several hours. And you're still welcome to join that. We will also have a number of knowledge transfers for developers, for users and contributors. Again, it'll be a host of these sessions. The Jenkins online meetups. So you can just go to any of them at SVP and you will see a link so that you can join this session. In addition to that, we run office hours. So you can just go to Jenkins UI, your hard-pressed calendar. Oh, I need to fix the link. So it looks like that. So we published a public calendar. You can just add it to your Google calendar and watch it. So for example, here you can see a number of events during COVID days. So right now we have for this early birth session and every day during this time, we will have open office hours. So what it means, there will be Google Hangouts meeting. So we won't be recording that. But if you have any questions, if you want to discuss something or just chat with participants, feel free to join and you're more than welcome. Same for evening sessions. Evening for me, but you're morning for America, so for example, we will have this session from Tuesday to Thursday and on Friday we will have a closing session. So you can also find all the plant events in this calendar. You can see that it's quite parked in the beginning. It's not that parked in the end. So one of the reasons, because we haven't published all the events yet, and if you want to present something, just let us know, we will publish it here. Okay, any questions so far? Okay, then let's move on. There are just too many links, but okay. So online meetups, it's something we already discussed. So I won't spend too much time there. Let's talk about the tracks and projects. So I already spoke a bit about that in the beginning. Let's just go to main page. Okay, I'll do something like that. So you have access. So let's go to our main page. And here you can find all three tracks we have. And for these tracks, we have projects listed. So again, this list is a kind of moving target. So we will be still updating during the half past, I think more links, I think special topics, depending on the contributor product. But yeah, let's go through the projects we have offered in the list. During the main kickoff session, we will have more presenters. So with one with just me speaking about all other things, but well, so please bear with me for this session. So one of the first areas we have is just modernizing Jenkins user experience. We have an epic created by UXC, which is focused on particular tasks. So there is one here. If you log in and you see nothing most likely it's because you need to log into the Jenkins Jira. Unfortunately, it's configured in a way that it doesn't display tickets if you are not logged in the system. So here you can find some issues you want to focus on. You can see that there is already a good progress, but again, we will be adding more tickets here. So you're welcome to just pick something and contribute. And basically the main goal here is to improve the landing page and the main controls on the landing page. So it's a project on the UXC. So I can hint some examples. Well, everybody knows Jenkins Web Interface, right? So yeah, we did some improvements over the past months. For example, we improved typography, we improved look and feel, but if you just open this page you can definitely see something which could be improved. So for example, this build queue, it's hard to navigate, it's quite long called executor status, you can ask for irons to get there. And yeah, there are many areas here and there which we could improve. And basically the same for any other page. So if you see something you would like to change which is not listed, please feel free to do so or to discuss it with contributors and do so. So we want to improve. So it's like quite small pop up here, probably also a topic for improvement. Okay, so basically we want to change many things here. In addition to that, there is also a number of issues reported in Jenkins Jira. So we have a lot of open issues in Jenkins Jira for approximately 20,000 issues. So definitely there is a lot of stuff you could work on. But we prepared some queries which could help to discover issues. So for example, here, if you're looking for a newcomer-friendly issues related to user experience or UI, and here's a query where you can find these issues. So yeah, there are around 40 of them and you can see that some issues are located in plugins, some issues are located in Jenkins core, but all these issues account towards the goal. Actually, you can contribute to any project within the Jenkins system, not even to plugin. So if you want to improve standalone component like a Jenkins Kubernetes separator, it's also more than welcome. If you experience contributor or if you want to try something advanced, let's remove new different label. And now we have more than 300 issues. So definitely something which could be taken. This list is not extensive. Again, we heavily rely on contributors, property setting labels, et cetera. But so if you want to dive deeper and to discover more issues, you can definitely can. Yeah, so it's just starting point with some information for you. So pretty much the same for other projects. I will quickly do introductions without spending too much time. So web UI accessibility is another site of look and feel updates. So we want Jenkins to be easily usable. And it's not only for people with disabilities, like so accessibility is sometimes considered like that, but it's not. It also applies to various areas. For example, mobile to use just other special requirements and if you're willing to improve that, we have some stories for you. So one of the major stories we are working right now is changing the Jenkins configuration UI from tables to divs. So if you look at this UI, so one of its problems, it's actually the structure is quite hard coded by tables. And they, well, it may look good on this device, but if you start resizing that, so this page may be looking slightly okay. Well, at least it works. Some pages may look terrible, especially configuration forms. One of the ideas is to change everything and to basically switch to divs. It might sound easy, but actually it's not because there are some changes required to do that. We have a pull request, we have Jenkins here, Jenkins. So there is a pull request here, which is ready to go future-wise. So you can see that there are 264 commands here already. And this pull request, it's not that deep, but it changes all layouts. We know for sure that it's going to cause some breaking changes in plugins, and we want to minimize the impact. So we invite contributors to try it out. I can show how to do that. And you can, for example, do some user experience testing. You can submit some patches for plugins, and we will appreciate that. So again, we can go to our Gira. And there is, so, yeah, definitely there is no quickly accessible links from this ticket. Again, we will be cleaning up these pages later during the hack test. So I know for sure that a team has created a number of issues. So let's go here. Yeah, here's a dashboard for us. So here you can find some issues related to redone the jink. So redone the jink is separate. Okay, let's go back. So, yeah, we'll make sure that links are linked from here, but you're welcome to just do some testing and submit the issues and the patches for areas which don't work well on resized phones. Okay, yeah, so that was the wrong detour. So what are the projects we have in the list? So for example, another important project for us is system read permission. So currently we promote configuration as code in Jenkins includes Jenkins configuration as code plugin where there's tools like Jenkins Kubernetes operator, Helm charts, et cetera, et cetera. And also of course pipeline as code because you can also define all Jenkins jobs as code. In order to make it more comfortable for users, we want to introduce redone the views of Jenkins configurations so that you can view them. But you cannot really modify them. And you can use it for diagnostics for quick analysis. There is a number of changes which have been already integrated into the Jenkins core. There is an announcement draft which we will like at least today. And this announcement basically invites everyone to try out this feature and again to report these cover issues to some contributions. And for that, yeah, the dashboard that I was showing you can find a number of issues which are related to particular areas which could be also made redone. For example, monitoring of Jenkins master on the monitoring plugin. Right now with this feature, it's not supported but we could make it supported and so on and so on. So if you're interested in configuration as code, this project might be interesting to you because as an administrator you would get more access to diagnostics information and instance while not having full admin permissions. Okay. And we also have GitHub projects and other links you can find. We also have developer guidelines for this project. So if you want to contribute to plugins and there is a lot of plugins which need to be integrated, you can refer to these guidelines and you can find examples and basically you can take any plugin in Jenkins which offers system configuration and start the support for that. Okay. Any questions before we move on? Yeah. Another topic which might be interesting for contributors is UI themes. So you're welcome to do that and you know that there is a number of themes available in Jenkins. One of the engines for that is a simple things plugin which is quite widely used on Jenkins instances. And there is a number of cool themes for Jenkins along improving this UI here and some other plugins for material UI, this new two theme. It's also based on material but it is a lot of improvements. And if you're interested in creating themes or improving existing ones it's something we invite to do during this hack test. And we also want to address one issue which is being placed frequently is about having an official dark theme. So right now we have on the classic theme but if you could create a dark theme it would be really nice. So if you're interested to contribute to that if you're a fan of dark themes, personally I'm not but if somebody wants to do that, let's do that. It would be fun. So I'll say you can create documentation. You also think about creating a themes marketplace because right now what we have for themes is basically this page created by a simple theme plugin in Jenkins because we could do something more interesting like having a small listing of themes with some documentation with compatibility requirements with screenshots and making it available let's say on GitHub I.O. So if you're interested to work on that please do that. It will be interesting. So we have some more advanced topics which we have in the list. For example pipeline visualization. We are well aware about lotion and pipeline stage review situation. It's one of the top feedback items we get from users. Unfortunately we were not really able to figure out how to make this story new common-friendly but if you like challenges and if you want to try it out we can definitely talk about this area. Same for credentials management. We could improve the UI navigation there and we also invite you to work on the developer tools because if Jenkins contributors get the better developer tools for UI they can basically take better UIs so it contributes to the goal. We have a number of items here for example extending UI samples. We have a special plugin which has a bunch of UI samples. It doesn't even have documentation embedded right now but yeah, so that is a lot of opportunities to contribute and of course you can create more samples specifically for example for JavaScript. They will be doing a session about beautifying Jenkins plugins with JavaScript. So yeah, this could be a good source of inspiration for you. Also, Dennis, he's on the call today. He proposed the Improving Fintailage ID integration for Steppler. So Steppler is UI framework we use under the hood of Jenkins. Basically, the SDPI and then Matlin Cop Request to Java Objects and there is a framework which uses that and there is a number of issues you could work on and if you develop Jenkins plugins in the Improving Fintailage ID probably you could propose even more enhancements there. And last but not least also creating archetypes it's basically a separate part of samples but we have template Maven projects so that any contributor can quickly create a new plugin. So right now it has samples based on Jelly and Steppler but if somebody wants to create advanced examples based on JavaScripts, et cetera, please do so. It will be also helpful. Okay, so a lot of information on short time. Do you have any questions or should we place it? Okay, then let's move on to user documentation. So again, user documentation is not just about documentation per se it's about everything related to layouts. We have two main documentation sites available right now. So one is Jenkins Ion. So Jenkins Ion is our main website. It's fully managed by a configuration as code. Now it's also based behind CDN, the set is static. For example, here we have user guides, we have solution pages, et cetera. All of them are allocated under doc. So this documentation, many pages came originally from Jenkins to Viki. We introduced this site in 2016 as a part of Jenkins to the Xero. We are currently working on migrating the documentation and there is a lot of stories. And you can actually contribute to any error within this documentation. So for example, managing Jenkins, there is a lot of content which could be added here same for user for installing Jenkins. Using Jenkins, well, it's quite empty at the moment. So if you have any ideas about topics which could be documented there, it would be much appreciated. You can also work on the improvement navigation, et cetera. Because yeah, you can see that right now this site is quite complicated. Well, it's even worse if you browse it to mobile. It could be improved. Also, for example, there is no search support on the Jenkins website at all. Well, I would say that Google works quite well, but if we had a better way to do some search, it would be definitely an interesting project. At least the directive to Google ideas or to all the search engine defined by the browser. So web UI experts probably have a better idea how to do that. So you're welcome to contribute to basically any area. You can see that there are two buttons here. One is improve this page. So basically all these pages can be edited just in GitHub if you don't want to install IDE. If you want to install IDE, actually you have contributing guidelines. So contributing which defines various topics like how to build it, how to run locally. It's based on Docker. So if you're a Windows user, just let me know, I will try to help because it might be a bit challenging. And there is a lot of common cases documented here. So you can just start working and contributing and we have a number of issues reported. So here you can see that there is a number of projects. One of important projects which I already referenced is migrating from Wiki to Jenkins Ion. So there are still many pages which are located on the Wiki, which is read only, often obsolete and you want to do the migration. For migration, we have a exporter tool which automates some bits and you are welcome to contribute and migrate some of the pages to the new location. It's for plugin documentation. It's basically the same for tutorials. So I'll probably go to Jenkins Ion again. So here we have, for example, installation guidelines, tutorials, all this information could be improved and improved a lot for tutorials. If you test it on modern platforms and you submit patches, it would be great. And for tutorials, you're welcome to create new tutorials. So right now we have only a number of them hosted on Jenkins Ion. And if you create a great tutorial, you don't have to put it on Jenkins Ion. For example, if you want to put it in your own blog like on Medium.com or DevTor, you can do that. You can still post a link and it will be much appreciated because Jenkins is a developer tool. It's a tool for automation engineers and many people are actually interested in automating their particular pieces. So if you have something to share, it's definitely a great opportunity to help users. So tutorials are here. You also have solution pages for specific use cases. So for example, if you're Android developer, if you work with Docker, if you work with embedded systems, we have something. So you can see that you don't have so many solution pages. So creating new ones, for example, for Kubernetes or maybe for Maven would be useful. So if you're an expert in specific technology or if you just read a lot of particles and you're interested to compile this information and to share the links, feel free to work on these pages. You can see that they're quite simple and rendering could be improved a lot. Content for existing pages could be improved a lot. So again, please feel free to do that. But extending these pages again can help Jenkins users to find solutions for their own use cases. Okay, so I guess I covered many project ideas here. So just work on that. One area I didn't cover is about plugin documentation. So the second important location for the communication of plugins. So we have 1700 plugins in Jenkins right now. So for example, we were talking about configuration as code. We can go to configuration as code and you can find some documentation here. So this documentation, again, it's documentation as code but instead of being based on the Jenkins IO website and it's a repository, it's actually located right inside the repositories. And we encourage contributors to work on documentation for any repository, adding more information, improving these pages. So for example, for configuration as code plugin, it's hard to find the details in the documentation because you have to scroll forward before you discover the documentation section. So just reordering the content, making something more visible, it could be also a great contribution. Obviously, many plugins would benefit from demos. For example, Jcast plugin has a lot of demos. Many plugins have no demos at all. So if you want to create something, please do so. And we also invite you to contribute to the plugin documentation page because many plugins still have documentation on Jenkins Weekend. I can actually show how many. So again, we have a weak exporter tool. And if you will click on the progress button, you can see how many pages still need some migration. So yeah, total we have 1700 plugins. We have migrated almost 500 plugins to GitHub, but more than one thousand to go. So if you're interested, you can just take one of this plugins, migrate the documentation to GitHub, copy edit that, update that. And it would be really available because again, by moving this documentation, by improving that, we improve experience for documentation users. And also we make it easy to contribute because right now the documentation on week is basically read on that and we encourage all plugin maintainers to migrate. So if you're interested to contribute this, just do so. If you're a maintainer of a particular plugin or active user, yeah, it would be really helpful if you could do that. Okay. Any questions about the documentation? Okay. So yeah, the last section, which is quite short is about spreading the word. So we invite you to share experiences about Jenkins using any channel. For example, you can just write articles, post them on your personal blog, post them on Jenkins.io. The link is broken here. I will fix it later, but yeah. For example, here we have a Jenkins blog where we post updates, where we share information about releases, but we are also happy to publish your key studies here. Or you can just do it in a personal blog post. If you wanted to share a success story, we have a program called Jenkins is the Way. And actually we follow this Jenkins is the Way theme in the hackathon. And we have a special site for that, where you can find the stories created by Jenkins users. Today we will have a session by Lisa Tonk and she will present this website and the stories. So I won't be spending too much time on that, but what is thinking you to know, you can share your story. So there is a simple survey on survey monkey, which you can pass, and then the story will be submitted and processed. And again, it counts towards a hard test contributions because we really appreciate user stories. It helps us to get feedback. It helps us to highlight that Jenkins can be used in different areas and these cases. So if you're interested, please do so. What else you can do? You can just post something, you can record videos. So for example, if you want to have a walkthrough about the plugin, or if you want to just show how your instance works, how you automate your pipelines, please be welcome to do that. Again, we ask using Jenkins is the way hashtag or label just to make this more discoverable for us. So that we repost to that and for others. You can actually use any other ways to promote the project. So this is just a number of examples here. And if you're interested, we still have some time later this week on Thursday and Friday. So if you want to present, for example, your work on Jenkins user experience or new features and comment on the project, please let us know. We are happy to host a session as a part of this hard test. Okay. So I think I covered everything I planned during this presentation. So again, it's the first one. So if you see any gaps, please let me know. These slides will be published basically just now. Slides from the morning session. Oh, that's it from me. Do you have any questions or suggestions? Is there anybody who's contributed access to the Stapler idea plugin? I do have access to that. Okay, so you'll be able to merge the PRs. Yeah, I will be able to do that. So I definitely know people who could help. If something is needed. Okay, that's good. Yeah, and for example, if you need to set up continuous integration there, again, we can help you there. So we have a number of channels and you can ask in any of these developer channels. So we will be providing assistance. And if you do not know where to ask, just ask in the hard test beta channels so that you'll be able to help after that. At least point you to the right channels. Okay. Okay, so one topic, which might be important is about how to collaborate. And because it's highly probable that some projects will have multiple contributors. For that, please use Keter Chat for coordination. And later, if you have many such collaborations to go and come, we will just, let's say running Google Doc where we will list teams and help teams to collaborate with each other. So right now, we don't have for that set up, but if needed, we can do it during the day. So anything else before we close? I guess not. So thanks for joining this session. If you'll be published as a video shortly and just have fun and looking forward to your contributions. Thanks for your time. Thank you. Bye.