 Hello, everyone. Welcome to Jenkins Online Meetup. Today we have a special session about the hardcover fest and we have two meetups. My name is Alekli Nachov and we also have Mark Wade on the call. So, both of us are long-term Jenkins contributors. We spend a lot of time contributing to Jenkins for our main plugins. Mark is famous for being the maintainer of Git plugin for the last 10 years or so. Thanks a lot for taking for that. Currently I'm in Jenkins for. I'm also part of the Jenkins ambassador. I work with the Jenkins Envoys and outreach specialist group which presents hardcover fest to you this year. Stay tuned for the presentations. So, yes, today we talk solely about hardcover fest. This is our second session. We had this session this morning where we had pretty much the same agenda, though we will have some differences. We will have a quick introduction to hardcover fest and we will talk about how to contribute to Jenkins, which project could you focus on, and then maintainers of future projects. We'll briefly talk about what you could do there. We have Uli Haffner and Kara Delamar on the call. So, I guess we will have presentations about Jenkins SACs and warnings in Git plugin, because me and Mark will probably do some extra presentations as well. If you have any questions, we just ask all speakers to make some pauses and ask whether there are any questions when you feel it's appropriate time. And if not, we will just ask you once we finish your talk. So, I guess everybody is familiar with hardcover fest. So, hardcover fest is a worldwide program. Each year in October, everybody is welcome to contribute to open source by submitting two requests. And this is a six-year hardcover fest. This year it's sponsored by Digital Ocean and Diff. Thanks a lot for hosting this event. Again, it's a six-year and last year was really big. So, there were almost 50,000 contributors and hopefully this year they will be approximately the same number. Hardcover fest includes both online events and local events. So, we have online events. You can just go to the hardcoverfestdigitalodge.com where there is a link where you can just sign up and start chatting. Basically, that's it. Though many communities like Jenkins we also organize additional online events and you can find more webinars happening around. If you're interested in something local, there is also events page and here you can find a quite long list of meetups happening during the hardcover fest. We have some Jenkins meetups there. So, there are only few of them there right now, but you will have more meetups. And you are more than welcome to join one of these meetups. Okay, back to my slide there. Okay, speaking of Jenkins, Jenkins project has increasingly participated in hardcover fest from very beginning because we were getting a lot of contributions since 2017. We run a hardcover fest as official program. So, it means that we prepare some documentation, we prepare new bear friendly issues. We facilitate hardcover fest in our community and this year we do it again. So, we welcome every contributor who is interested in Jenkins or every Jenkins user to start contributing and we are ready to that. We did some homework before the events started. So, if you navigate to Jenkins at your events hardcover fest page basically it's our pre-wending page for all hardcover fest matters. So, you can find all information and what we are presenting today is basically listed on this page. What we have for you? Firstly, we prepared a lot of issues across multiple organizations where you can find something to contribute to. For example, if you go to this filter, you can find the issues in GitHub. So, yeah, there are something like 60 issues there and we are creating more, but Jenkins is mostly based in Jenkins data and he can find much more issues just contributing to new bear friendly issues. Yeah, that is a little bit of a bit. So, you can find almost 200 issues there and using the hardcover fest we will make sure to replenish this list. So, if we start running out of issues, we sure we will create more ones. In the previous meetup Mark has presented a dashboard for new bear friendly issues. So, maybe Mark, you could do it now so that we don't lose the context. First things first, let me say something and then, yeah, I'll bring it. So, yeah, let me share mine and here it comes. Let's see, share. And here is this dashboard. You'll find the link to the dashboard in the slide deck. It's called friendly issues. On the left hand column, we find the component. So, core, the warnings next generation plug-in, web content, analysis model for warnings plug-in, platform label are my favorite. Remoting, one that Oleg's worked on for a long time, Markey Jackson's GitLab plug-in work. And then across the columns, the severity of the issue so that you can choose, hey, you want to work on something more severe. These are all newbie friendly, should all be ready for anyone to pick up and go to work on. Thanks, Oleg. Thank you too. Probably I'm the only one who is frightened about newbie friendly urgent issues. Yeah, I don't know how to, sometimes a critical issue being newbie friendly is a little surprising. I agree with you wholeheartedly and I am a little suspicious of those, but good to have somebody look at it. Right. So, thank you. Do you see my screen again? Yeah. So, in addition to newbie friendly issues, we also have a number of featured projects where you will get a warm welcome as a contributor, especially if you're a newcomer. So, the idea of these projects, that every project has contributors who are able to provide quick reviews, they have these contributing guidelines, they have newbie friendly issues. So, these projects are something we would suggest to start from, if you are just starting these Jenkins and you can find that there is a pretty diverse list. So, there is a website, there is a Jenkins code, there are several plugins. Also, there are tools like the Jenkins CLI tool, there is Jenkins software and other things. So, if you want to work on a code, there are some projects for you, if you want to work on documentation or just input design or draw something, we also have some featured projects. So, please feel free to choose something from this list and, yeah, later today we will have overview of some of these projects. Okay. Yeah, probably I shouldn't even switch to the presentation mode. Okay. Regarding Jenkins meetups, as I said, we have quite a number of meetups, not all of them have been already published on the hardware test site because it takes a while. You can find this information just by going to Jenkins landing page. So, Jenkins IO, if you scroll down, you can see that there is a number of events. So, if you want to see them more friendly way, there is this page upcoming events and a fun part about this page is that it has been already improved in the hardware test on the very first day because before that, the layout was perfect. So, here you can find incoming meetups and events and hopefully we will have more. If you are a meetup organizer, we also invite you to schedule events for that we have event kit available. So, if somebody just wants to organize Jenkins meetup, you can go to this page, hardware slash event kit. So, we have some slide decks, including the one we presented today with Mark. We have a few extra slide decks. We have some sample agendas. We have references to meetups you wish you can copy. So, basically, organizing a hardware first event is just a matter of your time and we are ready to support you. So, if you have any questions, we could do so. Obviously, hiking something together on site is quite interesting and it's a very nice experience in hardware first. So, last year I participated maybe in six meetups in total. Jenkins once, non Jenkins once and it was really fun. Speaking of fun, it's not only about the condition but we also can get some cool swag this year. So, hardware first organizers, sponsors, stickers and t-shirts. So, a few tens, thousands will get these prizes if you submit in time. To get a t-shirt, you need to submit four cool requests, which is quite easier and we encourage you to do so. From the Jenkins site, we hope to have some stickers. We will definitely serve them at on-site events. For online events, we are organizing it. And by the budget, we will have that. Also, thanks to CloudBeans, we have got sponsorship for DevOps for Jenkins for Brisbane tickets. So, we will have discounts for all contributors and we will also have free tickets for top contributors. So, stay tuned for that. Thanks a lot. Okay, this was my quick introduction. The question is actually what you can start doing now. And actually, you can start hiking right away. What you need to do is to go to the Hottoberfest website, sign up. It's just one form where you'll provide a GitHub account. That's it. Then, if you're interested in Jenkins specificity, you can join our Gitter channel. And after that, you can start submitting cool requests. You can find all the information on the Hottoberfest page if referenced. Basically, it's a quick start. One thing we asked you to do is to actually mark... Okay, I'll get to it. So, one thing I wanted to mention is that actually any pull request counts, so size doesn't really matter. If you find a type, please feel free to do that. If you want to contribute something to share your experience in a blog post or improve solution pages, it's something we really appreciate. And since everything is as code now, in Jenkins repositories, you can find pretty much everything. And every pull request will count towards Hottoberfest. So, even if you improve demo files or whatever, it's also a pull request which matters. What we asked you to do is to actually mark a pull request. One of the issues in the Hottoberfest this year that we as an organization have no opportunity to track contributors. And again, to find short recipients and to find pull requests to highlight, we would really appreciate to have some markers for us. The easiest way is to just mark a pull request as Hottoberfest in a pull request. So, something like presented here. And after that, somebody of the Hottoberfest team will update it and put the Hottoberfest label, which we will use for internal methods. If you are maintenance of the repository or if you have right permissions, you can just put the label right away and it's enough for us. Okay, there are a few useful links. So, I presented the first few ones. The results are FAQ. If you just have any questions, there is additional link page for all contributions to the Jenkins site. It's Jenkins.io slash participate. So, here you can find information about various kinds of contributions for Hottoberfest. We'd rather talk about this side of contributions because they end up with a pull request. And here you can find things. For example, if you want to write code, you can go here and you can discover a pretty terrible page because it's still work in progress. But good news, again, we have a pull request for Hottoberfest which improves this page. And if people review that, we will have it landed in 30 minutes or so. So, yeah, you can find all the information there and we will keep improving this page because basically I made it as one of the projects for Hottoberfest for myself. And everybody else is also welcome to contribute. Okay. So, regarding other useful links, all these links have a lot of different crosslinks. So, basically, it's like Wikipedia. You can read it from one page to another if you have a lot of time. If you have any questions about Hottoberfest, you have GitHub channel, it's Jenkins.io slash Hottoberfest. Use this channel if you have any question or if you need any assistance or if you feel that your pull request is stuck. And we have two GitHub organizations. One is on Jenkins.io organization and another one on Jenkins.io. So, if you're a member of these organizations, feel free to just ping us if something is new. Okay. That's it from me. And basically, you can start hacking. And if you still want to watch and how to hack, we have an next presentation from Mark Wait. Okay. So, are there any questions before we switch? Okay. Then thanks, Saul. And now presentation by Mark. Thanks, Saul. Thanks very much. Yeah. So, I want to talk about how you can contribute and give you some ideas of creative ways. So, first crucial point, choose things that interest you. What is it that's interesting to you about the Jenkins project? We've got space for programming language work, for test harness work. If you're interested in hardware or documentation or software in one area or another, if you're passionate about written language or spoken language, we've got spaces for you. You'll succeed better if you choose something that you use. It matters more to you typically. So, if you're using organization folders or if you're involved with the warning, if you use the warnings plug-in, if you use a freestyle job or a pipeline job, if you're a Jenkins core user, those are all places that can use your help. Use something that you use and hint something that you use. Where can you help? Code, documentation, tests, outreach, translations, even user questions. Any pull request counts. Just to reiterate what Oleg said, size does not matter on this case. It's just welcome to you. We love to have your contributions. So, you want to code? Java is everywhere in the infrastructure. It's in all sorts of interesting places that you can use Jenkins core. Configuration is code plug-in. We've got a whole bunch of featured projects that will let you work Java. We have an invitation and a whole bunch of good issues that you can use to work on Jenkins core in Java. If you say, oh, I'm not a Java developer. Okay, plug-ins are Java as well with their editions. Then you could say, nope, let's do JavaScript. Okay, we've got several really important plug-ins that have a significant component of JavaScript. In addition, the website for managing plug-ins is JavaScript. We'd love to have contributions and help in any of those areas if you're a JavaScript developer. If you're interested in Golang, we've got an entire project, Jenkins X, which is based in Golang. Also, we've got a Jenkins command line interface implementation now that is Gol-based from Rick, one of our colleagues in China. So if you're interested in Gol as a language, here's your chance to contribute. We've got other languages involved in the infrastructure, plenty of places and things where you can help, and Hacktoberfest can help you get started. Maybe you want to write. You say, I'm not interested in coding. I want to write instead. Well, all of our documentation is checked in. You can also do blog posts by submitting a pull request, user documentation, developer documentation, translations into native language, all available. You can submit to all of them as code. For user documentation, we have all sorts of different places here, tutorials. They're specific to particular platforms like Android or Docker base. We've got the user handbook. We've got all sorts of things that you can help just by getting started there. If you've got more interested in development, the developer documentation needs even more work than the user documentation. There are so many places that could be benefited by your help. How do you deal with tutorials? How do you get started all ready to go here? If you're a native language speaker, any plugin or Jenkins core typically has internationalization support in it, and you could internationalize that piece of that. There's also on the Chinese side, a Chinese localization sig that is doing a massive effort to localize Jenkins into Chinese. Maybe you're a tester. I'm personally biased towards tests, and there are lots of things that we could use in Jenkins testing. You could submit automated tests to help. You could assist with interactive testing every three months. We release a long-term support release, and that long-term support release needs testing for about the two weeks prior. Unit testing, integration testing, acceptance testing, already if you're interested in tests. Likewise for plugins, plugin authors love to receive submissions of automated tests. It's a great way to endear yourself to a plugin maintainer. Hey, here's a test, and it's just a test to check that stuff's working still. Maybe you're a graphic artist. We need art and design. You'll see here on the right that some examples of Jenkins area meetup artwork that the meetups have loved having as a way to highlight their unique differences, their unique contributions. On the right, we've got an image from the Belgian Jenkins area meetup. Another one from Austin, one from Spain, all part of creating artwork. We'd love to have your help, and we're delighted to have you help us during the month of October and beyond. Oleg, they covered the piece that I wanted to say. Thank you. Does anyone have any questions to mark? Well, it looks like not. So maybe we could start from doing some future projects over views. So, yeah, I could try doing Jenkins website over here again. So, yeah, on the morning, we were doing this overview, but unfortunately it didn't work well because probably there was too much traffic from photographer participants, so the site wasn't really working well. But now it should be fine. Okay, do you see my screen? We do. Okay, so let's go to Jenkins. So, yeah, we just do quick introductions of these future projects, and one of the topics website. So basically it's our landing page for everything. It includes information, it includes a lot of posts, it includes the user and developer documentation. And you invite everybody to contribute to this site. So if you want to create your own blog post, it's something which you can do easily and same for events. In order to contribute, we have a special page. It's Jenkins.io slash, yeah, this one. We're doing guidelines. So in this guidance, we basically have recommendations for common pieces, and you can start from this page if you want to contribute something big. If you want to contribute something small, it's even easier. So for example, we can take whatever on the page. Okay, let's take the Google Summer of Code. So here we have a special interest group page, and if you want to improve something, if you see a typo or if you just want to get some context, in the bottom of every Jenkins website page, there is improved this page button. You can click on that. And then you get to GitHub automatically. You just need to have a GitHub account. And here you can basically edit this page. You can preview this page using GitHub features, and you can submit a pull request using GitHub features. So you don't really need to call the repository or to check out something properly if you want to do small changes. For bigger changes, there are guidelines here that basically allow build files standardized. Just by running a simple make, you can get everything from it. It's a bit more complicated for Windows users, but if you need any help with it, just let me know. I have given that somewhere. Okay, so regarding the website, it's not on the front end. It's not on the ASCII doc. We also have engine under the hood. This engine is basically based on our struct. So this is a combination of Ruby and Hummel. So if you are Ruby fun, if you want to create something complex, because many outpages are automatically generated with some standard logic. And we have to use various metadata in order to generate pages. You can contribute to this logic. For example, for blog posts. So if you can just open this blog post, you can see that there are some metadata for authors, et cetera. And if you see how you could improve that, for example, doing something to automate meter content or just things like that, feel free to do that. Any questions about the website? So just to provide some tips about the documentation. So if you go here, there are some things like pipeline documentation and other needs, which are known to be painful for many users. So if you have any ideas how to improve this documentation, it will be really, really appreciated. And now on the Jenkins website, we actually have feedback. And the feedback gets captured to a spreadsheet that can be referenced. Notice, Oleg at the bottom there, was this page helpful? When you click that, it opens up a dialogue box, which you could check yes or no, and then give your feedback. Please no foul words, no harsh comments. Yes, I know that the Git plugins page is the most hated page of any of the pages in this set. We're working on it. Okay. And so, yeah, I will do an improvement of what you need to see. Okay. So if there is no questions about Jenkins, I hope we could proceed with something else. For example, we could take a look at Jenkins X. Great. Shall I share my page then? Yeah, it would be. Yeah. So Jenkins X is an open source opinionated way to do CI CD on Kubernetes. So it imagines CI CD and it provides a way to CI CD in a very cloud native way. It's written as Oleg said before, it's written mostly in Go. In fact, 98% of it is written in Go. So it's a good project if you want to practice your Go lang. We have this little blog post on our... Can you see my screen? Can you see the blog post? Yes, I can. We have this blog post outlining just the basics of how to engage what we're looking for and how to join our community. So you'll inevitably run into questions and we have Slack channels, which are part of the Kubernetes Slack. So you join the Kubernetes Slack and then join us on Jenkins X dev or Jenkins X user. And then those are very active channels any questions you have will be responded to right away. We also have office hours where you can ask questions and actually our office hours for this week start in one half an hour. So if you just want to go from meeting to meeting you're welcome to. And there's a link for the zoom forward on this page as well. But our main documentation site is Jenkins X IO and that will show you under the blog the page I just showing, but also it gives you documentation on how to start engaging with the project. So if we go to here and we go to contribute to the project you can contribute either to the code or contribute to the documentation and when you click here you'll see in I can't see it anymore but here you'll see the edit this page button and similar to the Jenkins website this will bring you directly into a GitHub page and you can edit it directly here if you have a GitHub account but in addition we have information on how getting started if you want to fork and clone the project run it and build it locally and then make a PR so that would be very good for contributing to the documentation if you want to do more fixes than are just on one page. We also have documentation around contributing to the code so that'll get you set up on sort of engaging with the source code of Jenkins X and for the source code of Jenkins X our Jenkins X slash JX is the readbook for that and we have a number of issues that we've already tagged Hacktoberfest or Good First Issue often both at the same time and that's a good way to kind of get started and start engaging with that code base but do feel free to ask any questions you have as you begin to poke at the code base and look into the various issues on our Slack channels. That was very fast run through does anyone have any questions for me? Actually I saw a poll request coming from me for a spelling error so that's great, thanks Kara. Well done, thanks Mark. Yes, actually the doc site is new, we've revamped it so there will be things like spelling errors which probably were there before but in addition to that because the architecture of the site is different a number of our links are the old links and therefore are broken so this is like a really nice little fast Easter egg kind of way to get some PRs in yeah, you're welcome to fix those and that makes it's a valuable contribution and we appreciate it and it will definitely get you your four PRs for Hacktoberfest quite quickly. We have recently added link validation to Jenkins IOP called the Quest Builder so if somebody wants to implement this for Jenkins IOP it's still free to take a look at the code and maybe copy that in our case it's a Jenkins file and likely you'll need to migrate to Jenkins X pipelines so yeah, probably it's a good case study. Great, any other questions? So yeah, thanks a lot for the presentation Kara. My pleasure, thank you for letting me speak. So who does want to go next? I think we should invite Uli next. I want to hear more about WarningsNG. Yeah okay, then I will step in again and I hope I don't forget anything if you have the same talk twice. So I will share my screen as well and Kara I think you may have to surrender the share so you may have to click the stop share. Yeah, I was looking for the button right now. Thanks. I still can't share mine. Okay I found the button. Okay I have it now. Okay, so the warnings plugin is one of one thousand Jenkins plugins so I present a little bit about the plugin but not very much so if you have questions we can focus on them later on maybe. So the plugin basically shows those warnings and you're from static analysis tools or from your compiler in several screens and so these screens can improved with pull requests for the hackathon and so for instance we have charts which are shown which show the number of warnings over a lot of builds for example or what be most important. I can also see the details of these warnings for instance you see here we have two warnings for Java to 12 from Maven and so on so one thing you can help in my plugin is to add some new parsers for instance or to improve existing parsers so there is a lot of work to do on the model side if you are familiar with Java and so on what is also very helpful if we have some people helping with the user interface sorry I need to go to a different one when you would like when you want to to jump into the details for instance for instance we can jump to the PMD warnings there are a lot of warnings and you can help to improve the tables which are here so here we have a lot of feature requests from people small changes they are either on the UI side where we have some JavaScript or CSS so one thing what would be helpful if you even you can't program JavaScript or you can't program in Java it would be helpful if we have someone with CSS know how who can provide different views for different resolutions for instance if I reduce the screen resolution of the screen the layout will change and we can provide different views for different resolutions for instance maybe you can even watch it on the handy if you like so this is one of the things you can help if you need more documentation about the plugin there is in GitHub is just for me okay in GitHub if you have the documentation then you can jump in to see what's going on and what you want to help or you just go to the GitHub channel of the ones plugin then I can help you with some of these issues Mark already showed the issues of the Jenkins project so in my plugin there are several different issues available you can simply write unit tests you can provide these feature requests or localization for instance currently everything is just in English but it would be helpful to have UI localized to different languages as well well yeah I think that's all I can say so switch back to one question are there any static analysis tools which need integration where there is high demand to get them integrated you are muted sorry again you too sorry which one so for warnings and gplugging are there any static analysis tool integrations which I'm missing now and which would benefit from contributors I'm not sure if I have a question sorry sorry Ulia I think you are wondering if there are additional static analysis tools that you would like to integrate that are not in integrated what I've seen in warnings and gplugging was every tool I'd ever considered seemed to be integrated but I think it's a good question are there tools that you're missing I'd love to have this tool integrated and it's not actually I in Java and for Java everything is supported but several people come on come and pull an issue and said yeah maybe this tool would be nice to be supported but this is something which is typically provided by the people who use these tools by themselves so they typically need just a small class to add an additional tool and then it works out of the box in my plugin so it's really easy to support a new tool it's just some additional work to do thank you are there any other questions to Ulia okay thank you okay so we have a few topics on the list so I think we could talk about Jinx configuration as code plugin and then we could talk about her plugin documentation what do you think one yeah I like that so you'll talk configuration as code yep why not we didn't talk about it on the morning that'd be great okay do you see my screen so yeah Jinx configuration as code plugin is one of the trending plugins in the Jinx system now it has something by more than 1000 stars and this plugin was just released one year ago and we have hundreds of contributors we have a lot of cool requests coming every day including a lot of cool requests related to Hattroberfest basically they do this plugin that you can configure your Jinx instance as code so like you can use Jinx pipeline to configure your jobs as code you can use configuration as code plugin to configure your system itself using TML files and it was much anticipated feature from Jinx community members because before that you had Groovyhooks, you had different configuration management tools like Ansible or whatever but there was no engine within Jinx itself so this plugin basically presents this engine and we recommend users to try it out there is a lot of activities going on in this plugin so you can find many issues right inside the repository or you can find a lot of integration issues available within within Jenkins Jira so for example here is a link to the plugin compatibility dashboard where you can see many plugins which still needs improvements in terms of Jcast compatibility Jcast provides a lot of things out of the box but still some plugins need some love and if you have a configuration as code user probably you will discover some plugins which would benefit from updates so it's one of potential opportunities to contribute and another opportunity is to focus on the plugin itself there is still a lot of features which could be added for example for example here you can find that there is a demo folder which includes a lot of plugins but definitely not 1600 we have in Jenkins so it's a nice opportunity to contribute something and you can follow the example of Victor Martinez who is one of Jenkins contributors and you can see that there is a lot of cool requests which basically move from integration tests to demos and you can create new demos for new plugins for example you can just install the plugin on your instance export the configuration then just export and extract some configurations if everything works well then you have a demo if something doesn't work well you can report the community issue and try to fix that so it's a kind of end-to-end project where you can have a lot of opportunities to contribute so I see the hand raised very briefly so if you have a question please ask probably it was just in the space button ok another site of this plugin is documentation so we are working in order to improve the documentation and all the documentation is already located in GitHub but there are still some gaps which could be addressed for example there is still no documentation for REST APIs in the plugin and if somebody is interested to contribute it could be much appreciated for example Schwagger specification it's something you could do as well just by here for example there is a ticket for J-Class REST APIs so you can just submit the request to the repository itself and then it will be integrated and after that the documentation will be a part of Jenkins official documentation because right now we have republished it on the plugin website for example so there is a plugin site which basically publishes documentation to GitHub from GitHub now and I guess that Mark was going to quickly describe this project ok any questions? ok then I will probably just stop presenting but I can also show another hint about documentation while I am here so there are some plugins which basically extend the integration code like you need to run a Ruby code and you need to integrate this secret SSM plugin for credentials and if you go to these pages then yeah so this thing actually opens this page and there is a reason for that because if you just go to plugin string to Sayola then what we will see that there is actually an empty page here so for the documentation in case system there are such keys which could be improved and it is relatively between and Mark will be talking about how to get documentation published on this page ok there is no question so I will just stop sharing so that somebody can take it over alright so ok if I go from there Oleg yes so it looks like you have seen Jean Paulo on the background oh sorry did I miss something there hello hello Jean Paulo Jean Paulo is one of Jenkins contributors who is a maintainer for Easy Jenkins which is a standalone repository but he was an active contributor in Java 11 projects and also in Jcast compatibility alright thank you Jean Paulo thanks very much so Oleg had showed the plugin site so as an example if I search for badge the badge plugin on plugins.jankins.io here it is and here is its documentation and it is pretty weak considering that there is an awful lot of actual documentation already available for this plugin and many other plugins in their own repository sometimes that documentation may be on the wiki site in this particular example it's not but there could be what we've got is a project suggestion as a good Hacktoberfest topic to convert from using the wiki as the source of documentation that you see here to instead using the github readme so if we look at the badge plugin you'll see that the github readme has actually got a lot of good information in it about how to use this thing how you deal with it and so the pull request to create that transition from hosting documentation in wiki to hosting it in github is a pretty simple change I open up the palmxml file find this urltag and change it so I first got to fork this repository so I'm going to fork the repository it takes just a few seconds and it will be back that I can then make the change that I want to make so I'm going to go back right to that palm file and edit that palm file and instead of HTTP pointing to the wiki page I'm going to change that to instead point to this repository like that and I have to take off that portion now when I save this it's going to make a commit for me so use the wiki as github for documentation and now Oleg reminded me the last time we did this I need to mention Hacktoberfest because it will help people see that oh hey Hacktoberfest teams are suggesting this so Hacktoberfest contribution I'm going to propose that file change now it's going to put me right into the user interface to create a pull request so I'm going to create a pull request and here again say Hacktoberfest so that everyone can tell that I'm doing this and it was that easy so I didn't have a local clone yes I can locally clone I can do all those things I could have built the plug in myself this will help the project and take advantage of already existing documentation lets people see the better documentation that is already available inside the readme any questions on contributing by converting from wiki based documentation to github based documentation great and Oleg sorry I was looking for the plugin to label that properly according to the policies one thing about migration from documentation so it's not only about putting some metadata you're also welcome to actually migrate the documentation itself because if you use Jenkins wiki you might have noticed that sometimes it's unstable sometimes the documentation just obsolete and by moving to github you can achieve a lot trust the documentation as well so that new features etc can be documented out of the box it's more convenient for maintenance it's more convenient for users and it's a great opportunity to improve the documentation so if you're a heavy user of whatever plugin and you don't like its documentation maybe it's a good opportunity to put everything to github rewrite the documentation and then get it published and even that is just a part of a bigger effort so if you work on documentation it's much appreciated but you can go further because there is an effort for actually have better integration of this plugin site so it's not only about documentation we have recently introduced automation for change logs in Jenkins so you may have seen that there are many plugins for example we can take Mark's github plugin and many plugins have all been updated to github releases with some change log automation same for learning synergy same for configuration scope and our intention is to make this documentation available to users in public on the plugin site so that when we integrate to github here again you can see github but you also want change logs to be displayed there you want to simplify analytics for Jenkins users so that when you update you can see differences between plugin versions and change logs so it's a part of bigger effort to improve user experience for all Jenkins users and you can contribute to this effort by just joining this epic website 637 so here you can find a lot of additional stories for example support g-class logos on the plugins sorry not g-class logos just supporting plugin logos on the site pulling information from update centers like maintainers from another source because maintainers also quite obsolete in some plugins and if you are interested to contribute to such doing this is an epic for you I haven't put it as an efficient project yet because I didn't have so many new friendly pictures but if someone is interested I'm happy to play it once thanks any questions about documentation specifically plugin documentation I guess not so we have 20 minutes left so somebody try to turn me off so let's take a look what we have in our featured projects so yeah we talked we didn't talk about Jenkins core a small thing we forgot about okay so yeah Jenkins core Jenkins core is just a part of any Jenkins installation so it provides engine which basically runs Jenkins it includes web container it includes all extension points and also some critical features all of it is a part of Jenkins core and if you want to contribute it might be a good opportunity because Jenkins core itself it has a lot of activities pending now so if you go to GitHub you can see that there is a number of cool requests about cleaning up the code so we try to finally enable spot bugs on a higher severity levels we want to just add in the code base so you can see that there is a lot of reference and this is actually a great opportunity to submit small cool requests also if you want to find more new befriending features you can just go to new befriending issues there is quite a number of them for the Jenkins core and you basically can take there is a lot of minor bugs which are waiting for fixes apparently there are two high severity features which are new befriending and waiting for the bug fixes as Mark presented earlier today but basically you can just take something and try contributing and you have contributing guidance available for Jenkins core developers as well Jenkins core is basically a model made in project so if you're familiar with maybe you can quickly build it you can get tested and yeah there is documentation which helps how to get it running and how to contribute patches there okay if you're interested please feel free to do so and it will be much appreciated because yeah right now we increase velocity of Jenkins core changes so any contribution will be much appreciated since I'm there there is also a lot of changes going on with this packaging so for example we're going to send going for official packaging for windows I mean docker packaging so you can find a lot of full requests here in docker repository or in agent repositories like this docker general pstave I believe that many users actually run with them and if you're interested there are also opportunities to do something there are already some full requests marked as October 1st so feel free to submit more fixes and yeah pretty much every other repository in Jenkins say you can go there you can propose something it will be much appreciated could I talk briefly about platform labeler my favorite plugin do we have time yeah please do so officially we still have something like 15 minutes I see that some people started dropping but still if somebody's interested let's have a quick cover yeah great so so here's the here's there's this little plugin that I maintain called the platform labeler and it automatically applies labels to platforms so in particular to Linux platforms the challenge for me is a number of these Linux platforms I don't have and some of them for instance red hat enterprise linux and susie linux enterprise server are licensed operating systems so I would have to purchase them in order to support them fully if you're your company already has a license for red hat enterprise linux or for susie linux enterprise server you could contribute a pull request for these that just borrows briefly time enough to compile and capture some data from the particular files that are described inside these bug reports so it's an easy pull request to submit and it's a pull request that I won't be able to submit because I don't have access to those systems so it's a good opportunity for somebody from the hacktoberfest community who has access to one of those to help out introduction any questions I think that's it for today so again thanks to everybody who participated in the meta or who watches it online we will get this recording posted soon and it will become a part of our documentation if you want to find more information again there are some links which should be available so for example the hacktoberfest participate you can find a lot of information there and if you miss something just pass it in the gitter channel so that we will be able to help you and hopefully improve our documentation in a very long time so any feedback will be appreciated if you see that something is horrible that something doesn't work at all don't hesitate to let us know about it we will be happy to fix it or just to create follow-up tickets for it so again thanks a lot for your time and have fun have a great hacken time and have a great hacktoberfest thanks Oleg thanks everybody thank you thank you I will stop the recording if I find the button