 Bye. Okay, goodbye. So again, thanks everyone who joined our sessions. I hope you liked the breakouts. I participated maybe in six breakout sessions. All of them were awesome. There's a lot of discussions. We will have a closing session with some follow-ups. But before that, the idea was to have a session of Ignite Talks. And the idea for these Ignite Talks is actually to just again share any kind of experiences and chat a lot. So have you already seen the Agenda for Ignite Talks? Okay, then I'll screen share. Just a second. I need to close a few tops so that I see something in my tops. Okay, so we are recording anyway, right? So I'm sharing my screen. Do you see it? So before we start, one of the things I want to say that you have a feedback form. So if you haven't seen the link yet, again, kind of reminder, feedback is welcome. And yeah, this time call these sponsors t-shirts. So if you want a special t-shirt like that, you can just submit feedback and that's all you need to do. And yeah, let's continue with actually Ignite Talks. So what we have on the list. So the current idea that we will basically go through the list. And if you have some ideas, then please just put them in the bottom of the list. So we will be continuing them until we either run out of time or out of sessions. And yeah, what we have next, first, a Twitter as code application for life data science with onus, hash sheet, get credentials, this hash sheet here. Yes. Then we have a session about the inclusive naming. Angelika is not here, but I will briefly pitch it. So it's the topic we are unable to do, then celebrating attributions and highlighting contributors and launching Jenkins Francophone. Again, if you just have time, because why not? Okay. And again, if you have ideas, just put them here. So this one is rather fun event that's something. So I will use it only if nobody wants to present anything more useful. So first of all, Twitter as code. Who did participate in our session yesterday? We were doing a bunch of feedback together with Mark. Did everyone participate? Okay. Do you like memes and joke? So good news that if you like them, we have a special Twitter account for you now. This Twitter account is called Memkins. It was created a while ago. And what we have here, yeah, nice logo, of course, inspired by Miminatus. And well, when it finally loads because I'm not sure what happens, you will see a lot of images. Okay. Yeah. So something like that. Some memes are related to Jenkins. Some are not. Here's, for example, our slide from our presentation with Mark because why not? Is there something about memes? And yeah, like that. And for example, yesterday, when I was doing a Twitter, I posted this tweet. And actually what I wanted to show you is, of course, not a memes channel, but how it actually works under the hood, because it's actually Twitter as code, at least for some posts. So there is a repository called Jenkins and Miminatus. So Memkins. And this is a repository actually powered by GitHub actions. And this repository uses Twitter together. So it's a standard GitHub action created for posting Twitter. It was created by one of GitHub. So GitHub employees, it works pretty well. And I was experimenting. We started making all Jenkins Twitter accounts managed by code. And I still intend to do that, but I needed playground, hence Memkins. And yeah, so if you're interested how it looks like, so there is some pull request template, et cetera. And there is also a pipeline, which basically does two things. Just it allows doing previews when you create pull requests. And secondly, it allows tweeting when you actually do something more useful. And you can see that it accesses Twitter as up. So you need to register it, but after that, you can use it as an action. And here, for example, well, basically, it's all we have in this repository. And this is tweets. So this, for example, what I created last time. Hello, Walter, memes are coming. And yeah, just a link to the repository. So there are some limitations right now. It supports only open graph. You can embed images, which is a kind of fatal flows for Memkins. So I wanted to actually combine it with there is another tool, which can generate memes from some text and images. So I wanted to create a GitHub action for them and create a chain. So we define mems code and then it generates image and post the image. But I haven't got to that yet. So maybe it will be a topic for my break in the coming weeks because I'm taking a break from the Jenkins community and I will definitely do something awkward like that. But yeah, let's see. So let's actually see how it works in practice. Does anyone want to post something? Okay, so how it works. You as contributors, we can create new file. Actually, it's not May anymore. It's June. And for example, here, what we could do with memes, etc. I'm not sure. Okay. Okay, so you need to tweet. Sorry? We should probably do a meme about Zoom bombing. So how we can do that? Zoom bombing? Yeah. So what I would be looking for is that basically any article which has embedded an open graph, so something like that. Okay, let's try. So we have an article from New York Times and I wanted to do something weird because that's why we have Slug because Slug resolves open graphs. So how I usually test it, something like that. Zoom bombing. Well, actually, they are boring. So register. So if you want something on, okay. So I assume that the register has a cool open graph as usual, right? Zoom bombing attacks Texas. Sounds fun, right? What could pose another fun, right? You had one job, the register. Okay. So yeah, I think that let's stop. Thank you. Okay. I can just delete it in the worst case, right? So let's take this, the register. Let's take the boring one, right? And yeah, where we have, so we put the link and what's the detail? Zoom bombing on the video. Confidence is wrong. Okay. So, okay. With these Ignite talks, we will definitely use all the time, right? Well, Jenkins contributor summit goes wrong. So, and then we create a request because we'll test preview. I think it's about the name, right? So we create the repository. Currently, I believe it has code owners configured or maybe not. I believe that at least I was intended to configure them. Let's see. No, I don't. So if you want to join Memkins copy editors, please let me know. So here what you can see that we have tweet and you can see that there is a bunch of things triggering and there is preview. It took just one second because everything is quite well. And here's preview, but it doesn't actually embed open trust. So it's not really helpful anyway for this particular use case. Anyway, yeah. So let's assume that somebody reviews it and then we just posted and you see that branch was automatically deleted, et cetera. And then what do we get here? It takes some time because after the merge, what happens? Actually, there is another GitHub action being triggered. It takes a bit longer because it actually needs to connect to Twitter API. So I was a bit optimistic. And here you can see that the results actually feedback that it was tweeted. So it even puts the status on the text and you just go to the hyperlink. And so, well, yeah, assuming that you have open graphs, it's nice and we can automate that. But I think that would be a good engine for things like release announcements, request announcements, because GitHub generates actions automatically now. Sorry, open graphs. So if you use GitHub, you can actually do a lot of cool stuff. Basically, we could automate the Jenkins releases, especially when GitHub supports open graph for releases. We could highlight key pull requests basically with zero effort. So let's say it is five likes, and we automatically generate a pull request for Jenkins releases or for Jenkins CI, which highlights this tweet, sorry, pull request. And then we just review it, maybe edit some text and push that. So we can leverage this Twitter as code for a lot of content. We can, for example, automate the tweeting from community Jenkins.io by putting triggers, we could automate tweeting releases of Jenkins plugins in our pipelines. So as an engine, Twitter as code is very promising. And I think that we should actually keep exploring that. And the new accounts I will be creating, for example, for French speaking community, I will be connecting them to Twitter as code right away. And looking for contributors, which is more difficult than automating, as you know, what I will be doing it as well. So, yeah, it wasn't exactly that talk, but I hope you enjoyed that. And you're welcome to try it out. So it's all open source. That was a live demo that you actually made an entertaining post from. That's no joke. That's not the easiest task, all right. Well, I find the meme just like, got it? Yeah, it was completely unprepared. Stay tuned for my last live demo when I will be creating a tweet in French and prepared. This is worse. Okay, so what's next in the agenda? Next in the agenda is actually application for live and data science. So I guess it's a nice continuation of the memkins. And yeah, so the honest to the floor is yours. As they say, I have some pretty big shoes to fit after the memkin's presentation. So thank you again for this. There are a few slides, but most of them are in the reference section. So I think I'm going to probably go pretty quickly through this. So let me share my screen here with you and we'll post this later as well. So we're going to hear a little bit about a different application of Jenkins. I also spoke of this earlier in the user feedback session by way of introduction. I'm a life science research scientist and software engineer. I have been an open source advocate and contributed for many years. I have got graduate classes in group reprogramming, occasionally doing some blogging in these days, a lot of gardening in the backyard. Just to frame things, in 2017 we published actually an article in the scientific literature with the opening title of Jenkins CI. And most likely people that were reading these had no idea what Jenkins CI was, but we continued with an open source continuous integration system as a scientific data and image processing platform. And I think this is a kind of use of Jenkins. The reason for this is that if you look at the basic cycle of software publishing steps, they very closely resemble those of typical scientific data, processing and analysis. And Jenkins has essentially all of the tooling that's required to be able to do the same kind of steps in analytical and life science space. So the key enablers for these is, at least from my point of view, the accessibility that Jenkins provides to these tools through its web portal. We use primarily the freestyle parameterized jobs. It's a rather easy deployment. Of course, it is a super rich plugin ecosystem, groovy scripting. It's really cool and powerful for bluing things together in a heterogeneous environment. And I don't want to read the entire list, but there is certainly great OS community support. And that was key for me because this was my first entry into the open source community. And I found it very welcoming and very supporting, both with the Jenkins community as well as with the bio uno community, which was lining very well with the goals I was trying to achieve. So within this context, Jenkins provides some really significant benefits for life science, data management, processing and control as well as for data science for all kinds of data analysis. And the environment in the life sciences laboratory is quite complex and it is actually a big data science lab these days where the labs generate huge amounts of data and they need to be transformed parts and then analyzed. So there's a huge number of utilities, applications, custom scripts and instrument specific software that you need to sort of bring together to work towards this final goal. So as an integration platform, Jenkins is very, very successful. And you can create this one page web applications really cheaply. Reproducibility and data provenance are key in the life sciences and research space in general and Jenkins offers both of those. And data management as well as sharing and collaboration become really powerful within the context of Jenkins. So all of these things are things that we propose in the paper we published. And actually there's two manuscripts now about Jenkins in the scientific literature. You're going to find the second one in the section for the references. So I don't think we went through the I don't know why we jumped to slide seven. So we did this. So here is the original application that we had published about Jenkins and that was high performance image processing. We have many automated microscopes that are used in the discovery of new drugs that they take thousands and thousands of images that need to be processed and analyzed. So for the first time, lab scientists were able to use some of the Jenkins workflows that we built to get access to the high performance clusters that we had process these images and be able to analyze them themselves. While in the past, it would take weeks and weeks for people to wait for some software engineer to cue their images on the cluster and run the image analysis software to do. So right now we'll provide them with a very simple dashboard where they can go and do a bunch of analysis and management task on the cluster through Jenkins. Another application is for data management and Jenkins is really, really cool and powerful doing that. A lot of the data that's produced in the lab comes as delimited data that is very amenable to SQL querying and transformational of that stuff. And basically we have many jobs that deal with this kind of data and I will show you an example, but basically these jobs also use an embedded H2 Java database that sort of higher apps on demand does the analysis and then dies as the build finishes. So they can use essentially Jenkins as a IDE to do SQL queries and then the results from these queries are saved and managed in Jenkins. Similarly, we have a lot of need for image and data annotation and review and I will show you a couple examples where we have integrated some of the build forms with JavaScript high resolution viewers that allow us to view images but also as well integrate a lot of interactive views reports and analysis into Jenkins. One of the key aspects of using Jenkins for life sciences and data science is the interactivity of the user interface with the data responding to changes in selections that the user is making and so on. And I know that this is not of a huge interest to the Jenkins community and it was totally lacking back in 2013 when I came in contact with the BIONO organization and I described what I needed and at that point my colleague Bruno Kinoshita who is in New Zealand now built this really cool Jenkins Active Choices plugin originally was distributed through BIONO now is from the Jenkins repository with over 24,000 installs and it provides really cool dynamic and cascading build parameters that use Groovy scripts and they also can return dynamic HTML so we can enrich the build forms with HTML. So I'm going to show you an example of what you can do with the Active Choices here we're using the Scribble plugin Groovy, the H2 embedded RD, BMS and JavaScript. So we're essentially a query for data in the H2 database by selecting the certain values that we want to search for in the data and here we have sort of the two query client terms and you can eat them and reset them and change them as you wish by and all of this is in the Jenkins build form, okay. So this was one example and here's a little bit a little bit more visually pleasing this is using an interactive viewer based on the OpenSea Dragon JavaScript this is called a deep zoom viewer and is used specifically for scientific images. This particular form integrates Scribbler, Groovy and images that are coming in from a so-called cantaloupe triple f image server where it's very powerful allows you to zoom and the images and as you will see in a second it allows us also to overlay images because that's important we have multi-channel images that need to be overlaid so we can see the same cell in two different channels so you can see the nuclei of the cells are blue the cytoplasm is green so all of that interaction happens in the Jenkins interface for the job we can adjust the opacity and everything else and do all those cool things basically using a couple Jenkins one games so that's it I just you know want to think about with people here both from my work interestingly enough as I said my boss is called Jeremy Jenkins and actually he has accepted the the Jenkins icon he uses quite a bit in his sort of way he needs to put his picture sometimes and of course you know the community here and by own organization and last summer we built this really cool machine learning plugin for Jenkins I've met many of you then again and at the end I have put a number of references that when I post a slide you can just go through them and see a few more cool things that we can do with Jenkins for data science so I'll be happy to have any any questions or any other things to discuss so how are you doing the graph rendering those those graphs are amazing are those j-graph what's what's at your what's at the core of that so there's a number of of things that we're using there's also a bio uno r plugin what I'm showing you right now actually is a bunch of pngs that were generated out of the r statistical language got it okay however the the things that were showing you earlier the dynamic images of the cells and so on those are based on these deep zoom javascript viewer called open c dragon I have some references to it um so we incorporate the javascript viewer and then the data is queried and prepared by the Jenkins queries and everything else to to come in and show it there so we we use the full strength of you know javascript or the you know python and r whatever is generating graphics yeah and and this particular plugin that I'm showing you here is called the summary plugin uh which creates um tab tables in um I mean tab sort of yeah tabular forms in the report stage of of Jenkins so you can get um this kind of view yeah despite we like a standard software developing team I can see the use case of such advanced parameterized Jenkins builds because usually we have some validation cycles like nightly weekly cycle but sometimes developers want to run something custom against their PRs to make sure everything is okay in the scope which we can't execute during procurement builds and we always got complaints that our jobs are not so parameters of our jobs aren't so intuitive so I think with these plugins we can maybe create some more intuitive interface maybe retrieve some parameters dynamically but uh does this can we use this in Jenkins pipeline or is it only in freestyle jobs so originally when we developed this and this was you know a lot of questions about whether you can use these um in Jenkins pipelines uh we said you cannot because essentially we're manipulating the the javas the um the the UI form elements trying to discover what these parameters were sending back but more recent releases of the active choice plugin do support now pipeline jobs so you you might take a look at that um because it's moving in that direction and I think also recently when Jenkins moved from the um what was it the the table forms to the divs we have also adopted these to to work with this in in in work so we're moving with the evolution of of Jenkins but as I said earlier um you know we're also worried a little bit about what we're doing here because a lot of the interactivity is because of inline javascript it's because of groovy execution within the delt form and we know that these things always kind of cause security issues and concerns okay thank you welcome Andrei okay thank you so we have a few more presentations so you can see that I already doing a really united talk quite literally about time out so without full automation of course and yeah just a reminder let's move on and thanks Errani it's a great presentation again yeah and I'm looking forward to publish and call this content okay so next uh hashita uh I already um yeah so hi all so the hi all so thanks for your presentation and uh you can uh just share your screen if you need it oh okay so so for for this talk after I just wanted to show a demo and just so so my project for the so I'm working on working with GSOC 2021 uh under the project named grid credentials binding so in this under this project we are trying to achieve good authentication in pipeline jobs so I've created a small demo it's not a big one but I think we can get an idea of what we are doing here so in this pipeline script we are using the credential binding plugin as a dependency to bind the grid specific environment variables such as get ask pass or get SSH to perform the authentication operations on the behalf of the user so they don't have to worry about any workarounds or any prompts that you might get when you perform the authentication on a command line or console so so as we can see that there are three in my four environment environment bindings that are being used to carry out this operation so the get ask pass is basically used for store for storing the path of the script that will be executed when uh it asks for the username password of the user to carry out the operation in this so in this example I am just making just making a clone of the repository of a private repository so I'm making the clone of this repository which is a private repository well this is also this binding is tested on a lot of os environments in windows in various Linux distributions such as sent os ubuntu open vsd and various architectures as well so the so the project for now I have shown the get username and password binding but there's also another binding called get ssh private key binding which will use for the ssh protocol authentication and that's all for the for the talk thanks nice quick introduction and yeah looking forward to see more at the next demos so in the beginning of july we'll have uh phase one demos hopefully and yeah I'm looking forward to your presentations by all the students okay does anyone want to show something we have uh several minutes left before before we need to start closing down I can show two really quick ignite talks and I would like to show them uh but yeah they're really quick I find with that yes okay so I just don't want to do demos all the time uh so if anyone wants else wants just go ahead so yeah the next topic is about inclusive name initiatives so it's not memcans it's serious uh so you know in Jenkins you invested a lot of time in cleaning up our technology and thanks a lot that don't work for doing the presentation today for you with details we also have this community Jenkins I will for discussion it's you'll end in page maybe integrate all the inclusive naming cleanup so we've replaced our g-ray issues and epics we aggregated everything here on basically discourse because it's easy to edit it's easy to collaborate and discuss and we will be putting all the links here and currently it's an official project in advocacy and outreach so I made a patch which basically made it explicit so we we agreed on that more than one year ago but yeah I've just edited and here are some links and you can see that there is a link referring to inclusive name initiative so this is what I was about talking about several our contributors including me, Angelik, Thierry Vasylenko, Karin Target and Karadolomar we joined this inclusive name initiative channels we contributed to some meetings so what is it it's global initiative which is focused on helping organizations not only open source but also private source so I thought to include in terminology and you can see that there are actually a multiple organization participating including the Linux foundation cloud native computing foundation that is our founding members so Pryan Khasharma and Steven Augustus are one of the founders of these initiatives CNCF also there are quite big companies and there are also related projects including for example by Kubernetes by Linux foundation networking and what I propose to either we as Jenkins and maybe as the continuous delivery foundation also join this initiative so we join as a related project so basically our name here refer maybe this advocacy on outreach link so that we highlight that PS Jenkins project that we are committed to cleaning up terminology because this is what we announced and for us there is no reason to not participate so yet it would be great to participate here also we agreed that we would be helping inclusive naming initiative is marketing so Alex Searle who posted on terminology updates on CNCF recently he would be also interviewing this inclusive naming initiative and we are helping by sharing our expertise so for example here they shared a tool for discovering mis-usages on screenshots embedded in the documentation so he created the tool for that fully localized and somewhere open source so we can with already and I think that for us it would be reasonable to not only join as a related project but actually try here participating organizations so it could be Jenkins or it could be the continuous delivery foundation or both and for us it would be free because we are non-profits open source and we can join for free for companies they currently discussing what would be the cost for participating so for example I also brought it up in my company that hey since we contribute a lot to terminology cleanup in Jenkins why don't we also join as a company and you can also offer it in your company see if you contribute but yeah for open source projects it's free and this is basically my proposal let's join I still want to put it on the developer manager please the official voting at one of the governance meetings but I think it's quite straightforward for us and it's definitely win-win situation for all participants so well why not and yeah they have a slack channel so yeah there is inclusive gaming somewhere just it's here and on this channel you can see that actually there are multiple work streams including community including marketing, language, setting standards, company outreach which is rather most communicating with OSPA etc but we participated there already there are regular meetings where we participated and we could again participate more highlighted the Jenkins project and basically work together on setting for example standards marketing and aligning to use other organizations. Questions, comments? I think it looks very promising that's great so so the the kinds of initiatives that are happening here they would they assist with phrasing things what sorts of things do you see us involved with? Obviously they are organizing quite big initiative in terms of cash so there is an ongoing proposal to ask premier members for example for $15,000 a year for membership etc and they plan to funnel the most of this money to marketing they are non-profit and what it means that they will be facilitating for example they plan a series of blogs about how open source projects and organizations create basically an environment and how they contribute to naming and clicking up so it's definitely something where we could contribute and since they have their marketing team they need content we can provide content and they can provide marketing for us by using our content and vice versa they could create a generic guidelines etc using their resources their outreach programs and we could consume these guidelines we could implement standards or we could just for example adopt some guidelines as JEPs currently Angelic is working on JEP for localizations and for NTS updates but in the future we could get these standards out of these working groups so for me it's clear win-win and it's totally non-commitment so why not just by saying that we join this initiative it will be also quantity marketing splash so why not yeah I think so we're going to do the work we are so why not why not announce it why not say so yeah I was gonna say we're already doing this this is an alignment with what we are doing and yeah okay so yeah and thanks all so I will bring up this topic in the developer list maybe use this recording to save time once it's ready and I think I can show the last really quick hopefully really quick it's both celebrating contributions and highlighting contributors would you like actually I wanted to showcase a few features of community Jenkins IO is this where we get to see showing off I like that that channel is that yes exactly okay so you already know the so community Jenkins IO is yeah this discourse which has a lot of phrases and a lot of opportunities for us and what you can see that here we so just a quick question are you thinking this is eventually going to replace the google groups some of them so currently we have so many google groups so many guitar channels so many other channels in there like rc etc and yes we want to consider some of these channels using this course so if you participate it in the opening session there is actually a slide about that this standard text kassidy mem about introducing the 15th standard so this is exactly what we are doing and we hope it works but yeah so we want to get rid of many other channels by using this channel not all of them so currently it's not on the table about for example moving open governance here but we want to do something maybe we will move some discussions etc and here we already for example moved announcements because it's easier apparently to write announcement here write a blog post much easier and there is also a question whether we want to automate that so from advocacy on our strength point it's quite handy and I think we should evolve that we could combine it with twitter as code there is linked in this code which is also possible but yeah today it's not about that today it's actually about highlighting what happens in the community again in a lightweight approach so without writing a blog post and ask a dog spending a lot of time so for example here team jack omp announced bloat in a button classic ui and yeah here's basically this post just one image some summary reference to the plugin and for example what I did I'll show you my linked in account hopefully no recruiters today but yeah let's see it's probably even more dangerous than the shopping for my youtube okay so yeah I'm looking for lotion but in jenki's ui and you can see this post so let's see what happened here this blog post just copy pasted text from team etc i injected one image almost 400 likes which is quite good for the channel twitter traction was also quite good and you just post a link which points you here and there is a place for discussion so now it's not only announcement but it's also embedded way here to actually discuss the content provide some feedback etc and this is showing off so there is topic and we've already we've got quite a lot of things and again the idea that you share whatever you want so for example yesterday I shared uh uh what what did I share roadmarks for open source projects is basically what we did with mark so it's basically again just some summary i leave our slide deck which is already public recording is coming soon but I've put some teaser slides here just as images again everything can be done in minutes and seconds because you can edit it and mark down and you can just control c control before images like on github you get a automatic resolution of these links so you don't even need to write mark down for that this course results automatically and then well there is a post there is one like from somebody but definitely discussion is missing so if you want to share feedback about this slide deck we will appreciate it because we spent a lot of time to prepare a lot of time yeah maybe two hours three but yeah so yeah and yeah this is one side it's basically when contributors make announcements again about anything so what you want to share for example Ionius wants to share his achievement he created a code pipeline levy wants to say that I created a new pipeline library uh limo wants to say that hey I created a new feature for the credit pipeline etc no blogs needed no nothing just write a post here and we will be able to connect to our social media engine and yeah once the traction grows we will get actually more things well it's something for the means so I won't open and yeah actually another set which I wanted to present it's quite opposite so you can highlight your contributions or achievements but you can also kind of highlight contributions of others and for that we actually discussed approaches and I created a praise topic so basically a place is a label you can create something like a separated post for example I created that this weekend to celebrate father's days for course a care some of you participated on twitter etc and again it's linked in this page so you can post like that again it depends on how much time you want to spend so on this post I spent maybe five or ten minutes because I held the links in place and the everything else is just brain dump and coffee paste from somewhere else so it's not like I spent one day to prepare that I spent one hour on the entire annals on all announcements and yeah for the the results thanks for my two contributors which is kind of suggestion to use a topic so that instead of creating new threads you can create a comment like that and another feature of discourse so that you can just put twitter so you put a link displace it and you can also search etc and I suggest that we spend a few minutes to actually say thanks this time it would be a more thinking because I did my homework and I want to send Olivier because you may not know Olivier much if you don't work on infrastructure but Olivier is a key contributor to the Jenkins project who does a lot and yeah I've written some text when I was thinking about this demo and I'm going to thank him just here so yeah you can see that you can write in markdown and html you can just basically control the html here from any blog post etc and it will render automatically so it's really handy because and everything is to be preview etc so like that if you want so again I just copy paste the text here's a typo okay so I send Olivier for living maintenance open source project moving Jenkins to Asia etc and Jenkins releasing projects supporting Jenkins governance at the CLA being an awesome team with anything else to mention before I post need to end this or end the sentence in the first line or like the end he has is missing a phrase I would just take off the last three words of the first sentence these ones you look at look at the last three words on that line okay oh okay and he has been a key Jenkins contributor ever since yes there you go so finally we do more community management again right that's nice and again you can also inject smiles if you want something like that again all images etc you can control c control v so it's quite handy as an editor and the gates it's not as code but if you want you can dump everything to mark down and if you have to visit or in this case ship it ship it and yeah thanks Olivier you can just like it and then what I can do I can actually for example go to Twitter and say something like again I'm not sure what exactly will be rendered here so let's actually see because I have no idea well in the worst case he will be embarrassed but I can well if you don't know how it will be rendered inject deep right it's gifts always render yeah it gives all this render so yeah yeah okay I like game of trance oh okay yes let's see the con probably Tracy sees that my sense that he said who knows not sure that's the is that the gift that you want it looks like he's kind of not so thankful oh okay we we definitely mean this sincerely not with any degree of okay yeah not any degree of game of trance right yeah actually how it renders so it renders not well because it just renders the heading so we definitely need to give applause applause one I was right yeah oh yeah what else do you have cats always work right yeah there you go okay okay there yeah yeah I put too many cats in my these days no such thing as too many cats okay so another more programming probably will lose a few followers but who knows okay feel free to retweet so yeah this was my talk about how to promote and yeah please use all channels show off your contributions because as Jenkins we would really appreciate your contributions and highlight them because we really need to highlight what happens in Jenkins and you can do it in minutes you don't need to write a huge ask you for Jenkins you can use this channel as a really lightweight option and I think that it will be a similar default way for us and Jenkins you will become more and more redundant I mean Jenkins your blog post but let's see so questions comments yeah I heard that this course has also live chat does it it's a discord I don't think that this course has live chats so discord is chat discourse is I know what is this and just I saw that these course maybe uh yeah I remember that also but so for chat it means that Gitter and IRC remains as it is yeah so we are not to do something significant but if maintainers want to close down for example Gitter and move to the discourse they are welcome to do so we do not talk maintenance and currently we have almost 100 Gitter channels for Jenkins TI many of these channels are not really active yeah 100 almost there are also mailing lists which are not really active so for example I can totally foresee that a focus in outreach mailing list will be replaced by discourse entirely because it's a bit of a place for open discussion the mailing list at least I think so and yeah the idea that we will be removing some of the channels but ultimately we won't be forcing anyone so as a maintainer you have full freedom to decide what you do and well for yes because I think consolidation here is really important because as like as a guy who seeks some answers I would go to the place that have most of community and I really like this course so the UI is really great as I'm more a reader than a writer it's really convenient for me to follow discourse topics yeah right so in our case we rather need by example this platform is currently Springview so you're welcome to contribute you are welcome to share your feedback so there is site feedback top category for that but yeah assumption that if it takes off if there are contributors so that it will eventually activate even more maintainers to migrate and yeah that's how the community works so right now I don't think that we would force anyone to migrate from any channel but if it plays out we will rather even buy consensus does it make sense yeah thank you okay so try it out and if you ship something you please show it off because I will be working on information for these things and I want content so that I can work on information okay so let's close down because we are going over time and we won't have much time for after party well we will have basically infinite after party anyway but I have a few closing slides before we move there so please just some patience there is there are not that many slides so first of all thanks to everyone who contributed and who stayed until the end yeah it was almost six hours by now and yeah it was quite a packed agenda so but I think that it worked pretty well because there were a lot of discussions we had a really active state of the union session and next time we should maybe make it even faster and user panel it was a great experiment and I believe that we should keep doing them thanks to mark for leading newcomer track mark could you share some expertise from this track how did you go I was delighted with it we had a relatively small group three presenters five six and seven participants and we talked about topics that were interesting to them thanks very much to them for being involved it was a great thing I think we're going to get some plugins adopted as a result and I know we're getting more help from some people who are wanting to be more involved yeah thanks a lot was this session a recorder for anyone that might need to go back it it was recorded yeah I've I've got the recording in my in my zoom channel in my zoom feed and I will upload it along with the other recordings from the from these I would have love to be to that so I'll probably follow it thank you great yeah currently we have a contributing to Jenkins playlist on Jenkins YouTube channel so you can find it there I won't spend time right now to find it but yeah I believe that mark will put the recordings there as well so that you can take a look and there are already a lot of recordings from previous sessions so thanks a lot for driving to mark also yeah I think that breakout sessions were pretty good I jumped into almost every session there were nice discussions there were some action items so for example for terminology update it was really nice discussion the github corrections was awesome yeah I'm just looking to repeating this Jenkins online meetup maybe with hundreds of participants cloud events integration was pretty good as well Jenkins but not the operator was good open telemetry again they had a great discussion between basically Jenkins and Jenkins X communities here so Vincent the heart joint shared experience with visualization jumping to limit and others so plug-in end of life policy that we even have a planner so last when I was living this session last time they were drawing a kind of decision three how we actually decide whether plug-in is inactive or not which is a quite challenging question so I'm looking forward to it being adopted as a kind of job because it was a struggle for us for a long time we made at least three attempts to standardize it and it was failed and yeah it's one of the ability Jenkins X and that I believe all of them were good discussions for Java 11 maybe James North summarize it because I failed to visit this session or James left oh Mike could you please summarize yeah maybe he's offline well or Oleg if you'd like I can give a brief summary oh yeah yeah just go ahead so Java 11 was discussed in depth looking at alternatives including hey should we drop support for Java 8 we were really grateful to have some some users attending with us Marcel and and Jonathan and it worked very very well for us to have those users there to assist and discuss outlined a rough plan that we think is appropriately conservative and looks still forward to the future it'll be coming as a Jenkins enhancement proposal and be discussed in the mailing list before that okay so goals of this session will be totally achieved well I would have liked I was certainly would have liked to have a final all sorts of things but we we really had a great conversation and good notes captured from it as what next steps are okay great so thanks to all participants of this session thanks to all hosts because yeah hopefully it helped us to push the projects forward the United talks and then was here it was just well again fun time and I hope it was also learning experience thanks to Hashi thanks to Eranias for great presentations yeah again Eranias I'm looking forward to see the full presentation maybe even a solutions page about Jenkins for data of science and life science because yeah I know that you've written a lot of blogs so maybe it's time to aggregate them and yeah for Hashi looking forward to JSOC demos and thanks a lot for working on your project and yeah currently we are closing down so we are going slightly over time but yes I believe that it's still using the reasonable limits so for feedback first of all we have discourse channel oh it works so Jenkins contributor summit feedback so if you want to discuss it in discourse here's a channel for you or sort of topic so just put your feedback here register it's just registration through github and then you can post a comment it takes a few seconds then slug everyone from this session is on slug so we will keep it open for a while we wanted to archive it maybe for one week or so so please drop any feedback there if you want and yeah t-shirts so if you want to get them there is a feedback form please fill it out it's actually not a huge deal so there is only one required question how was the event all the rest is optional but we will appreciate feedback and yeah if you reach the end spoiler for those who are here you can actually order a t-shirt so this feedback form is anonymous but the t-shirt feedback form is not anonymous because we ship in address and all other kinds of personal data so by filling it out you agree with us storing this personal data for sometime before at least send t-shirts and then we will delete it so we do not store this information we do not send spam etc and yeah again any feedback will be appreciated and as I said before we intend to do the next event in Asian and Pacific time zone so ready for the next summit there are three yes answers please choose one you prefer okay so yeah that's the plan and yeah thanks to cloudbiz for sponsoring t-shirts I believe there will be stickers and other things we using Jenkins is the way but yeah again if you want to contribute to art work for the next summit you're welcome to do so we will appreciate that okay so for moderators what's next so I can't ask you that if you let the sessions to take a look at the meeting notes etc write down action items decisions if you want you can write posts about that or for example a discourse post which is much easier yeah publish materials because many sessions had slides many sessions recorded we recorded so we kindly ask you to publish these materials and let us know because we will be able to again promote them if you've seen a uiux hackfest so many of you expected there I believe so there we just used a bit of repository we dropped all the content there so for example here presentations we had quite a lot of presentation and for example migrating plug-in docs just first random one so here you can find the guidance and the recording references etc so something like that and it's available as code if you want to mark down it's one of the ways another way just put them on discourse again with all the links as you prefer but we will appreciate if you could post these sessions and for recordings how to do that you can post them for example on your google drive make it public and then mark or maybe somebody else from youtube managers they will publish them process them and make them available to everyone and then we will be able to use our social media etc to promote events because we've had a lot of great demos we definitely should promote for example github actions the conversation was awesome ianis did great lemmas angelic batista for go up update etc etc so there is a lot of great content to share and why not and spread the word so whatever uh twitter link today in community jenki sayo it's much appreciated again jenki's community needs more contributors and needs more users and doing promotion is one of the ways to get that if it's related to particular decisions you can use special interest book mailing please the developer mailing please for example for jabs etc we still expected to happen in mailing please so for unformable discussions community jenki sayo is fine for formal decision making we kindly ask to use mailing please at the moment and external communities for example tectonium terribility cloud events open telemetry please use these external channels as well because again working together with other communities is our opportunity so why not jenkins shouldn't be just locked down in its own community that's why we start working with foundations talking to end users etc because we should be more open and i hope that we will make jenki so the great place to contribute for everyone even if you don't try to code and yeah as event officer i invite everyone to think about doing combined meetup especially for those who did user facing sessions or developer facing sessions because we do developer meetups well because jenks online meetup is another platform for us to promote events and if you have a talk why not presenting that okay and yeah also applied to one of the next conferences but yeah DevOps world call for papers is over maybe we'll have contributors summit there maybe we'll have something for users but it's to be determined so at the moment jenks online meetup is actually the best opportunity and yeah interesting part of the party so we had a lot of discussion on how do we do that we consider two services we put actual sponsors from work adventure but we were unable to set up that time but again thanks to water adventure for supporting us and we will definitely delete the platform so but today since we don't have much people anyway let's try out a rounder round leads a new service it's just a single contributor working on that but it's pretty cool it has no video but it has pretty good audio so i'll share the link so i think that i will stop sharing anyway because yeah i have a lot of stuff and yeah it's not interesting so we are going to rambler and you're welcome to join there if it doesn't work we can return back to zoom but yeah let's see everyone finally strength it out okay so yeah i'll post it so what about posting it in social media mark what do you think we may get a lot of random people well so is it that the link's not available because we could paste that link into the chat here yeah i'm posting it in the chat but yeah if you want to we can announce it in social media or maybe not yeah i was hesitant to risk the social media thing given our fun with with earlier then no social media and yeah so everyone is welcome to join me so i'm walking around and i'm hearing sound yeah i'm a bird a bird you mean uh the goose i i don't know oh look that there's a butterfly yeah there are some my easter eggs as well i've heard so you can i also see a butterfly but i don't see people or birds okay it's uh somewhere on the map yeah i just don't want to run into the cactus oh i see okay levi i see i see somebody else sorry i'm still choosing caviter it'll take me maybe then i have to party okay i seem to be stuck and i've got to find a way past these i do not want to be okay uh so yeah i'll probably stop uh mute myself here so is there anyone else oh so many people yeah i have to drop off wait wait wait all of this why i don't see anyone maybe you clicked the wrong link so you should uh click the link rum.lead Jenkins can contribute resummit yeah okay i will try to maybe as a someone being in rescue got sent to special domain domain i don't know i hope no yeah now i am a robot oh one of them one of us okay see you there no yes i still can't see other people okay let's follow up and chat if needed okay yes so see you there do you see anyone because i definitely see a lot of people okay so let's try it out okay i'll drop from zoom and try