 things covered today. Welcome. It's the 6th of May, 2021. This is Jenkins documentation office hours reminder that we follow the Jenkins code of conduct. Be nice to each other. So, Dheeraj, I don't have any particular topics that were hot for me. Are there topics that you would like to bring, things that you wanted to discuss? Well, nothing specific from my side. Just a few doubts, like very small doubts about jcask docs. I think it's just a one question, basically. Great. Well, let's put that on the list just a minute. So, five, six, and topics. Okay. So, jcask documentation question or jcask question. And Kristen, I'm not sure you have any others. So, let's just go ahead right into that topic. So, Dheeraj, what's your question? And let's talk about it. So, last time we discussed that there are already some contribution guidelines present for maintainers as well as for the new users for jcask, right? And you also redacted me to data breed me as well. And all of the instructions are very clear and very nice. So, my just simple question is that what qualifies an article to be published at Jenkins.io's website from data breed me. Because I think that sounds more looks more professional if it's on Jenkins website. Yeah. So, are you interested? One of the ways that we take content into Jenkins.io is with documentation submissions that go inside the inside the documentation. So, on www.Jenkins.io. Another is a blog post. So, if you're interested in trying some experiments, exploring a little bit and then writing about your journey doing that exploration, then a blog post would be just fine. If you would, if you say, no, I'd rather write about how to use configuration as code in production. And I want to do, I want to do writing like it was a manual and be able to point people to this. Here's an example of my writing of a professional quality manual. Then you'd probably submit to the Jenkins documentation rather than as a blog. Which, which of those two is more interesting to you? I think blog one sounds more interesting to me. Good. Okay. So, that would be great. Like any type of like, hey, I'm trying it out. I'm experimenting. Here's what I found out. That would be so helpful to a lot of people. Yeah. So, go ahead. So, one thing I noticed is that in previous to previous meeting, Mark, you showed me that how we can extract a UI snippet from the main Jenkins YAML file when you go to view configuration tabs in Jenkins on the site, right? Jcast. So you asked me that you can extract the snippet out of it very easily and just know how we can configure a plugin using Jcast. So this thing was very helpful for me to know how we can use Jcast. Then I noticed that in GitterChat, there was a message from somebody else. She seemed like an experienced guy and he was asking how I can find out that this XYZ plugin can be configured with the Jcast or not. So then Tim suggested the same thing, go to Jenkins UI, configure it and get it. So what, so this suggests that not much people know about this feature that you can actually go there and do that. So I was wondering, as Christina also suggested that you can document anything you are finding out along the way. So this would be a nice thing as well. That would be excellent. And one of the things that you might consider to make your blog even more interesting if you could record a two-minute demonstration of doing exactly that so that people just record your screen so that people see what the clicks you're making because many times they read the words and fail to make the transition to what is the action I must take on the screen. Whereas when they see the video playing and it probably should not be longer than, you know, the shorter is better. So 60 seconds or two minutes is much better. What you do then is you record that video. And for instance, I record mine with Zoom. I just turn on Zoom, a meeting of one and share my screen, record it and then download it. And it lets me use it. It's a very simple screen recorder. It doesn't have to show my face. It's all just shared screen. And then you can embed that video inside. And what we would do is we would host your video on the Jenkins YouTube channel. And what that then gives us is it gives us measurements of how many people have clicked through to watch the video. And so we can now take hints. Oh, good. Did video supporting a blog post help it? Or were no, there weren't that many people who looked at it. So yes, if you're willing to do a blog of, hey, my first time experience using configuration as code and highlight these kinds of things where you say, look, you absolutely can I use this plug in? Yes, I can. Here it is. I configured it in the usual system. Now I open up configuration as code. Here it is. And I paste that into my configuration and I'm set. Exactly. That sounds like something I can do. And it would be really interesting to do as well. Great. Good. Okay. Yeah. So the other for me is that if the video, if the screen recording is interesting to you, it's interesting for me because I'm curious if it helps people or not, if we get more positive hits, if we get many, many accesses of that video, I did that technique with the get plugins documentation and have been amazed at the number of people who click through and watch that video all two minutes of it, right? I mean, it's very brief. So this is how you use this thing. And lots of people seem to like to see a video of what's happening much more than they like to read. Exactly. You showed that with views previously as well. It has lots of lots of views compared to me. Right. Yeah. Okay. Good. So well, that's that's good. So first time experiences with configuration as code. If you're if you're interested, well, I think I linked you, I provided you the link to the repository where I track my configuration as code, right? So if if you want to see some examples, now that thing's evolved over years. So it's it's not a great choice to put in your blog. Your blog should be your experience where you you share with people. Look, I did this and I did this and I changed the description of my Jenkins server and I changed these things to make it valuable to me. Definitely that makes sense. Great. Excellent. All right. Now, Dheeraj, have you been able to have you been able to create a development environment that will allow you to work on the Jenkins.io site yet? Maybe that's something that you might need some assistance with. Sometimes people find that a little bit challenging to be able to build the site locally and see how it looks. As of now, I think I don't I haven't done that yet. I think I need to look for it first. Okay, so yeah, so so I'm going to what I'm going to do is I'm going to put into the notes a link to the the how to get started for that for that site so you know how to do your how to how to get begin a blog post. So here in the contributing file and for your help, it's also posted in the chat here. So the Jenkins.io repository there has a contributing file and we like to think it's easy to use, but we had bumps and bruises for our last contributor that was using it. So don't be shy at saying gee, I don't know what it takes to make this work. Are you now are you Windows based or Linux based or macOS? Linux. Okay, good. So you have chosen wisely. Good choice. Yes. In this case, because it's the the environment is known to work quite well on Linux. So so I do my development on Linux. I think Kristen when she does doc development probably does hers on Linux. I know Meg McRoberts does hers on Linux. So yes, we've got some Windows based people but Linux is we know works. Great. All right. Any any other questions that you have? Excellent. Thank you. And thank you for being awake at this late hour of your night. I assume it is the middle darkest darkest part of your night. So thanks for being here. Very much appreciated. Thank you so much. It's totally fine. Excellent. I don't have any other topics. Kristen, did you have any other topics that you wanted to bring? No, do we need to talk about is there anything for a contributor summit? Excuse me. I don't know if we have anything for I just like just onto that. I don't know if we're ready to talk about that or if there's anything that we need specifically for docs. That's a very good one. Let me let me put up a shared screen and let's talk about what's there currently and then we can refine it. Absolutely. So okay. So what I'm going to do is bring up here are the notes from today and then we need to look at the contributor summit which the way I find the notes for it is I go to Jenkins.io, look at the blog on contributor summit. Now where is where oh no no no no no sorry it's community over how where is just a minute contributor summit at CDCon. Okay. So contributor as always right there it is contributor summit. Okay. This one and here down at the bottom is the coordination Google doc and what I had put into this doc was for Jenkins documentation the topics we would be discussing Jenkins and Kubernetes as of the documentation for Jenkins and Kubernetes as a funded outreach project likely to start September of 2021. We don't have final approval yet but it feels like it's a reasonable thing to do and we've actually got good work already started from oh dear from Sudhakar who's who started an outline and has already started plans for how to write on it. So so that was my thought was one the other was contributor onboarding and now Dirage will be a good test for us how what's the experience for a new contributor onboarding on Linux and we'll we'll learn from that we know Windows had several difficulties for for Xenob during Google season of docs 2020 then I had content improvements including the wiki migration project are there other things you think we should put on to the list for for a documentation track no but it's good to see this for right now um I it'd be also interesting to hear if there's any teacher proposals I'm not sure really definitely the contributor onboarding improvements I almost feel like we're missing some of the stuff around the getting started with Jenkins development I feel like from contributor thought maybe like that was something that we need I don't know that falls under the wiki migration project maybe well or well it probably does actually I think about this like a weight probably but but if I took if I took it under contributor onboarding contributor onboarding certainly a hot topic right now and maybe what we should say using what we learned from Sheikot Africa yeah to improve the experience yeah cool that that's perfect and really this is this is not just because they weren't actually doing per say documentation development they happen to be writing documentation but they were inside code doing it and so it was really developer experience for programmers and writers right right this isn't just this isn't this isn't a thing about just documentation improvements we learned some things there that oh hey it's better if we do it this way for someone who's not not got Java experience or who has not never done Maven before good okay very good cool I'm glad to see that this is what we've got for a we've got a lot for contribute for contributor summit this is exciting yeah so let's see and and and we've got the Sheikot Africa retrospective tomorrow to gather and sort of refine that into into a better set of actions good okay great now one of the things that that we had on let's see I submitted the roadmap pull request proposing maybe let's take a look at that for just a minute if you're okay with that where I submitted a pull request to update the roadmap based on our February work so in February we had these slides that we presented continue the 2020 roadmap plug-in docs wiki docs and terminology increase the outreach so we said we'd mentor Sheikot Africa we did that the google season of docs we got rejected so that won't work and then we said improve onboarding so those are those are I think still aligned then this one wiki migration is probably a bigger thing than that is described in this contributor summit because there's a lot to do for us to before we can actually migrate off wiki yeah so that that maybe what we should put there is timing leader etc and then there was yeah so does does that seem reasonable to you Kristen yeah okay all right great and and Oleg is currently watching over and shepherding this this document so hopefully he'll approve those proposed changes as we get closer to contribute on or as we get closer to the contributor summit excellent link to this very good all right anything else great thank you I'll I'll we'll end the meeting I will post the recording of the meeting in probably 20 or 30 minutes thanks very much everyone thank you thank you so much bye