 Hey Mark, can you hear me? Welcome to Advocacy and Outreach. It's the 2nd of December 2021. So agenda topics, adopt a plugin, upcoming events, advocacy budget, Google summer of code, and Jean-Marc's asked questions about measurement and what kind of data we might need in terms of measuring the health of the community. Any other topics we should put on the agenda? None for me. All right, so the adopt a plugin initiative is now, let's call it modernizing plugins, and the development is ongoing. Ideas keep getting captured as we capture them. We'll eventually place a developer tutorial on www.jankins.io and Jean-Marc has kindly agreed to be one of the reviewers. Thank you, Jean-Marc. Yes. Then go ahead, Jean-Marc. No, and I am starting to rehash my experience with a new plugin started today, so it will be very welcome to cross the experiences. Great. All right. Thank you. Well, and would you be willing, I may be able to give you access to a site that looks like the tutorial, but is hosted separately. So maybe we should try that with you. Mark, provide a link to a copy of the tutorial, because I think that might help. Yeah. Great. All right. And especially before I take any initiative to improve existing documentation, because if it's already done. Well, and this may also let you contribute to that repository, so to that pull request so that we get your content into it as you learn things and improve them. Great. All right. Next topic then, upcoming events. Alyssa. So, Fostam, I reached out to the organizer. They do not have the plans for or any the dates and such in terms of, you know, when we can submit our information for the stand, but I'm waiting for that to be available soon. They're telling me that it will be available soon, so I'm monitoring that. And then I will also reach out to Olivier with regards to the CICD dev room and try to get some Jenkins sessions in that dev room as well. So there was discussion in the governance meeting on Wednesday, based on experience last year and experience in other conferences that we may not want to attempt to stand. Uli described his being present at last year's stand for multiple hours and having no visitors. I'm wondering if we just declare that for this one, we're going to focus on talks, talk proposals for the CICD dev room and involvement in other ways, but a stand may not, doesn't seem like a good use of the time of the people hosting the stand. Right. Do you think it would be worthwhile that we still have, so I think the pro about the stand is that it allows us to list out a lot of our content along with other exhibitors. Now, we don't have to post it, but I think it would be good to get some visibility there in case if somebody wants to click on, you know, something about Jenkins, how to contribute to it, things like that. Okay, so there's what you're saying is there's more value than just whether or not people actually visit the stand. Yeah, just I think having that virtual presence there with offering, okay, these are the content we have, like giving them a place that they can go to for content, not having somebody to having to virtually sit there and host it, I think that's fine. We can eliminate that part, but the other part we probably should have there, space for valuable content to place on their site. Okay, so that feels like a good compromise. Can you keep on that and work a proposal? Great. All right, so finding that compromise, right? That's great. Okay, thank you. All right, talks for the dev room. Yeah, and I agree, Jean-Marc, you're right. We should promote this to the dev list, right? And we should propose our own talk ideas, right? Multi-talk ideas. Two comments about that. The first one being we need to, before we promote, we need to have a better view on the dates for the request for paper. No, it's the deadlines. Yeah, the deadlines for submitting the talks title, CFP call for paper. Yeah, so I'll gather that information and I can send that out, Jean-Marc. Yeah, so we know when we start doing noise on the various lists, but rereading this, I think maybe we could get people prepared. The other comment I wanted to do for our talks, we should start to build some kind of a talk ID repository or dump or lists or if somehow to have a set of presentations that are either ready or good ideas that can be explored or I don't know if I'm clear in what I'm trying to explain. Yep, you're clear to me. I understand. It makes sense. So if we collect subjects, I know that Gitpod is a good experience. A good experience is also what it is to modernize a plugin. These I know how to mount, but I think it would be a good idea to prepare a list of subjects we can. Oh, this is a topic that would be, well, and somebody comes along and starts filling in ideas, putting a couple of slides. And so depending on the audience, I started a page listing and that I need to find it back. Those sound great to me. They really do. Anyway, this is one of the things we can discuss together offline, but we need to get prepared so that we don't have to scramble to find the subjects. Right. Now the CFP Olivier said that they only just, Olivier said at governance board meeting that only just a day or two prior to that meeting was when they were confirmed that they were authorized for the dev room. And their deadlines have been compressed because, hey, it's coming very fast. So he indicated that, yes, we do need to be aware and yes, calls for papers will be, the opening will come very soon and will probably be much shorter than it has been in the past. Okay. All right. I think we already talked to the booth availability topic ideas. So, although she called Africa, that might be a good one to encourage, right? Invite some of our contributors. Good idea, Jean-Marc. And there is the swag part for the booth, but we need to see the logistics of it, the stickers. Right. Oh, speaking of, I've got, yes, thank you. I've got another advocacy budget topic, item topic. So swag for Professor Andrew Myers. Yeah. And just putting on, okay, go ahead. Anything else on Fosden? Maybe when we discuss together, Alisa and myself, that they were sure that we covered the different subjects. A lot of material here. Yeah. Okay. All right. Scale 19, March three through six in Pasadena, California. So it's still holding in person, right, Alisa? They haven't backed off. They haven't converted it to something else. They haven't canceled it. Correct. Still in person at the moment. And you made a submission for our, for a session. I spoke with the organizer and they said that they're trying to see how they can accommodate the virtual speaker plus a live speaker combination. So that is TBD at the moment. And then I am, I'm also working with them on a training room. So the, the initial discussion was that Saskia, Colby's events team would pay for the training room, which is about $3,000. So Saskia is away at AWS at the moment and there's been some changes. So I need to figure out how that's going to work out with regards to budget. Okay. So that's, so there's, there's a risk that we may not be able to do that if we don't have funding for it. Makes sense. Yeah. Yeah. But regardless, we should, we would still have the booth, the stand there, and that it would still be for free. I'm, I've yet to hear otherwise, but still working out the details. Great. All right. Okay. Advocacy budget items. So Alyssa, you and I are working budget requests at still open as far as I know. And I did get a request for a suggestion. So Professor Andrew Meyers is a professor at, oops, is a professor at Cornell University who maintains the condorsed internet voting system. Now you may say, what's the condorsed internet voting system? Why would I care? And why is he involved in Jenkins? Well, condorsed internet voting system, CIBS is the way we host our Jenkins board elections. Okay. And he had to do some work the day before Thanksgiving to bring back a failed system. And we thought, oh, you know, what it would be nice to offer him if he would like it some swag. Is there a way that we could do that if, if, is it, is it feasible if I can get his email address? Could, could he be registered for that? Yes. Can we give him the, the, the contributors swag package that we were, okay. Yes. That would be the, that would be, yes. All right. Yeah. I can add him to the list. And if you can just add his email address there and I'll take care of it. Yeah. And I don't have his email address yet. So all I've got connection with him is a Twitter account. And, and I'll, I may have to call him on the phone or, or something to ask for that because email address is sensitive, right? Many people just don't want to share it. So, so then Alyssa will, you'll share, you'll do the next step. Send the invitation for swag. Great. Because he, and he may choose governance board noted, hey, he may choose not to have it. He may say, I don't need, I don't need any, any acknowledgement, but it's a nice thing to say thank you to, for what he did for the Jenkins project and he really did something very positive for us. Yeah. All right. That's all that I had on budget. Google summer of code. So here we, it was discussed, it was agreed in governance meeting that we are all, we are, we are doing Google summer of code, but we need, Oleg will probably not be available to help in many ways at all. So we will need leaders to take the, to run the program, etc. Don't forget me that. Right. I don't know what, what swampy grounds that can turn into. This is definitely something I have on my radar to get involved in. Excellent. And Alyssa, I think you're also willing to be involved. Is that right? Yes. So if we could work together, yeah, and pair that would work out. Yeah. And getting, this will be, there's a promotional part of this where we've got to encourage people in the Jenkins project to suggest project ideas. There's a, a technical component where we've got to update the Jenkins.io website to show here are the new project ideas for 2022. And then there's a promotional part of this of announcing that yes, we are in it and a coordination piece talking with CDF. Right now the, my assumption is we'll still do it with CDF, but I've got to double check that with CDF that they are interested again next year in doing Google summer of code. So, so maybe Alyssa, you can check with them. Oh, that would be great. Thank you. Sounds easier when we're pairing on a problem than having to push it low. Yes, yes, it is. One is a lonely number. Yeah, that's true. Very well said. Three dog night. It's been a long time since somebody made a reference to that song. Well done. It's a song then. There is one is the loneliest number by it's an old rock and roll song from long ago. Okay, so I, Jean-Marc, given my schedule, I'm prone to say, hey, I will pass control the meeting off to you and to Alyssa. I need to drop off to get ready for a next meeting. Or would you like to end for today? We just call ourselves done and we'll meet again next time. Yeah, just an update here and let's work more in depth later. I got access to not the name, but to some data sources available and have been browsing no more than 10 minutes. I need to make more time available there so that I have a better ID there. And then I suggest that we start looking at it together. Alyssa and myself and you, Marc, definitely, but that we start to brainstorm on that first, what we dream of and what is available and that we know what is the gap and what kind of plan we can work out to better understand the audience. Excellent. Thank you. Yes, that sounds really great. Okay. I'm still reading books on this. Right. Any other topics we need to discuss? Okay, let's call today's session done. Thanks very much and I'll post the recording probably within 24 hours. Thanks, everybody.