 Okay, and we are being recorded. So welcome to the UIX HeartFest and welcome to the last meeting of the UIX HeartFest. So today is June 1st and we will summarize the key achievement of the project, talk about them and talk about what's next for the project. So that's our main objective and this is just a summary call. So we will be publishing the recording. My next step doesn't work. Okay, so first of all, I would like to thank all the contributors. Thanks for your participation during the event. In total, we've got 53 contributors. As you may imagine, I cannot put names on this slide, but if you want to see more details, there is a link above. And here you can find actually all the information and links on our UIX HeartFest site. So you can find more details here. We are still processing late reports for the contributions. So maybe the final number, yeah, it may change a bit, but yeah, anyway, we've got a really good number of contributions and thanks to everyone who participated. So yeah, we've got a lot of people working on documentation, on UIX testing, on patching Jenkins and also on sharing the stories. So it was amazing for one week during the working week. So thanks to everyone who was able to dedicate some time and help us to move the Jenkins forward. And thanks to the org team and the special interest groups who helped this event to happen. So there was a lot of overtime work, a lot of late night fixes and reviews to keep this event going. So it's a much appreciated thanks. And of course, thanks to all the sponsors who will be helping to spark and these prizes for the events. We'll talk about them later, but yeah. Again, thanks to everyone who contributed to this event. Let's spend some time and discuss how the highlights you've had. So first track we had is about user interface. So if you see this slide, it's not a definitely a reference user interface, but yeah, it's just a quick summary. So what we've got during this hard first. So first of all, we had done the Jenkins integration preview release and we've got a lot of distributions, bug treatise and just your testing and reliability testing there. We've released a preview of the dark theme and there were many improvements in various components like credentials management plugins, script security, Jenkins core and many other components. So there should have been links to the demos. As you may see, I forgot to put it on the slides, but I can show you how to find it. So during the event, we were using Jenkins online in order to record all the sessions we've had and we're recording today's session as well. And if you want to find a recording of the session, you can just go here and you can find all the sessions here. If this list is too big for you, you can also go to the Jenkins UI UX hard first. Here we have a presentation stuff where we aggregate presentations from all sessions we had today. So for example, here demo sessions and you can find a link to the recording here. So while we're here, we'll just put the link, but yeah. Thanks to everyone who presented their demos. I will just show a number of key stories, but yeah, there is also a lot of improvements and later we will be following up with a blog post, with a full list of contributions. So the first story, as we said, read-only configuration. So now it's available. So everyone who manages Jenkins's code, now you can switch your configuration to the read-only mode so that you can occasionally change the settings. And we will keep working that in order to make more diagnosability analytics tools available for read-only admin instances. Another achievement we had is Jenkins dark team. So we started basically from now where there were a number of teams, but we created a new one, shout-out to all contributors and especially to team Jakob, who was driving this project. So now we have a dark team in preview. Right now that is Jenkins weekly release, which is going to be released, maybe in a few hours. Starting from this release, this preview will be official, but even now you can try it out on your instances and if you watch the recording, you'll definitely be able. So it wasn't just creating a new dark team. It's basically considering how Jenkins theme extensibility works. We switched the Jenkins code to CSS variables. So now themes take just dozens of lines of definitions instead of hundreds of lines like it used to be before. And we also spent a lot of time on the UX testing and capability testing for this team. So for example, if you go to the repository, you can discover a lot of reported issues. And this is just issues which haven't been fixed yet. Many issues have been fixed during the hard first. And if you're interested to contribute, you're welcome. So this will be released just in a few hours after this recording. The next thing we will be working on was migration of configuration user interface from our tables to these. So it improves visualization of narrow screens and especially on mobile devices. It also just makes Jenkins look better for configuration pages. This feature hasn't been integrated yet, but we are working on that. And again, we invite all contributors to participate, but still doing this hard test, we did some testing and now we have much more confidence about this change. And hopefully we'll be able to integrate that in a few weeks or maybe in a month. So let's see about that. And another major improvement we had is script security plugin. So if you have ever managed script approvals today, you may know that it's extremely difficult. So now thanks to Wadi Kholangier, we have a new web interface. There you can manage approvals, you can define them, you can see usages of script approvals and manage them. So it's a major improvement for Jenkins admins who allow custom scripting from the main instances. What else did we had? For example, there was improvement in auto grading plugin by Uli Hofner. Now it supports Excel screens. So many reports, many study analysis reports and summary pages are even more extensible than they were before. If you participated in a knowledge transfer session on Monday, you may have seen how it can be developed in practice and now US plugin developer can also adopt that. And we definitely got a great foundation for building the dashboards, writing these Jenkins plugins without creating any additional tool for that. And I guess that's it regarding features. Again, this list is not full. We were still working on particular cases and your UX, I mentioned some names, but in general we had more than 30 contributors working on this area. So thanks to everyone who helped to improve Jenkins user interface and to deliver improvements and plugins. Let's switch to the documentation. Documentation is also a great part of the user experience. We have good news to share there. Yeah, the documentation, thank you very much to everyone who contributed the documentation. All like that slide was a perfect one. Is it okay if I share my desktop to show the slides the rest? Great, let me do that. So what I wanted to highlight was that we've had wonderful contributions to the user documentation. One of our beginning points was that we have lots of information that is in the Jenkins wiki that would be better suited and better presented if we moved it to Jenkins.io. And we've succeeded in moving over 40 documentation pages from the wiki to Jenkins.io. In addition to that, it's now actually 30 or more plugins that during the last week advanced their motion from using their documentation on the wiki to instead putting the documentation right inside their GitHub repository so that it can be managed as code. We love that transition, both the wiki and transition from wiki and the transition from wiki for plugins to documentation as code for plugins. Excellent result. In addition, we did documentation updates using various sources of content. The Docker Solutions page has been improved. The many sections have been added to using Jenkins to managing Jenkins and a substantial improvement to the Jenkins system property list. There's a summary recording available. The link is there. And what I'd like to highlight further is some additional changes. We switched to using GitHub issues instead of using the Jira system for our documentation issues. And that has been a major positive. We identified a number of issues out of good first issues. And new contributors picked up these good first issues and did great work with them. Six of the 11 open good first issues that are currently open in our issue tracking already have someone working the issue. Great progress. Nine of the 12 closed first issues were closed during the Hackfest just last week. 26 of the 57 closed issues that have been closed in the lifetime of our time on GitHub. Issues were closed last week during the Hackfest. And 16 of the currently open pull requests are from Hackfest. So we're getting great results by using GitHub issues and great results from contributors like you. Thanks very much. Now there's still more to be done. We have over 200 pages on the Wiki that need to be migrated. We've triaged roughly one third of those and need more people to help us triage them. The triage process needs someone to look at the Wiki page, decide where it belongs in the Jenkins documentation set and then to create an issue in GitHub to track that. So we need more reviewers. We're looking for those. I'd like to highlight some of the pages that have come as a result of last week's Hackfest. So first thing to note, 36 pull requests were merged last week and there are 16 new pull requests still to be reviewed. In the managing Jenkins documentation, we've got a number of new additions. We've got additions in the using Jenkins, including using local language, including how you use fingerprints, including how you reference another project page. Those things added by new contributors as by transferring content from the Wiki into Jenkins.io. Thanks very, very much. Now, in addition, we're grateful that Devon Nussbaum, one of the experts on pipeline, extracted the pipeline CPS method mismatches documentation from the Wiki and placed it here, doing a serious and significant rework to be sure that it was current and correct. So the Wiki transformation process is not just copying content. It's thinking very carefully about is this the correct thing to say? Is this current and accurate? Similar happened for the Jenkins CLI. And we're especially grateful to Daniel Beck for his work on Jenkins features controlled with system properties. This page describes many of the properties that are in Jenkins that are controlled by various special flags. And it helps users to know what those flags are so that if they have to control something, they can. Well, this one is worth noting for me because Daniel had to clean up a mess that I had left behind and he did a brilliant job of it so that when I hover over this link, it just works. When I click links here, it just works. In addition to the benefit of what he did there, the glossary now has the same exact capability so I can point to one of the terms in the glossary and the links work and lay out beautifully. Special thanks to Daniel and sorry that he had to clean up my messes. It was wonderful. Grateful also for the plug-in migration progress that over 400 plugins have now migrated to documentation as code and there are pull requests pending for another 90 plus. Really great results from the documentation portion of the one week long hack fest. And, oh leg, I think that covers mine. Do you want me to continue showing slides or do you want to take the control back? I can take over the control. Okay. Thank you for the summary mark. Okay. So our third track was spread the word. Basically it was about promoting Jenkins and recording content, recording user stories and we actually had some. So during the hack fest, we recorded 10 knowledge transfers and demo sessions for Jenkins users and Jenkins developers. I've already presented this link. You can find the recordings there. Also, we were promoting the Jenkins stories on Jenkins in the way portal. We had eight stories fully submitted there and there are some stories in progress. So hopefully they will be finalized and thanks to everyone who shared their success stories about Jenkins. Then there was a number of tweets, LinkedIn posts and blog posts about Jenkins. If you're interested to find them, please use the Jenkins the way hashtag on our social media platforms. And last but not least, we also launched the Jenkins the way comics. So just let me show you these comics first. So thanks a lot to Comet Street for creating that and thanks a lot for everyone. So we'll have more of these comics soon. Also, thanks a lot for your posts. I've just put a number of them on the page. They do a lot more. So thanks to everyone who shared the experience from the hard fest experience from using Jenkins or information about new features. It helps us to promote the project. It helps us to talk about more contributors and finally it helps Jenkins users because the project gets a lot more features and visibility can. So thanks you and we appreciate this feedback. So let's talk a bit about what's next for the hard fest participants and for those who would like to participate in such events in the future. So first of all, we said that there would be Schwark and prizes and there would be. So we are processing the hard fest results. We'll be contacting the participants soon. Yeah, there will be t-shirts. There will be other goodies we will be distributing soon. So stay tuned and we have your contacts. So it will just happen in a few weeks because we still need to analyze some details but we will definitely do that. We will also appreciate your feedback about the hard fest, about how we could improve. Again, it was our first experience of doing online hard fest like that. We had a few events before but they were rather focused on a particular topic or they were part of October 1st or other wider events. So if you would like to share your insights, please fill in the feedback form. This feedback is full anonymous and we will appreciate any suggestions and feedback about what we could do better. And of course, if you have something positive to share about your experience or something we could repost, it would be also much appreciated because we could use this information for the future. Hopefully it won't be our last event of such kind. We have already started discussing having more events. So your feedback would be very appreciated. Now we will share links later in the email to all the contributors but if you want, you can find it here. And after that, we invite you to keep contributing. So hard fest, it was just an event but Jenkins project is open 24-7 any day, any time of the week, we appreciate your contributors. We have documentation which describes how to contribute. For example, if you want to code, if you want to help with documentation on piece design, we have some stories for you. If you want to help using infrastructure and other things, we also have some documentation. So we will appreciate any kind of your contributions to the project and we invite you to keep contributing to the Jenkins project type of event. There are some programs happening now. For example, there is a Google season of dogs for those who are interested in documentation and there will be other events for hackers, for example, October 1st and October and maybe organize more events. But if you see an issue in Jenkins which impacts your user experience, if you want to contribute to fixing that, not by writing code, but just helping to plan this issue, helping to find proper solutions or to facilitate contributions to this event, we will appreciate that. And if you need any help, if you cannot find a way to contribute, there are two channels. One is from newcomer contributors, another one for advocacy and outreach team. So if you have any idea how we could improve Jenkins as a project, we will appreciate your contribution even if it's not a code one. And we will be happy to help to make it happen and to find the proper venue to discuss this change and to make it deliver. So, and that's all for me, for me. Again, thanks to everybody who contributed to the Jenkins project. Thanks to all the first contributors and thanks to all thousands of contributors who work on the Jenkins project during the EM. So for example, last year we have got 5,500 contributors and this number keeps rising. So thanks to everyone who helps to implement these features, review features, deliver them and the same information so that we can help users to use all these new features we deliver in the project. Thanks all. Okay, are there any questions? Okay, are there any feedback or comments? We can discuss them. Sumit just posted, thank you very much to the organizers and reviewers saying it was an amazing experience. And I agree it was a, that was quite a treat to work with people across so many places in so many ways has been just a lot of fun. Yeah, and for us, so this fun doesn't end because we still need to review all these pull requests. We have a bell clock, we've managed many pull requests that you think hard pressed and if your pull request didn't get managed please stay patient and you will definitely get to that. So we track all the feature pull requests or the documentation pull requests whether it's change to your own like insights. So we will do our best to help them to get rendered. I was truly impressed and number of the new contributors chose issues that I thought and actually had described was, hey, this is a more challenging topic. They picked them and they started working on them and they made great progress. It was, it was quite surprising to me. I thought, oh, this is going to be a very hard issue. No way will we get progress on this during the hack fist. And I was wrong. We got really interesting progress on some what we're challenging and daunting issues not just the good for first time contributors impressive from both fronts. Yeah, so yeah, for example, there was some unexpected developments like dark theme. Yeah, dark theme is just a part of their story but real story that we completely reward Jenkins internals to make it happen. This help of multiple contributors and later it will help any thing developer whether it's a theme hosted on Jenkins CI or whether it's an internal theme you create for your company you will be able to benefit from this story. And there are already follow-up developments. So for example, team Jack on he started working on a better way to select themes and to get them adopted including user defined themes. So you as a Jenkins user would be able to choose themes without asking your admin to change the theme globally. There were some experience with marketplaces with discoverability of the plugins. So there is a lot of stories which will still happen or have already started happening. Also, yeah, we didn't talk about pipeline as Yamal which was one of the major points of feedback but again, there are some changes happening there. So, and we will definitely get there. So now one of the questions is can the timings in the meetup be shared in IST and I'm not sure what that means. Oleg, do you have a guess on what that's saying? I guess I esteem in Indian standard time. So it's definitely something you could provide as a feedback in the feedback form. So yeah, we just shank everything in UTC. There are online time converters but we didn't use them on the website because for example, the limitations of platform. For example, if you go to online meetup it's even more challenging than just UTC because the meetup is located in London time which is UTC plus one at the moment and even people who are located in London are sometimes confused. So, but unfortunately, we cannot easily change it without changing the platform. At the same time, we could make it better on our side because there are services. So if you see things like that, please just share that in your feedback form. Okay. Any other comments, feedback, whatever about the event? Okay, if not, we will just process this recording for publish it online. And after that, we will start working with other contributors synchronously to get more information and to publish summaries. I have already started working on a blog post for your improvements. I guess Mark has already started working on a blog post for documentation. As always, it will take a while but we'll do that and stay tuned. We'll publish that. Thank you very much Oleg. Excellent, excellent work organizing and what a pleasure it's been to work. You've been great. Thank you, thank you. The community thanks you and I thank you personally. Thanks very much. Thanks for the feedback but yeah, I wouldn't be able to do that alone. There are so many people who are hoping to organize the things including planning for the stories, documentation, et cetera. So yeah, okay. Any feedback before we stop the recording? Yes, just wanted to, this is what just wanted to thank you again, Oleg and Mark for organizing this in perfect manner, I guess. And so allowing everybody, including newcomers to contribute in any possible way to this event. It was nicely organized and I hope that you will have a very good results for everybody. Just on a quick note and this is, I guess, more related to Mark, our results of this hackfest going to be somehow considered for Google Season of Docs applications or it's separately. So if I understand Google Season of Docs correctly, one of the ways that they assess participation is participation in things like this. So my expectation is that this would be, contributions to this would be considered valuable and viewed positively as part of the evaluation process for Google Season of Docs. Now, Oleg's got more experience in this field than I do, Oleg, your comments. Yeah, you're to the right. Moreover, we referenced this hackfest as one of potential ways to get started with contributing to documentation. So, yeah, we will take revisions into account and it's already a way to do some community bonding. There are a lot of discussions about the documentation and yeah, I think we can keep working on that. Thank you very much again for organizing this. Yeah, thank you. So, if I recall correctly, the application phase for Google Season of Docs starts in two weeks on June 13th, right? So, yeah, I think we have to actually read. Okay, yeah, I think you're right that we're not there yet but it's coming soon. And yeah, June 8th and the conclusion is July 8th if I remember correctly. So yeah, if anyone is interested to contribute to documentation and to spend a bit more time with the Jenkins project working on documentation, you're welcome to join the Google Season of Docs program. And we will see what will be the number of contributors supplying because yeah, Google Season of Docs has limited number of slots but we still have other options like community bridge, like maybe hosting another program. So, if you're interested in documentation and the Jenkins project, please contact us and let's see what we can do there. Okay, any other comments or questions? Thanks to everyone for joining this call and thanks to everyone for participating in the event. So, there is a question about how can I contribute to documentation. Mark, would you like to speak about that? I think I may have frozen. Oleg, can you still hear me? Yes, I can, but yeah, you definitely froze. Okay, so the documentation contributions are welcomed and encouraged. You can go to Jenkins.io and you can see on the contribute page, on the participate page, there's a documentation link. There it gives a number of places and ways that you could help documentation. And they include things like revisions to existing pages, migration of Wiki pages, converting plugins from using Wiki to using GitHub as their documentation source, all sorts of different ways that you can contribute to documentation. Yeah, and basically we will welcome any kind of contribution if you're active user of Jenkins. Just I think what is missing in the documentation, try to improve that. If you're looking for something new, newcomer stories, in a way, you can basically find different tickets and I guess we still need to put the link to Jenkins.io here, but I mean, to GitHub issues, but in general you can find all the information here. Right, and we'll be creating, I expect to create several new first time issues this week because the good first issues process and the GitHub issues has worked so well that I'll create some more this week based on the triage work from the Wiki transformation. Yeah. So thank you for this question. Okay, I'll probably stop the recording and see you again at Jenkins online meetups or at other events. So the next online meetup is scheduled to Thursday. It will be a story about the defined builds with captain and Jenkins. So if you're interested in clouding different environments, please feel free to join us. Thanks a lot, bye for now. Thanks a lot. Bye.