 Hello. Hello. I am good. Let me start my video. There we go. Oh, good. Thank you. Okay, so I had, I had only contributor summit communications improvements. Actually, I'm not even sure. Well, that's probably a healthy one to discuss. And then I think we should probably include. Outreach program status just. Just in case. What topics do you have that need to go on the agenda? I have an ebook, ebook, the Jenkins is the way ebook number three. That I like to get a plus one or a negative one. Hopefully a plus one so that we can get that published on the Jenkins is the way.io website and get some visibility on it. Yeah. But this ebook focuses on the fortune 500 companies. Oh, cool. So you've got big names. Yes. Oh, wow. Okay. Yeah. So, and, and so do you have a link to that ebook that, or have you already sent it and I'm, I've just been ignoring your email. No, I sent it last night, and then it got rejected because the file was too big. So I need to zip it and then. Resend it. Okay. All right. So. Topic is added to the agenda. And I think it may just be you and me. I assume that Jackie is probably, probably comatose somewhere trying to recover. Sorry, that was a tip. Thankfully I'm not being recorded, but, but she's probably comatose somewhere trying to recover from CD con. Yeah. Yeah. I don't blame her. If she's not, if she's not. Drowning her sorrows in alcohol, she's hopefully doing something very healthy that, that helps her. Yeah. Yeah, we get the July 4th weekend. So a lot of people are out. Oh, right. Hadn't thought of that. Very good. Okay. So I'm going to start the record. I'm going to share. I think it's already recording mark. Oh, is it? Oh, it is. You're right. Oh, so I've already been. Oh, that's terrible. I may have to edit out my comments about. I don't know. I don't know. I don't know. I don't know. I don't know. Copious amounts of alcohol or anything. Okay. Sorry. No offense intended, Jackie. It's all love. That's right. It is true love. That's great. Okay. So let's share this. So here's what I've got for agenda. It is the July 1st. Okay. Contributor summit retrospective document is under development. And then, in the office of code upcoming. A CDF. Webinar. A week of July 19. Presentations by all six projects. Nice. That's what the hope is anyway. Yeah. Okay. So that, and then Jenkins is the way e-book number three. So nothing else to put on the agenda. Uh, do you should I mention about the DevOps radio opportunity that cloud. Oh, yes. Yes. Right. Okay. Sure. Absolutely. Okay. So let's let's put that on the list and great. Okay. Okay. So on the contributor summit retrospective, the retrospective document is here. It's available. Please let's see where is the link to the retrospective section of it. I have to find it. What? Here we go. Here's the retrospective. And, um, that is just a great opportunity for us to learn from the experience. There were lots of things that that it went very, very well, but there were so many things that we could improve that we would be remiss if we didn't use them and learn how to do these things better. Now, Alyssa, one of the things that's on my mind is I assume we'll have a contributor summit associated with DevOps world. Yes. And that's also your plan, right? Yes. Or unless that has changed between, um, maybe perhaps Oleg and you, but, but yes. Yeah. And Oleg and I certainly did not discuss any, any backing away from it. We did. We did note that would like to have the summit. And this will be a little weird maybe, but during Asia Pacific times. Okay. So India and Australia and China can participate. Okay. And, and that may mean, well, it may, may be a little strange, but I think it's worth it because we, we had a bunch of Asia Pacific contributors in the current summit who were meeting with us at 1130 and 12 at night. And that is, that's heroic of them, but we'd like to, to counterbalance that. Sure. Um, and then I'm assuming that we would use the same platform that we use with CD con, which is our own zoom, right? Or that works out fine. Yeah, that's, I, that was my assumption as well. Okay. The, uh, there were lots of observations about the, the many different ways that that didn't go perfectly. But, but the, the summit itself had great results. It's just, there are things we learned about painful mistakes. Don't do this mark. Don't do this mark. Don't break things this way. And, and so those are all noted in the retrospective. That's how we learn. Yeah. Well, it's just awkward to learn in front of 45 people who are all very skilled, very talented technical people. But that's what I did is I learned in front of an awful lot of very technical people. That'll help you to remember. Exactly. Yes. It's, it's embedded. It's burned into my mind. Absolutely. Yeah. Okay. Anything else on contributor summit. Um, so I have the t-shirt list. I will work on that. I've not forgotten about it. Okay. Oh, good. Thank you. Thank you very much. And you'll handle the, the shipping, et cetera. That's sponsored by cloud bees. Yes. Thank you so much for cloud to cloud bees for doing that. Excellent. Thank you. Yeah. All right. The next topic was communication improvements. We're using this discourse site. To gather and encourage people to talk and chat with each other. And then we're going to talk about what we're doing. Here we, here we've posted, for instance, links to the contributor summit, the full sessions. And it's an easy to use platform. It's very simple for me to post those kinds of things. The content looks good. It's, it's not a, not a poor experience for the user viewing it. And just helps us be more effective. We're still, we're still in prototype mode. It's not yet. Not yet superseded. As many places. Oops. As we think it will. But for instance, I consider the documentation SIG. Communications. Are now on dis are now there. And, and I like it. It's, it's simpler, simple and easy. Yeah. Yeah. I like it as well. We had talked about posting blogs. Yeah. Discourse. So is that still in the works or under discussion? It's, so I think it's still an open topic, but it's an open topic that will likely wait until Oleg's back. Okay. Because I think, I think you've, you've got an excellent point. Alyssa's, let's, I'm going to use you as a very specific example. Experience creating Jenkins.io blog posts is terrible. It's painful. It is. It's, it's just painful, ugly, et cetera. Right. It's just not how we want. It's not what we want. If we want to encourage people to contribute. And, and it's, that's just the reality of it. Right. If we want someone to contribute and we say, Hey, we're open to your contribution, except that you need a PhD in computer science in order to do it. Yeah. That's, that's not the experience we want. So, yeah, I'm considering ways to either blog across post the blog or cross host the blog from discourse. To Jenkins.io or other techniques like that. Yeah. Yeah, I had, I had a similar, Oh, I had a discussion with Roxanne from CDF. And I said, you know, because she also posts blogs on Jenkins.io and she made it seem really easy. And she said that she was also struggling with it, but her only advantage that she had was that her husband is a developer. So he helped her with it or else she would have struggled too. Right. Good. So, so that, that highlights. Now I guess we missed one item. I've got to show this because it's such a treat to have this. Oleg has already added the ability for us to comment. On blog posts. In discourse. Yeah, yes, I saw that. I love that. And quite a quite a cool feature. It's okay. Look, we announced this change, but now conversations. Oops, we announced this change. This change here, but now conversations can happen here and people see the conversations attached to the blog post. Love that. Yeah. So. Oh, and I have an action item there. That's right. I need to create a blog post for the contributor summit. Because we need need to capture. The videos. The ideas, the action items. Etc. Good. Great idea. Yep. Okay. Outreach programs. So I listed Google summer of code and July 16. Let's see July 12 through 16 is evaluation of phase one. And then during the week of July 19. Kara Della Mark is leading the. Is gathering the students and preparing them to present. Any questions there, Alyssa, we will, we will need to the usual things. We'll, we'll need to promote it. Need to encourage. Involvement, et cetera. Yeah. Okay. Next topic then Jenkins is the way. So, um, E book number three Jenkins is the way E book number three is, um, has just been, um, completed. Um, it needs to go through the community for a round of approval, but this E book focuses on the fortune 500. Companies that are using Jenkins. Um, so just off the top of my head, um, you know, we've got IBM and Apple in there. Uh, and Roche, I think that's how he's pronounced it. Um, but they tell their stories, how, what the challenges were and, um, how they use Jenkins to solve problems and what benefits they got out of it, what values they got out of it. So, um, I'll be sending sending. Should I send that out? The, uh, the sick mailing list mark, or should I put that in discourse? Oh, that's a good, that's a good question. I mean, I think we've got. Yeah. So both of them are public lists, right? Why not try it in discourse? Would you be willing to try it in discourse? Yeah. Yeah. Yeah. Yeah. Because there's, there's nothing in these that sensitive, or there's not intended to be anything particularly sensitive or things like that. This is not where you need private, private conversation. It's really okay that this could be. Yeah. I would love that because it then gives us a chance to check. How does discourse work with. What in this case is probably a large file. It's a PDF file. Yeah. Yeah. Right. So. And so you may need to, may need to host that. Place that on Google drive. What I found just as a pointer, what I found when I was doing the discourse postings for, let's see, let's, let's show it. I just posted a bunch of things for to Jenkins. To community.Jenkins.io for these talks. And the easiest way to do it was. If we look here, they don't show me the text. Oh, that's so sad. They've already, what you do is you see where it shows these videos. Yeah. All I did was paste in there. A URL to the video. I did nothing else. Well, all by itself on the line, a URL to the video. And I think a URL to your PDF file may cause it to be expanded automatically by discourse. So it's visible right there as here's a PDF file with a thumbnail, but it's not visible. It's not visible. It's not visible. It's not visible, et cetera. So, so, yeah. So I think. I think. Discourse is a great place for you to post it because it'll probably be a better experience for you than even email is. Okay. Okay. Great. Excellent. Anything else on the ebook? Nope. That's all I needed for that. Now it may, I think it may help. To include. To post to the mailing list. With a pointer to the discourse discussion. Okay. Just because if somebody hasn't yet started monitoring discourse, a post to the mailing list will say, Hey, I've sent this. I've posted this over here. We'd like to discuss it there. Okay. Excellent. Okay. DevOps radio opportunity. Yeah. So, um, cloud bees has given us an opportunity to, um, to speak on the DevOps radio with their DevOps radio. So basically I'm reaching out to our governance. Uh, board and see who would be interested in participating. In, um, this opportunity. I think it's projects and visibility. It's been a while that we've. You know, we. We had an opportunity to build awareness in terms of that's outside what the great things that within the project that's been doing, but outside of that beyond, you know, the, the blogging and the tweeting and the LinkedIn post. So I thought this would give us a really good opportunity to get some visibility on Jenkins and get some interest on Jenkins and. For people to talk about, you know, what's the latest and greatest things about Jenkins? What can people look forward to and such. Good. I like that. So, and do you have a timeline on that? Um, I do not at the moment. So, um, I think once I have volunteers, then we can set up a time with DevOps radio. Um, just want to make sure that we give our participant or our speaker appropriate time for preparations. That makes sense. That's, that's great. Thank you. So this is DevOps radio is a podcast kind of thing that it's an audio only experience that people, people attend. They listen to it at any time, just like any other podcast. Correct. Cool. Thank you. Okay. Anything else we go ahead. Yeah. So one last item, Mark is, um, Calbee's also has given us an opportunity for, um, um, PR, not pull requests, but press release opportunities to speak to, um, analysts or, um, yeah. So they're asking for a spokesperson in case we do get an interest. Um, in the past, it has been KK, Tyler, Croy or Tracy Miranda. So we might want to talk about who should be the Jenkins spokesperson in case in the event that we need one. Yeah. Good, good question. So that feels like to me, we'd probably need a, that question would go to the governance board, I would assume. Okay. I think we should ask the governance board. For their, their preference, you know, I could see easily see Uli or Avelina or Gavin or Oleg, any, one of those four members of the governance board being a very reasonable spokesperson at any time. Right there. I think they're all well aligned and understand. Um, but, but I suspect they would also want other members of the governance board agreed that it's okay that they speak. Got it. So I can, I'll send on email to the, um, the board mailing list. If that's okay. Uh-huh. All right. Great. Thank you. Yep. Yeah. There was, I mean, there was some, there was some talk after. After the Oracle cloud thing, um, there was some talk that it would probably be best if we had CDF act as our press release coordinator slice source, but I don't think we came to final that it's still, um, governance board needs more discussion on the topic. Right. Great. Right. Yeah. I know that they, CDF can help us with press releases. Announcements, but with like a spokesperson, we haven't really discussed that. Got it. I see. Okay. All right. Anything else? No, no, all good stuff. I'm, I'm good. All right. Thanks a bunch. Thank you, Mark. Go ahead and end. And I'll upload the recording later today. Thanks. Yeah. This says. I am, am I still recording? Yes. It shows that you're still recording. Okay. It is. Okay. My thing did not say that. So. Thank you very much. That's the end of our session. Bye.