 Okay. Hi everybody. Thanks for joining today's Jenkins Advocacy and Outreach SIG. Today is January 11. On the agenda, I have GSOC 2024 update, change Twitter to xunchenkins.io and FOSTA 24 discussion. Is there anything else that we should add to the agenda? Not that I know. Awesome. All right, we'll get started. So the two action items that I carried over from our last meeting was, and these two items are still work in progress because I foresee that it will continue to be a work in process for a while. So as to continue to recruit GSOC mentors for 2024 and then our FOSTA logistics. So that's going to be ongoing for another couple of weeks at least. So GSOC 2024, I am planning for a January 25th Jenkins online meetup to discuss how to prepare your proposal. And this will be dedicated to the new contributors, potential contributors. So I will be circling the slide deck or that this week. And then we also need to scrub and finalize the project ideas list. I know that's also on Chris's to-do list as well. I know they are thinking about it. So we need to work on that. And then an important milestone or date that is approaching for us is mentoring org application that will begin on January 22nd. And I will be driving that effort as well. Mark, you have a question? Yeah, so one of the one of the on the scrub and finalized project ideas list. I've certainly got an action that the get, plug in, use, bear token authentication probably will drop. And I've got to do the back end extension indexer create. So that one feels like it's, it's viable, but I've got to do a prototype or at least do some exploration before I can be comfortable putting it on. So one, one is going to drop the bear token thing doesn't look like it's viable to me. And the back end extension indexer looks very much viable, but needs a prototype. Okay. Great. Thanks, Mark. I think I was from for GSOC 2024 before we move on. How is the activity on the on the social network? So do we see positive activity or I'm seeing actually a lot of activities. So yeah, be ready. I think, you know, just like previous years, their people are asking, they're interested, how can they contribute or, you know, where do they get started? Where do they get started? So, okay, so there is interest. Yes. Yeah, I'm not sure I'm seeing as much traffic as we've seen in years past, John Mark. But, but again, every year is different. And, and every pool of potential contributors is different. So there's activity around. Well, I'm looking that from too far to to judge correctly. I see indeed activity to. So reminder, Alyssa, I'm trying to follow as much as I can, but I expect Chris or you or Bruno to shout if I need to jump in specifically. Otherwise, I'm just. Yeah, in the back seat. Yeah. Got it. Thanks, John Mark. And then the next item I have is. So, I'm on the Jenkins.io homepage at the moment at the bottom here. I think perhaps maybe we change this to letter X to the X logo versus Twitter. Just, just something that is all minor stuff. I think I hear it's a good idea. So I, I confess though, I'm, I won't understand if I just see the letter X there, could we put Twitter slash X for, for those like me who, who think that the choice of X as their, as their name confuses me very terribly because I happen to have a thing called X windows running on my Linux computer and I have quite a number of other things that use X in their name. And okay, not everybody has that problem. Not everybody has ancient experience with old Linux things, but, but for me, replacing with just X is short. Yeah, yeah, it will be unclear. My, my recommendation would be there to paraphrase the newspapers that that's a X previously known as Twitter. Okay, that that would be fine. Yeah, I think we have enough room there. Go ahead. So this is showing the image of the X logo and what is the X logo that part I understand. But that place you were showing on the on the Jenkins site really doesn't have a great facility to put the X logo in right if we're going to put the X logo in we should probably put the Reddit logo and the GitHub logo and and so I think, I think that's just words right now and words and hyperlinks and putting a logo in there would be a little unsettling at least for me. Okay, yeah, and I think it's fine. We put, you know, Twitter slash access. The other way around. Yes, yes. Okay, people might get upset and these people are powerful. Okay, and Kevin also wrote in the chat X formerly known as Twitter, but also he wrote like Prince I didn't know Prince used to be called Twitter, but anyhow. Because X of course is an unpronounceable symbol just like Prince's new name is an unpronounceable symbol that's good. Thank you, David. Okay, so do I speak with Kevin about this or what do I do. Yeah, I can help out with that with no worries. I think you just put the action item on Kevin to propose the pull request for the change because he'll go figure it out. Okay. Let's see what other projects on doing. Right. And that's a good Kevin's Kevin's exactly well suited to that kind of thing on the on the dock side look, look to see what how other people describe it how they say it, because other people other projects have the same exact challenge. Right. Okay. Great. Thank you. Thanks Kevin. Okay, so foster 2024 are just to know our. Our stand usually is on the second floor of building K. This year we are at the bottom of the first floor. So once I believe once you're, you go through the entrance were towards the back end of the building. Please. Yeah, sorry Bruno for for your remembrance. It's under the stairs leading to the to the to the to the first floor, as we've seen your so second. Yeah, I see now. Thank you. Yeah, yeah, not far away from the bathroom. Yeah. So Bruno, I'll, I'll catch up with you via slack, but I should be able to help you with all the setup and all that stuff to get ready. On that subject the list I can report that the logistics. So the different sending of stickers and other material arrived at my place correctly as I discussed that with you. And I already know who's going to make the cab driver on Saturday morning. To to build a stand. I'll exchange the boxes. Yeah, on during the contributors summit and congratulation for the new t-shirt design. That one, the beekeeper is a donation from cloud bees. Oh, great. To donations one from cloud bees with our beekeeper t-shirt the design and then the other one I believe it's just a plain Jenkins the generic logo and that's donated by CDF. And some socks too. So we got t-shirts and some socks. Yeah, the socks, the socks. It was a terrible thing for my dog. So I had to fight to protect them from the over enthusiastic interest from my dog. Okay. And has has a price as a selling price been set for the items. Do we need to discuss the selling price here is that already a standard thing. What we've done in the past as we walk around to see what others are selling it for. That was my point. Yeah. Okay, so competition based pricing that's very good. Okay. We have some some very good people very smart on these kind of things that are going to react very fast on that. So we all agree that the collected money goes to the Jenkins fund or is it worthwhile to give a word on that. That that was my assumption that's what we've done years past. Yeah, I was assuming now how we do that transfer. We'll do it better this year than we did three or four or five years ago when it sat in someone's basement for multiple years. Let's get the funds transferred to the Jenkins account promptly if we can. Yeah, last year between smoothly, if I remember correctly, very good. So I think with this year with you being there, Mark, you will, you will be the keeper for that. I thought we had Bruno planned. Yeah, but that you chimed in and say I'll do that. So you might not be there. That was the plan. But since you'll be there, I am happy to take care of that. That is a very reasonable thing. I am happy to do that. If there was a fee because of the currency conversion, feel free to reach out so I can do that without any fee just in case. But maybe we have to give the money in dollars anyway. We have to donate the funds in dollars. Okay. And therefore there's going to be a conversion, a currency conversion process somewhere. Yeah, if it's me or somebody else, somebody will have to do a currency conversion. And Mark, we'll take care of you if you get stuck at the border with a huge amount of money, huge cases full of money from t-shirts. So we'll explain that. Right, right. If I cannot import more than 10,000 US into the US without paperwork. So we must not sell more than $10,000 worth of items. Okay. We need to tell Stefan. Okay, I'll stop the nonsense. Sorry, Alyssa. So the last item which we have, Mark needs to sign off or he needs to hop off in about 15 minutes on Mark. So I thought we'd talk about the contributor summit, the format agenda. This is a topic that raised quite some discussions and where I have very mixed feelings about. So the current format, I can show the paperwork. Do we need to run in on the details of the contributor summit or we just talk about the agenda? I think we can talk about only about the agenda, right? So the general principle of the agenda is that and what I proposed to the first circle of reviewer was that we start at 10 o'clock in the morning. Because this is when the meeting room is made available to us officially. And the morning, so the hour and a half of the morning or little bit bigger than that will be spent on know each other presentation of the day. And a review very short of the different officers. The officers talk, I try to steer that as much as possible because it can very easily get boring is not to look backwards, but to look in front. So what do the different groups, SIGs or officers plan to do? What are the challenge? This is normally to trigger discussions later. That's inverted from what I usually present. So it's important that you set it that way. I usually look backwards and then rely on the rest of the meeting to look forward. I like that. So you're saying look forward as the first preference. Okay, because normally most of the people attending will be will already know if they read the Jenkins newsletter and a little bit knowledgeable about Jenkins. We just need to do a very short refresh where I'm more personally about here officers are free to organize that as they they want. The format that I proposed, but it's still open is that either we do a formal presentation, which is a lot of work to prepare to get efficient information in a 10 minute format. So the format is 10 minutes presentation, five minutes buffer and probably a technical break in between allow people to stretch their leg shortly. But I tried to keep that as compact as possible. The other format that can be used is that we have a the the way it would work is an interview like of the officer where we give prompts and eventually a control. That's what's the English word for that is as an orchestra conductor, where we keep the time correctly and we can guide the officer in the direct the general direction, depending on the cues given by the audience, either by this particular topic, or they get excited by this other topic we can then dig so this this interactive format could be powerful really depends on on who we're we're talking to. Now, this was my proposal, because I received a limited amount of classical communications for a contributor summit. And the one that I collected and the people that stepped forward and I'm thankful for those will be for the afternoon so I at noon I have foreseen one hour break, because we're going to grab a sandwich nearby and eat stretch legs smoke cigarette for people that require that. Oops. Oh, yeah. But the afternoon so from from 1pm to 5pm. This is where we'll really dig into the more technical presentation. One is about the changes that have been made to Jenkins in order to implement a high availability on the cloud B side for CI so some some interesting technical things there. The second topic is the debates on debate strategy and the difficulties account encountered to remove blue ocean, which was from the base distribution from Jenkins. This was announced already sometime ago, remember in Lisbon, Portugal. This must be before the COVID long long time ago. And now we need to take actions for that. So there's the third presentation, the second presentation, the third is about the directions issues and opportunities for the user experience where a lot of work has already been done but there is some interesting things that could be discussed and where the audience can interact in the afternoon is much more debate triggering explaining things. And then we have fourth is more general where we will open the discussion to any topic that we heard during the networking in between. We plan to finish a little bit before five o'clock in the afternoon and give either. So two possibilities either people are completely jet lagged board or tired and want to get a change at the hotel or or just take some some fresh air, or people can stay in the court or places where we can stay and we would then organize a coding session or people knowledgeable we can start interaction is still a bit obscure to me I know what I would like to do for my personal plugin and the type of advice I would like to get. I need to get a few people in probably will ask basil to lead that that effort. And then we go together for for a networking event so we go together to restaurant which is about 12 minutes walk time so this is what I proposed. The reactions have been that first where there were several ideas that were thrown on the table. I have my personal opinion there. But I'm happy to to discuss that and listen and let other people decide but I made with what I had available and try to have the best program with what I have first comment was why not start earlier. So that we could have a longer break. This is indeed a good idea but there are two practical problems for that the first one is being that room is only available at 10. The second one is that the lunch possibilities nearby are scarce and will be difficult to time correctly and so it's easier to just let people go and grab a sandwich nearby so logistically and I think Bruno knows also the place. It will be less invasive that that way so this is why I propose it that way so personally I am not in favor. Or or stuck the other comment with which was also interesting and worthwhile was that why spend so much time on the officers presentation. Which is a good point so first I believe that the office so I say what my point of view is. Well now to be honest. Officer presentation can be boring. And the person wanted to have more beefy or more interesting or technically oriented presentations for that. A first comment I have with that is officers have an important role. I think we need to give them the opportunity to present it and expose their challenges for the future so I believe this is important and more practically. I didn't have any other presentation proposals. For that so it's it's interesting to say well I want more technical presentation debates or whatever I just tell me and I'll organize it so. This is this is the state so I organized everything with the current. Thing and what was the last I don't remember what were the. Basically in a nutshell. There was. An expectation to have more profound. Future oriented discussion technical presentation or whatever so I say well. Tell me do it so. So back to you Mark then for your reaction or if somebody else in the audience is. Yeah this is the state of the plan so I like I like your guidance I appreciate very much your guidance. Officers we want to be sure they have some time and charter them to do look forward rather than backwards that that feels really good. I think the blue ocean deprecation and the you use you X the three topics you identified. All feel like very very important topics for for the project so so for me that that feels good in terms of. If we could shrink the the officer presentations to be less. I don't see any shame in that if they can get their message across. Replaced by what so this is 10 minutes is already short in challenging knowing me for instance if I had to do it in 10 minutes I would die. Exactly well and and for me more challenging is the replaced by what question and the the open thought on my mind was. Possibly replaced with free time at the end of the day for group coding exercises as discussed right if we were to accelerate the arrival of group group coding time. By just 15 minutes that actually could be quite valuable but but that's a that's a relative because we'll all be physically there. That's a thing we can be we can be elastic to. On the day of the event hey get get done quickly with the officer reports and with the look forward and get to the the meaty topics to the to the significant and relevant topics very quickly yeah. Yeah. So I don't see that I would change anything in what you're proposing John Mark. Okay, so well it's reassuring. My experience with these kind of things and this is why I would like to to start with the officers in the way I'm going to introduce it will be very strong. The point is that the planning allows some improvisation depending on what topic we capture, and this will be your my responsibility to take the opportunity of some free time during the afternoon or where we can arrange squeeze something or so or even in the morning. And so I'm ready to to and I think it will be necessary to adapt the presentation depending on the I really want to grab opportunities. And I agree and I think you've you've said it very very well, you and I will be there physically, and we will certainly intervene to try to make that meeting as effective as we can, based on already the preparation that you're doing and that you'll continue to doing as we do as we get closer to it so for me I think that's a that's a good assumption and a correct plan for us that we will adapt the agenda as necessary while we're there. So why this this the spirit, I might reach out to you personally and also with the officers that different formulas I don't want officers to feel because doing such a presentation 10 minutes is challenging. There are other ways to do to do it. Maybe we could. I have several ideas trying to optimize the time and the purpose is that it's not a boring experience. Anyway, if I see somebody fall asleep, I will wake him up. So this is the the planning. And I apologize I have to drop off for my other meeting but I think I think you've got the right right approach, we can talk about it separately we can also talk about it in the advocacy channel or on, you may be even better on the community forum and say we're here's where we're headed. This was my question about the next steps with that proposal, can I move ahead in the next announcement. So one will be a blog post, maybe waiting first to do the community and give opportunity to the audience to interact with that and then I'll do a blog post to I like that I think that's a great that's a great way to approach it. Absolutely. Okay, so if you agree with me, then I go ahead but I'm ready to listen to comments or. Thank you. Thanks very much for what you're doing. Alyssa, I apologize for having to drop off. Thanks very much. Thanks. Thanks, Mark. Thank you. So, John mark, perhaps. So I think who attend the contributor summit is will kind of dictate our agenda. That's how I see it. And I've I've been to enough contributor summit where I've seen both spectrum right so where we had a full room of let's over 50 people that just wanted to sit and listen. And then we also have a room of let's say less than 20 people that are heavy Jenkins contributors. So I think if if it helps, you know, so we know that the room is we're limited to the 30 capacity. And then if we take, I know that you've already started like the register or you know who's going to be attending the contributor summit. But we, if you want, we can set up a form and people can, you know, sign up register as as you will. And then they'll give you an idea like where our agenda should be in advance. Yeah, yeah. Try to steer that as much but no as a military know that plans holds just the first minutes of the battle. So we have to adapt. Exactly. Exactly. And I think Mark has been there and often enough and he I've seen him just, you know, throw things out there on the fly and it works out just perfectly. And it will be perfect. Don't worry. Yeah. Okay, that's that's good for me I'll work out with you the logistics part because at a certain point. I need to know how many people will join us for the evening dinner. Okay. Okay, I need to confirm the numbers. Yeah. Okay, that's that's it for me. With the community post I published the link to the different work documents so people can review them. Okay. Sounds good. Thanks. Thank you john mark. All right, thanks everybody. Thanks for joining. Thank you. Oh, I'm sorry. Hi, Chris. I'm here late, but I've been wondering if you have to confirm the time for the January 25. So that will be the same time as our previous one, which is eight a.m. my time and your time. Yeah, so that will be really late for you as usual. Yeah, it's kind of like, I think it's night but not too late though. Oh, cuz like harsh has been asking about it because I need to tell him in advance so we can make arrangements to attend. Okay. So is that okay? Is that time okay? Do I should I change it? I think it's okay. Yeah, it's a good time.