 Alright, so so topics that I have were here and I'll just share my screen and we can go off the shared screen topics that I have for Jenkins documentation office hours are. Okay, so Jenkins contributor summit. Jenkins 2.271 change log and 277.1 change log and upgrade guide and then she code Africa. Sponsorship status report. Yes. Yeah, they got you got response on that nobody's ever responded to me on my other thing I even pink her in directly to see if I posted it so. Yeah, it was a bad idea. Well, I, yeah, and I, I'm not going to claim one way or the other. I had specifically poked them in slack and then asked the question and then was willing to poke again and had the additional benefit that Alyssa was also helping with the poking. So, so multiple pokes, maybe the magic solution. And really nothing to report officially so but but conversations look promising for at least one corporate sponsor. And that's that's a good sign. Yes. And then Mark will is willing to coordinate project proposals for the Jenkins project. So, so any other topics from you contributor summit change log and upgrade guide and she code Africa. Looks good to me. Okay, so then let's talk contributor summit the crucial thing that I need Vlad silverman can't be with us today he's he's out on an unavailable away from his desk. So, the question I had for you is, I saw that you hadn't registered for the contributor summit yet, and Vlad hasn't registered. I preemptively assumed you're both registered anyway and put you on the list. But now the question is, when would it work best for the for you, Meg, for us to do a contributor summit documentation track for one to two hours, either Tuesday afternoon, or Wednesday afternoon your time. I'm pretty flexible. Step back, I have, I don't know what we're doing what's happening Tuesday and Thursday mornings I got that I didn't know I was supposed to register for something so yeah and and my expectation was that if you didn't register because you and I had talked about it so much it didn't matter that you didn't register no requirement that you need to register no expectation that you would register. I was using the registration just as a way to pull people, which areas were interesting to them. I know yours documentation and which times were available for them and I know yours in general it's afternoons in in US time zone, you know in California time zone afternoons. So what I was trying to do here is say, Okay, if we met at this time tomorrow, or this time Wednesday with that work okay for you or is an hour later better or two hours later better. I think let me. Let me go check my calendar but okay, I think my afternoons this week my mornings look I've. Okay, what happens at these sessions that are for me started seven in the morning. You actually don't particularly need to attend those. Oh, my hero. Well, I can tell you what happens in them so the first 90 minutes of the Tuesday session will be a summary of the results from the last 12 months of development work in Jenkins. Very valuable, but it's just a summary and you could watch it later. It'll be recorded okay absolutely and then the last 30 minutes is a coordinating session, where we find the times when the tracks will work best for track participants and since you and I are already doing that. There's no reason for you to be up at that early hour of the morning to attend to attend that session so. So the intent here is let's, let's not even assume that you will attend that session or the Thursday session because the Thursday session will just be a summary of the results of all the tracks. Again you can watch the video of that you can watch the recording of that. So in these afternoon sessions what happens in those. Those are the working sessions where we talk about where we're going where we review, for instance, will do review exercises around the, the framework or the outlines that I'm going to assemble hopefully on site. We'll do discussions about hey, what would it mean to have search site search enabled on the Jenkins documentation site. What would it mean to have an improved site search on the plug in site. And those kind of questions will discuss with Gavin Morgan, and others Gavin happens to be an exactly your time zone and he tends to prefer your, your style of working hours, at least a little closer to yours than to mine as he's a good candidate for the Tuesday afternoon or Wednesday afternoon session as well. Okay, looking at my schedule. I have one meeting tomorrow from two to three and it's a very, very flexible when it could easily be moved. Okay, so that I'm open. And right now it's your time it's three. Um, yes. Okay, so it's so Tuesday afternoon after three after 3pm works for you is the same for Wednesday Wednesday afternoon. Yes, I would say afternoon on either really because the it's just no well and I were just going to go over front matter for the courses. Okay, and it's you know, she just threw it up as a time and said, you know, move it I don't care. Okay, so that it's as good as any other time but there's nothing just two of us and all right great so and I'll, I've still got to check with Vlad to see what his calendars like I know and I don't know Jonathan's either. Jonathan I think strongly prefers this time slot because of his work schedule this is just after his working day has ended in Brazil. Okay, so my bias is towards choosing this time slot again because I'd like Jonathan's input he's one of the key players in the site search questions and right hey what are what are the things that work well and what don't. Okay, so. So that's that was the crucial thing for me. And then just as a reminder day one starting session is a 90 minute overview, and then 30 minutes coordinating the track meetings, and we know there will be two docs tracks, at least one for Europe, Europe and Africa. And one for West Coast US. Okay, I'm actually three o'clock California is like 7am isn't it in Australia and. Okay, I didn't know that but that's interesting. I think. I think the Australians ran. I'm just saying that that that late afternoon one might let us say that it was open for Asian Pacific to. Yeah, so can invite can welcome Asia Pacific. Asia contributors at that time. I'm also welcome. I'm also willing to meet during a time that works very well for a contributor from Asia if they come. That's that's one where I've got several that have expressed interest from Asia specifically from India in documentation and I want to send them a meeting, send them a question saying hey you've expressed interest in this. Would you like to meet at this time or at this time to discuss further. Some of them, some of them didn't actually I should show you well I can't show you just a minute let me turn off. Let's see am I screen sharing I am right. Yes, yes. Okay, so I'm going to briefly pause my sharing. Bring something up and show you this really now I guess I can't because we're recording, but I've got what I've got is the people who have registered have provided. So the, the people that have registered have provided their preferred times. When they can meet, and I want to use that. Use that to suggest time to even before we start the meeting tomorrow because you can imagine 3pm UTC is terribly early for the US West Coast, and almost unbearably a bad time for Asia Pacific right for Japan. It's that's just, or Beijing China that's like the dark middle of their night. And so, so many of them who might have been contributing who might have been interested may not be available or willing to attend that open session, but they might be willing to suggest hey if you could meet at this time, Tuesday evening or Wednesday evening or Wednesday morning whatever. They might be might be willing to contribute so. So I'm going to offer ask that question later today to them in an email. Now, what am I expected to do in these sessions. Be a listen, comment, discuss and bring your ideas. Somebody else is leading right who knows what I will lead right I'll be leading the docs. So, so I'm the I'm the leader for the docs sessions and for the platform sessions. And I have some some draft agenda ideas that I've assembled and I've got more agenda topics than we will then will reasonably fit in a two hour session. So, so we've got a lot of topics you know hey how do we improve contributor onboarding. How do we add site search. Google summer of docs do we want to do it. Those kind of things and I've got a bunch of those as candidates current outline review process. That's the one we had discussed over the course of the last several weeks hey we need to. Let's talk about the chapters in the Jenkins handbook, and which content goes into which places in those chapters and which content doesn't fit in a chapter. So I think we've got lots of places where good dialogue between us could really help. Right, right. Oh and if you'll be there. You know, I mean I have ideas but I'm still. There's times when I'm just totally stupid about stuff so if you're there I'm comfortable. Well, and I just had experience with was who was it Janet Janet Gregory I think it was who introduced me to a tool that that I may try as an experiment in the docs. I think it's called Jamboard. Google. Yeah. So it's this post it's post it's on a big whiteboard digitally. So we may do something like this in the docs in these docs sessions just to try to get ideas collected etc. So, so I've now learned a new tool and having a new tool I may have to see if this problem is worth hammering it. So. So yes, so do we know. I mean, we have are these people like glad and Jonathan who mess a lot with tools or they a lot of writers or. We have, we have two or three different categories of people involved right so Jonathan. Let's take, let's take going from East to West. So, Zina is has been predominantly a writer but has has a little bit of tooling experience but predominantly writing for us. Then Kristen whetstone, lots of tooling experience she wrote the thing that the original implementation of the thing that extracts pipeline documentation, and makes it publishable on the Jenkins that I oh site so lots of coding and tooling has been a connection in the in the Czech Republic has lots of tooling experience but I'm not sure he'll attend. Then as we come further we've got me who I've done mostly writing not tooling. And then you and Vlad, where it's a mix of writing and tooling right Vlad's done, done some tooling and, and certainly plenty of writing. And, and then we've got a number of people whose names I simply don't recognize, therefore probably first time contributors fabulous. Well, if, if they attend great. Many times you get a first time contributor who registers and they don't even bother to attend. Jonathan, Denise, Jonathan more ice as well is a is clearly a tooling expert who's also done some writing, but it's his real forte is clearly tooling he's very very good at it. Okay, so we've got a mix and, and we'll try to shape the conversations to fit whichever group is in that particular session so if, as I suspect in the Europe and Africa session we get Jonathan and Zina, we will likely likely spend about half time tooling and half the time on content and structure, because Jonathan was the initial initial one who helped us through a content and structure exercise so he's interested in that but he's also deeply interested in search and search and other tooling. Okay. And then the, the US West Coast when I think will be dominated by writing portion, unless Gavin chooses to join and if Gavin chooses to join, then we'll talk pretty deeply about what search means, and what he's learned from the plug in site, where he implemented search using a commercial search engine. So, so that's an awful lot of words to say we'll, we'll adapt as we go. Right, just kind of want, you know, wrap my mind about what the sort of parameters are so. Right. And then. Yeah, for my schedule. Anything from noon until 3am is a no brainer, but I can be flexible on the other sides of that so. Okay, excellent. So, very good. Okay. So I think we covered that the crucial parts are there. I've got actually maybe I should show my slides let's talk about the doc slides because I've created some slides for the contributor summit. And I would love to have feedback on them. If you want to if we can just go two or three minutes through them it's it's like like one or two slides and see if I missed something. I'm good for whatever summit here it is. Okay, so here is the slide deck. And we'll have welcome and intro why we're doing this what's the schedule. And then we skip rapidly down to Jenkins releases Jenkins user experience. Okay, so here's my piece. Oh, I need to put artwork on this just a minute. Okay, which, which Jenkins artwork do we want to choose. I don't know I still want I want Jenkins holding a book and Jenkins with a. Yeah, and I don't know which is the one that is the closest approximation to that already use that one for platform. I think I like the the one with the rapier the sword here. Because that's my preferred one so far because we don't have one with a book. Right. I've used this one before. So I'm going to go ahead and just grab that one for now. Okay. And if we get a better one we can always insert a better one later. Right. Because we did have we did have one from somebody in in the in Asia if I remember right where they had a, a like a scholar kind of thing it wasn't a book. Yeah, that's if we're looking for training yeah we don't see a book one. Okay, so there we go. All right, so what I said was hey, we've had made great progress on migrating documentation to GitHub, over half the plugins have migrated, which is actually quite amazing. With as many plugins as there are and in the varying states that they're, we completed Google season of docs, and that means we've got dramatically better Kubernetes Kubernetes documentation thanks to that work from xenobu car. Do you want to slide. What's that. Do you want to mention what was accomplished out of season of docs. Yeah, good. Kubernetes Jenkins on Kubernetes. Bernadies. Is enough of a car. And special thanks to Gavin Morgan. Gavin Morgan for tooling. Oleg Natasha for promotion tutoring. Wiki migration in progress, slow progress needs structural help. And twice weekly, we've got Europe and Africa to attending regularly. And we've got US West, US West Coast, two to three attending regularly. I don't know where Jonathan is today, but I know where Vlad is he was unavailable so. Three to four attending regularly couldn't we. Yeah, yeah. The year we've had a lot of times when Vlad and you're on a dinner roll. That's that's fair. Good point. Okay. And then on the what's next in documentation I said, Hey, we want improved site search on the plugin site. We want site search for the Jenkins docs site. Change log automation. And I don't know how to, that one makes me a little nervous because that one really needs Oleg and I'm not sure he's available. But I'm going to put it there just in case. Okay. Okay. Inventory the current documentation. And proposed document proposed destinations. So this is the, this is the work that we've described earlier. And improving the contributor onboarding experience that one is, is definitely a need. We've seen with Xenob that the documentation development has to have a for for most convenience you need a Linux computer and that's not something every contributor has Linux or macOS and again that's particularly in, in what you might call underserved communities. They're more likely to be running windows than anything else. Right. Okay, anything else that you recommend there I will double check these tonight but your suggestions are welcome. I went along improving the I'd like to see us getting more new contributors into the doc stuff. But maybe that's implied by that industry. Well, let's add more contributors I like that. Yes. Yes. The real the real goal is add more contributors maybe we should say it that way. And we need to improve the contributor onboarding experience because otherwise they may arrive and leave. I like the current contributor onboarding experience if one is running Mac or Linux is that good. It is. Yeah. This is a windows issue. Yeah, so she called Africa's she called after a project ideas. Okay, you're going to have to split split the slide don't you. Yeah, and really maybe we should do that already is admit that it's going to be a split, because what there are more contributors because that stuff up there is sort of known and in place, and then this other stuff. Yeah, I like that. Very good. Okay. I hope to well and inventory the current documentation really needs a converse, you know, more discussion what does that mean and why are we doing it. These are sort of pie in the sky going future those are other things that are sort of in progress sort of known. Right. Yep. Good yeah so the yeah I like that because these things. I'm quite confident we're going to make happen. Right. We're going to make things so that it will be a push. Yeah, some of this will probably happen but you don't know exactly what part. Right. Yep. Okay, very good. Excellent. All right so let's. Okay, anything else on contributor summit. Looks good to me I will listen and learn. All right, so next topic was Jenkins 2.277.1 change login upgrade guide and that's a. This one is there are four major areas changing in 2.271. That is table configuration UI changes. From the table, the HTML table to div transition. Then there's the some HTML internal changes from the jQuery update. Then there is the authentication the security framework update from a CG to spring security framework. And there's one more that is oh dear what is the fourth topic there. Oh yes, extreme upgrade. And on fork. Sorry for using a non word. So, so those, those four need need some alert and discussion and framing them in user terms, and the release candidate is scheduled to be available. Wednesday, the 24th with final delivery release. And then for March 10. So this one, the change log and upgrade guide it would be very desirable to have it ready for the release candidate. So that people can review the release candidate and review the upgrade guide and the change log. Now there's also additional benefit for others with this that, for instance corporate products oftentimes can base their change logs on. Change logs on the Jenkins. Whoops on the Jenkins open source change log. And so I have people who are asking from a business perspective, hey, when do we have the change log available. So, further motivation to get this thing done. I love to have reviews of it, but the reviews are somewhat complicated because it's done using a, it's a data driven change log that has a very specific style guide. Daniel Beck has been my primary reviewer and he's absolutely wonderful reviewer with Daniel back what else you need. So, but there's the style guide and it talks about rules and regulations. And then the change log itself appears here look like this. So this is how the change log looks, and the upgrade guide is in a also accessible from that same page. What happens with documentation changes that might be necessitated by new features. Is it expected that whoever contributed the new features updated any documentation or Yes, so if they're well depends on what you mean. So, for instance, if there's something that is changing a core component, then then it's expected that they will submit new features to the documentation to support that that change in the core component. Jesse Glick for instance submitted as part of the, the extreme and the, the, let's see, it was extreme, and it was extreme. Yeah, CG as part of that he submitted two different blog posts, or a blog post that then I supported with another one so this was his blog post on pay here these major changes coming. This is what it means and this is where you go for more information you go to either this page, or you go to this page. You go to see if there are open issues you click these links to see okay, any issues open, none for that one. Any issues open there, none for that one. Okay. I haven't even looked. Do we have screenshots all over the play the, the change in the doing the tiling for the managed shaking page and all that sort of thing. Are there any screenshots that have been impacted by that all over and we do and those have not been updated so, for example, we did just Zina just submitted the updated Jenkins installer for windows screenshots and they are correct and complete. But for example, the, any pipeline screenshots or let's take a different one pipelines probably a poor choice because it's actually not largely not affected by, by this 2.271 7.1 but if we were to look instead at system administration if there are any screenshots here. We expect them to be now be out of date because because things have changed let's see what we've got here so for example, monitoring doesn't have any screenshots, securing no screenshots. Oh maybe they've gotten clever and cut back on the screenshots. And given the relatively low, low small amount of information that's available in these, and their focus on administrators it's it's uncommon for these particular things to have screenshots. Okay, but any place that does for example if we look at managing Jenkins, the managing plugins, it's probably got yeah, here you go. Here is a here is a screenshot of the managing plugins page. And if we look at remember that page I'm now going to bring up the current Jenkins page that looks, I do know what it is that you don't have any lists there. Well yeah so let's let's see this so here's manage Jenkins manage plugins. And this is available and it looked for find bugs, other than how amazingly fast it is. If we look at this. You'll see a rather different user experience there so let's maybe drag this. Let's put them side by side. So there's one. And now you see, okay notice there's a message about deprecation. There is information here about when it was released, that is no long that is not in this screenshot version number so yes we definitely need an update to our to our screenshots, and we haven't done it. I think the pros around it probably needs to change to. So how is that handled I mean, obviously we can't always get that at the release, but do we at least generate an issue that this the section needs to be updated or we do not commonly that's a good point that a review of the sort of as an example here we go this from the web UI page this HTTP proxy configuration screen will look quite different with 2.277 so now, if I go there and let's go to the plugin manager and first notice that Jenkins is not catastrophically broken on a narrow window I love it it's brilliant. Yeah, go to advanced. Okay notice the difference between these two pages so here we've got the field is left edge oriented and expands to fill the whole space, instead of this have a label and be require a minimum width. Right. So now with this thing I can actually shrink this, and it still works make, and it doesn't put a horizontal scroll bar in it and. Oh it's much, much better, but it is different, definitely different. No improvement. And the other question because we don't have versioning right and huge numbers of people are not updating so what happens to the old people they've just lost their documentation. So what they do is they see a screenshot that is more attractive than the screenshot that they have and now I, I did that as a test case with with a certain plugin that I maintain. And, and have had no complaints at all about it. Oh good. So this thing has been switched so that all of its screenshots are now. Oh, here we go. I changed this screenshot as an example. This is the new UI. And yet, there are old screenshots in here that I still need to take again. So, so this is a good example of needs more work to update the screenshots to reflect the new UI because the new UI is much more attractive in terms of its layout, then this layout is great. So, so when did the screenshots get updated. They don't. Okay, unless somebody does it. That's maybe we ought to put that as as a topic, because really. So screenshot updates updates based on the 2.277.1 user interface, and that that might be an excellent candidate for a she code Africa project project to get better screenshots to get. You know, you had all the plugins and stuff a lot of those were good first projects but this is another thing that would be good for somebody with coming new to it. Right well and, and this is this is more of a documentation effort than it is a plugin code development effort. Right. So we could also do pipeline pipeline examples submitted to to plug in source code as as a as a another candidate and that would be more development focused but with an HTML spin on it. Right. Whereas this one is mostly doc with with a doc. And all strikes. Good. That's, that's a good one. Thank you for helping help and discover that. All right. So, let's see anything else to discuss on 2.277.1. I'm good if you got what you need I don't have to produce this thing. I've got to spend the time on it today and tomorrow and squeeze it in between in between things so yeah I think I'm set. Good. All right. That's very promising actually the notion that we could use she code Africa contributors as a way to update the documentation for the screenshots would be really attractive. It would be how many do we have. We have the one do we have a group of people in she code Africa. It depends on how many are funded and, and which projects they select, etc. So, I, I don't know right now and they won't know until they see how many corporate sponsors they get. Okay, I just think it would be nice. My, my impression is that women tried to code in Africa are often feeling rather alone. Yes, have some people go while you're wonderful that you can do all that stuff that it might be a chance to let them form sort of their own little sub community. Right and I think that's what she code Africa is doing right its goal is to form exactly those kind of sub communities. Yep. Okay. I propose we call an end here and I'm going to get back to work on the change log. Sounds good. Holler so you'll let me. So I'm not going to get up at seven in the morning tomorrow and Thursday and you're going to put something on my calendar. Absolutely, right. If you are you, you've only got one thing to conflict on Tuesday afternoon and if you need to conflict with it do I can move that so great. And I will what I'll do is I'll send email to Jonathan to Vlad to you and to several others proposing a time for Tuesday or Wednesday and asking for for responses back. And then, then we'll try to work that out before before the session starts tomorrow. If it doesn't work out before the session start starts tomorrow at 7am I will work it out in that session, and then send you the link so that you can see it when you get up fabulous. Alright, thanks. Thanks so much. See you tomorrow then. Bye.