 Welcome, everyone. This is the Jenkins advocacy and outreach meeting for the 26th of March, 2020. Let's review the agenda and then work through it. So I had put on the agenda, zoom accounts as a possible topic. Assuming that that's one for discussion Jenkins area meetups Jenkins roadmap, Google summer of code and case studies. I'm going to pause as possible. Are there other topics or any of those topics that should be deleted? I've got a couple of topics. Just one is I wanted to just highlight the Twitter analytics and what I think is a next step we can take. And then I noticed as Jackie's here, I wanted to highlight CDF Ambassador program and also kick off a discussion because I've been looking at it. And I think there's some scope for kind of taking what we had as the Jenkins Ambassador and kind of evolving it to be part of CDF. But there's a few decisions we need to make or discuss. We might not have time today. I don't know. Go ahead, Jackie. Yeah, I think maybe that that we could do like a separate call on on what we wanted, because I know Jenkins has an Ambassador program and I'm going to assume that maybe spinnaker and maybe Jenkins X already has them so I know we had discussed figuring out like how do we identify the ambassadors by specialty. But I, yeah, let's let's have a separate discuss let's table that one and have a separate discussion I'll set it up. Um, because I do want to get I want to figure out how do we really leverage and make this a robust program. And I don't want to step on the community's toes I actually want to integrate them into it. So, let me I'll set that up right now. Okay, yeah, I think that sounds good. It's probably a wider topic than we can cover. I think we should add to the list to get an update on the talked about a store and getting codes to give out to people when they do something good and. Yeah, so I, sorry, Markey, I think I might have missed you. But I sent that. Can you hear me rather we can we can hear you just great I just wanted to gather all the, all the topics and sort of before we actually execute. No problem. I'm just, I'm just trying to beat because we've got Tracy only for a limited amount of time I wanted to be sure we get the hot topics on the top of the stack. That one I think we could, we can we can certainly do it but it would be okay if we did it later in the meeting even if Tracy is not here. Okay, so CDS store at the same time. Oh you do okay well so then then all right so that helps guide the prioritization. Okay so Jackie you you win the prioritization challenge good okay. Are there other topics before we get before we go crisply diving into specifics. Okay. To the bottom of the agenda. Okay. Great. All right, and I think we can sort them so that we've we've already covered CDF ambassador so do we take CDF store first then zoom accounts then Twitter analytics and let's go onward. Okay, so CDF store Jackie. So I created some discount codes or pinnacle already created some discount codes I sent them over to Tracy. But I think that I need. Let's talk about it more because I think if I need to have them create more for you guys just let me know. And then I can send over the discount codes and you guys manage them. That's a good start so Maki. I think Oleg and I have in our inbox some codes. What do you need like is there someone you want to go ahead and send that to how do we want to manage it. I had one person that I wanted to send just want to. But maybe in terms of processes maybe we should have a. I think we should have a different sheet where we can mark them off and like who you who who took it in terms of which one of the advocacy people took it and then who did you give it to and then we mark it off. I don't know sort of use the honor system on that I don't think that may be the best way to do it that's how we do it in in the Kubernetes community. Yeah, that's fine I can do that I can. I think I only had like 10 cent created but I'll have pinnacle create more and basically the way it works I don't know if I reviewed this with you guys yet, but basically like say you wanted a pair of spinnaker socks. You just give them the code for socks and it's a one time you use only and then they go and use it and it gets shipped directly to them. So we cover the cost of the socks and the cost of the shipping. Do you have something Jackie or is it like Mark if we just do you have an existing spreadsheet we could just use if it's something with other communities could just make that. I do think I don't personally have a story was that a question for me. Yes, I was just asking if you if you already had a template we could just adopt and I could easily I could easily make it up and then I'll share it out. I will make it only available to the people that I sent you so you'll get it to your email so we don't open it up to the community. I could have that done by the end of the day. Oh, the codes and oh you have one so I have I have I already have an Excel sheet that pinnacle shared with me so I'll share it with you guys. And then I think all we need to do is probably add a couple more columns to like who received it who gave it away. And then but I'll just share it with you guys right now and then what I'll do is I'll have pinnacle continue adding the discount codes to that same Excel sheet. And then you guys have access to it and then it'll like you said it'll be an honor system and we manage it that way. I'm going to put up a document that I'll put somewhere that we can look and you can see how you actually use it so we just don't assume. Yeah, and that's what I was going to say it's like, do we want to put some guidelines around who we give it to and tracking and all that kind of stuff. I'll create a document and I'll make it editable with the team here and then we can go from there. Yep. I won't give anything I won't give any of the codes out until everything is all agreed upon. Okay, sounds good. Thank you very much. One comment about the park. So my understanding of it now we use the code so basically we send a pair of socks to whoever receives it right. It would be nice if we could use maybe a pack so let's say socks couple of stickers and kind of thank you message or letter, because it would be a bit more efficient. So, do we have an opportunity to have something like that in principle, or We, let's talk about maybe creating a separate kit for that. Because I, and then we can what we want to talk to pinnacle about is actually creating a code. And basically that code is for like, I'm calling it like the ambassador kid just as an example. And then it comes in a box that's all branded with our design. And then, like you said, it has stickers it has socks so just let me know so that we can get it created because I think that if we do a bunch of codes. That might just be a little bit more tedious. I think the handwritten note might be a challenge because it's basically people in a warehouse putting all this stuff together and shipping it out. So it's not part of their offering service to write a handwritten note. Yeah, hundred and notice not something required. So for example, we can just come up with a letter on our own. Yeah, maybe we come up with something generic that they can print and just sent out. Approach it. I'm going to suggest things slightly different when we award the code. We just do a nice kind of thank you and I think we're biasing here to just keep it as automated as possible. So while I do think hundred notes have a nice touch and even printed messages I think the more we can make it efficient and keep doing it the better. So, yeah, maybe it's something like Jenkins contributor certificate or whatever. So you can put it on a wall. But yeah, I agree that you can basically deliver it separately without a park. So just if you can print. Yeah. All right, anything else on CDF store. Nothing for me. Thank you, everyone. Next topic then zoom accounts. I said I would follow up on this I haven't and I still have it on my list so I will try to do that and thank you mark in the meantime for giving us a stop gap solution using your own personal zoom. So Tracy, sorry, what's the issue with the zoom account do you guys need access to like the CDF zoom account so that we could schedule these meetings. You have access but they seem to be a lot more overlap now and so we run into clashes so we wanted to have an independent Jenkins zoom account. We just use for all the stick meetings do you saw. And we know that we're not we don't have to look at the CDF calendar when we're scheduling. Yeah, and we had some cases when the account was locked even if there was no official meeting on the CDF calendar. For example, it was a case for Jenkins online meetup one month ago. And basically I finally had to interrupt the meeting because we had an announced online meetup with people waiting. I don't feel bad about that. But yeah, we have no way to continue to access the single account reliable right now. Okay. Okay, I'll also follow up with that Dan to see if we can come up with a solution for this. Okay, yeah, if I leave that with you Jackie you're probably better place to chase up then than me. Okay, I'll change. Okay, thanks. I assume that covers zoom accounts next was Twitter analytics so Tracy I believe you had that. Yes. Yes, so I know this is something Mark had brought up when he first became a contributor which is basically you know how can we get feedback for the tweets we're putting out no active. Recently, there that so let X does have a way you can bounce into, you know, the number of impressions between and all sorts of different kind of analytics info. There's categories. And I think I shared a shot where I think the right ones is called an organic analyst to have access to all the data, but you can't necessarily roll pains and it's a bit add centric centric. And also short, I thought what should basically do is have every Twitter contributor who has to tweet deck should also be given access to the Twitter analytics. I know Tyler had some concerns in the past that you know it's important. These analytics are not used by specific companies or they always shared with the community and that data is kind of made open, and the output is used to help the community. So we have a caveat that people have that responsibility with the data, we then give people access and then maybe we added monthly to this meeting to look at that data and draw some conclusions and share that with the community. I guess. Alternate approach would be to just have a public statistics instance. Let's say something like remark lab. But it's much more complicated way. Just for reference, a thing I used to do is I used to bug Tyler every month to download the monthly report. And then Olivia would save it somewhere and then I would do some analysis but it was just too kind of heavyweight and relied on me bugging Tyler. So I think this would be kind of a better setup where people can go in, look at their tweets, see what's being effective see what's getting, you know, spreading the word and what's just kind of being ignored. So I like the idea because it at least feels like it's lightweight for my benefit I can decide if I'm phrasing things, if certain phrasing is getting better traction than other. It doesn't give us a particularly long term archive for it, but I don't object to that. Yeah, I don't know if access to that means we could download the reports ourselves but we can find out. So if folks are fine with that I will, I can just ping Tyler and just when he can get around to it if he can take a look and try adding us and then we can see how it goes. It would be nice. Speaking of publicly accessible Twitter analytics, we just hit 40,000 followers one week ago or so. So I'm not sure whether we need to celebrate it but it's definitely quite good number. I think that should something that should be like a tweet and it's well formulated nice hashtags in there and sent out. I think that will generate a lot of buzz. Okay. If somebody is ready to do that. I'll take action item. And if you want you can also tweet about 15,000 stars. Yeah, or I can do it. Can you send, can you, can you just shoot me a direct message with those numbers, like the 40,000 and the 15,000. I'll get something together and then I'll put it in. I'll put it in our. The advocacy getter. And if everybody approves then I'll get it shot out today. Okay. So we treat that today and Jenkins maybe next week. Yeah, nice numbers. Excellent. Anything else on Twitter analytics Tracy. Yeah. Okay, so next topic we had, I had put Jenkins area meetups there. Oleg is there anything you wanted to review with us on Jenkins area meetups. Some small progress with regards to meetups in Europe. I reached out to organizers to get feedback whether somebody is interested to organize them. We are planning one online meetup may be in May. So there is some progress, but it's the progress is definitely slower than I would like to. And the separate stream of work for me it's something we already discussed in this week, having an announcement for meetup organizers about COVID-19 situation and recommendation to go with show basically offering help to use our existing framework because we have Jenkins online meetup. We can host meetups if needed through zoom. So if somebody wants to organize online meetup we can help them by providing platform. So I have an action item to write it down, but after that probably we will need help from CDF to send a message to all meetup organizers, because without CDF we have no permission to do that. Yeah, that's the unfortunate part, even if I make you guys core organizers. So yeah, just let me know what you need me to send out and I can do that for you guys. Yeah, and I think it'll be what I know CDF we're having lots of conversations about, you know, virtual strategy. So I think this will fit in really nicely to that. So, yeah, just send it over to Jackie. So she's, yeah, that's something that's like, I'm trying to figure out how do I start prepping content to share with the meetup folks so that they can post online versus in person. So yeah, just let me know. Yeah, while we're here, Marky, I'm waiting for your abstract for Kubernetes and Jenkins online meetup. Thank you for reminding me. I'm going to write that down. Oh, Mark, not on this topic, but I just remembered another topic I want to sneak in if I can. Yeah, so this is just a very early. So something we're doing in CDF now is there's a kind of subcommittee of the outreach committee which is focused on projects. So one thing we're driving there is like themes around the newsletter. So I've got on the hook to create a GitHub repo which sort of sort of outlines like, you know, April's theme will be this may seem will be that. But then what we're looking for is folks to write specific articles and suggest future themes. Long story short, I think in May the theme is going to be ML Ops. And I wanted to see if we could find somebody who could write an article on Jenkins and ML Ops and if there was somebody who was running like a GSOC project which had ML Ops in it and I don't know if there's anyone in the room like that. Long story short, if there was some Jenkins and ML Ops angle that we could do as an article I wanted to just pre-see that in people's heads so we could find some authors or something exciting we could contribute to that newsletter. I may know somebody. Yeah, and there may be weekly meetings. We'll use regards for that. So let's see whether we could do something. You're also ambiguous with the May thing. That's great. I love that. Excellent. We have even an organization which targets that. So let's see whether we could facilitate it. Yeah, so just early I'll have better dates and I'll soon have something we can reference but I just wanted to see that so people to keep in mind as, yeah. Okay, so Mark, is it fine if I add an action item for you for that? Great. All right. Anything else on CDF theme of the month? Okay. Jenkins roadmap, okay. Okay. So quick update about Jenkins roadmap. Firstly, it's going to happen. Yesterday we had a Jenkins governance meeting where we approved publishing of the work in progress roadmap. So I'm assembling the pull request together and I hope to finish it by tomorrow. And it means that we will be able to publish it and then work with all special interest groups together items. And since we had the special interest group meeting, I would like to bring it up to everyone to understand what we would put to the roadmap as advocacy and outreach. So right now I put all programs there like JSOC, JSOC, the Potentially Community Bridge, Hard Turbo Fest for the future. But other topics we would like to highlight in the roadmap. Do you have outreach in there? I'd love to have that even if we can't necessarily commit. Okay. Not now. I can put it. Yeah, problem. Yeah, I can put outreach here. So for us, outreach is rather problem is financing of this program. But if you can find sponsorship, why not? Yeah, CDF can sponsorship. They could have sponsored it last time. I just think Jenkins wasn't ready with mentors. Okay, so I guess we can safely assume that we won't be ready with mentors for the summer season. We kind of make a call to double check, but everybody who's interested in mentorship is right now at the JSOC. Yeah, I think the summer deadlines have already passed anyway. So it's the next cycle for one. Yeah, outreach should be in to plan. Okay, so it basically summarizes what we do with outreach, at least with community events. Do we want to do something for advocacy? Talk to Alyssa about what she's doing on case studies potentially. Yeah, so I'm happy to put case studies on the road map. But yeah, I'm trying to limit number of items for each project. But right now I can put whatever we have in mind and then we will sort it out. Yeah, I'd say something like potentially the ambassador program as a next if we want to put that on there. CDF ambassador program, right? Yeah, well Jenkins evolution of the ambassador program to CDF. But if that's too fuzzy for now, we can leave it off as well. Well, it will be a living document. So it's not something we need to propose all topics by the next week or something like that. We will be able to add topics later. So once we have a road map in place, I think that it will take one to two months to have it finalized and to make it get announced. Once we have it announced, it's definitely something we could promote through CDF resources as well. It would be a major milestone for the Jenkins project to have something like a public road map in place. We have never had it before. Yeah, I think it will be good. Excellent. Thank you. Anything else on the Jenkins road map, Oleg? I'm waiting for feedback from everyone in the pool request, especially from ones who want to propose their own road map items. Just as my note, the platform special interest group met this morning and brought in six or seven or eight different items. Most of them already on the road map that draft that Oleg had proposed, but they agreed that they were good roadmap items. They included things like specific platforms, specific initiatives around JDKs, things that I think the community will find both interesting and useful. Yeah, so we can go through the drain dump stage and then we will align it. That's why I put one to two months before we do final approval and conciliators published one. Great. Should we go on to Google Summer of Code then? And Tracy, I think you and Jackie said that you needed to drop off. Thanks everybody. Thank you. Yeah, I do. But I'll follow up with you guys on the Summer of Code because I need to get caught up on how do I help out as an admin. And I think Tracy might have said that we would sync with Oleg. So just FYI on that, because on the CDF side, the ball's been dropped on this program. So we need to, you know, get it up and going and start helping folks. So yeah, that's, that's all I had to say about that, but I got to drop. So I'll follow up with you Oleg. Thank you. Okay. Chats on CDF Slack. Yeah, so speaking of chat, Marky, are you in the CDF work admin and mentor chat now? CDF? CDF? No. Okay. Yeah, I just asked whether we should invite Jenkins or Cardinans and mentors there because right now it's only me in this channel. It was created by Tracy yesterday just to facilitate communication on the work admin side. Is it a private channel? Yes, it's a private channel. If you can invite me, I'll definitely go there. There is public JSOC channel, basically equivalent of our public JSOC channel. There is also mentors channel, which is basically equivalent of our mentor and mentor admin, many of these at the same time. Okay. Yeah, I didn't, I didn't, I know about the public JSOC one. I'm in that one, but the private ones or the mentor one, I did not know about that. I feel there's a lot of we're crossing a lot of wires in doing that. Just, yeah. Yeah, I think you know what I mean. Yeah, I know. For me, focus until next Tuesday in the Jenkins JSOC, but I'm trying to help when I have some bandwidth. If you need me to help in the CDF one, I'll help you there if you need help. Okay. So let's move on to JSOC. Yes, please. Okay, so for JSOC, one major update. So we have regular meetings. So I will just provide quick summary. There will be changes in the timeline. So coding period will start in June. Community morning will start in May. Basically, it's back to the common schedule because this year the plan was to start a bit early. What doesn't change is student application deadline. So it's still March 31st, so five days. On the Jenkins site, we've got a number of proposals. We've got a number of strong proposals and hopefully we'll have a great JSOC. Obviously, COVID-19 situation also applies. So we've been asked by Google to increase mentorship capacity and to improve increased redundancy in all projects. So what we decided on the open side is to target three mentors per project as default instead of two what we had last year. And it will be a part of our student selection part in April. Regarding the rest, we got a lot of applications. You can find out some using the public materials. We have a Google Drive where we try to reference proposals. I cannot say how many proposals we've got through official channels, but we've got a good number there already. Any questions, comments? Everybody on this call already participates in JSOC. Yeah, I think we may have a little bit of concern with the Jenkins X projects. I guess there's some internal stuff going on. I don't know. I just found out about that yesterday. I'm forcing them to give me some more information because I find it extremely unsettling for students that have submitted proposals for this and have showed interest to just have them do, you know, proposals and then pull the rug out from under them. I find that not acceptable. If there is a cancellation, we want to know about it by tomorrow end of the day. That's what I've said. I've said that to Kara and Oscar and I said, I need to know this now. I told Oscar I need to know it by today. Well, do we have any applications to that particular proposal? Three that have sent them to me personally and I was in the process of telling them to submit their draft to the Google. But now I don't want to do that because that's just not okay to have them send it and then, well, I feel bad already that they've worked on something that may not. Firstly, if they already have drafts, it's better that they submit them because while the proposal is in draft, you can cancel it. This first item. Second item, we need to push proposals to draft or to discussions to it on the website. There is no certainty whether they happen. We need to move for them from published state immediately. I'll have them submit them today. One of the things that I find concerning is, well, I've done reviews. All of my reviews are now dependent upon James Stachin to do a review. I was not aware of that until yesterday that he has to approve everything. What? That's what I found out yesterday. Yeah. Yeah. And I'm okay with that. I just, I didn't know that beforehand. I didn't know about it, even though we had some discussions specifically related to that. Okay, so thanks for the heads up. I will follow up internally. But yeah, I can comment on the situation because I also don't have all the information. Great. Okay. Yeah, thanks for the heads up. So I am going to do a Oleg Oleg and I had a conversation earlier today that highlighted that we could benefit by more, more mentors in a number of places. I'm going to put out some attempts on social media to encourage additional mentors to subscribe to, in my case, the get plug in project ideas. But I think that's a general technique we should consider inviting more people or contributors because with COVID-19, we need more and more depth. We talked to those mentors about it several times. I wasn't pushing it too much in the million piece again because of COVID-19 because at some point people are not really sure whether JSOC is going to happen. Now I believe that it's going to happen. We still need to do some promotion. But yes, right now we mostly target mentors for the projects where we don't have enough mentorship capacity because we can do a final call for student applications. But let's be honest, there is quite low probability that a student to come out of the blue five days before the deadline is a great proposal which we are able to review and then which we will accept. It might be possible for projects where we don't have for good applications already. So I'm writing some messaging. Sorry, I'm behind all the action items. And I will be posting it in the million piece, but specifically for proposals where we don't have applications right now. Okay, so I'm not sure I understood that last, that the subtleties of that last comment. So if we don't have proposals for a particular idea, we want to encourage proposals in those areas. Can you clarify for me? Okay. So, yeah, the idea that if we already have applications in particular areas, when we internally can see that these applications is something we would like to have. So it's not something we can discuss publicly. Yeah, obviously, all the students and mentors already started reviewing proposals that they have their own preference list. And the next five years, we will be just doing this ranking and making decisions. So the current feasible strategy is to encourage proposals and areas where we do have applications. So that we may get applications there. And then if you have additional mentorship capacity or additional slots, it becomes more feasible there. So, yeah, if somebody wants to come up with proposal, any project idea is fine. But it's a question about what we promote. Because, for example, we can promote machine learning project now, please apply. But how many students and you already have market something something like 610. Too many students. Yeah, so. Okay, yeah, what's the point of promoting this. Yeah, that one is, is not. Let's close that one off. Great. Got it. I understand. Okay. There are areas where we're rich and areas where we aren't as rich. And so we want to we want to spread the wealth. Got it. Okay. Yeah, that's something like that. All right. Anything else about Jesus. We can move on. I have too many meetings. Yeah, so I propose we delete the topic that had case studies with Alyssa. She's not available. She could talk about it the next time she's here. Let's go to LinkedIn account. Yeah, one thing before we move on, Mark, would you be able to update statuses of Jinx sex project ideas. What do you mean update statuses. So push them from published to draft, or maybe even to pending discussion. Yeah. Let me talk to Oscar. The care is offline already, but let me talk to Oscar, and that'll decide it will get pushed to one of those that where is after will to be dependent upon that conversation, but I will have the PR in today for both of those. Okay. Thank you. Great. Okay, so I link it in. So, yeah, just to summarize from, yeah, I'll probably share the screen if you don't mind. Okay, do you see my screen. Do yes. Yeah. So, regarding LinkedIn, historically, we have an organization that he key has created it, maybe 2010 or something like that. So I'll just open my profile. Yep. So there is Jenkins project organization there. But this organization historically wasn't really maintained. So, if you go there, you can see that basically there is no posts. Nothing. My proposal would be to actually use it as an additional vehicle for outreach, because you can open the number of followers and it's something like, yeah, almost for Southern followers and in LinkedIn, we can actually do a good outreach. For example, if you talk about the Google summer of course and about other items, well, the ship has sailed for this year but still by doing LinkedIn promotion, we can have additional impact. Or we could just configure EFFT and just forward tweets there, again, additional three to almost for free. So I spent some time, I got approval from the governance meeting yesterday for me to get admin permissions there. I got admin permissions there because apparently AKK was owner, so I got it quickly. And now I just have some ideas what to do. But these ideas are pretty straightforward, I would say. Just to do some facelift to update the obsolete text, for example, until yesterday the page still include slave in the description. Yeah, so minor thing that it's fixed. You could set up some repos. One of the ways is to just approach Twitter contact management thing, another approach is just EFFT or something like that. The bonus my preference would be towards that because you have limited capacity. Unless somebody is a strong LinkedIn fan, because in my case I open LinkedIn once a week or something like that. But yeah, we could definitely improve outreach there. Also, we can encourage contributors to highlight the affiliation. So if you go, you can see that basically people who highlighted the Jenkins contributors, for example, you can take Mark as an example. And here if you go to Mark's profile, if you don't mind Mark, here you can see that he's a Jenkins project contributor for six years. And he does a freelance job as a documentation officer. I didn't know how to classify that one because I don't know what else to call it. Yeah, it's not really helpful in terms of LinkedIn, but well, something still it can raise the visibility of some roles of some things we are doing in the community can help contributors also you can now refer Mark as Jenkins contributor if you want. No idea you could do this my mind is absolutely blown right now. Right. See, and that's, that was the astonishment for me was how many people congratulated me oh congrats on your new role. I've been doing. Oh, that's right. Yeah, I actually did the same. And intentionally because I added Jenkins bot number to the list I forgot to uncheck sent a notification. And I've got something like 100 congratulations, a bunch of can't respond. Can't congratulations from people. Oh, sorry. I'm not removing chess but I doubt that there is anything except headhunters. So, still LinkedIn is something we could use as an additional engine. Why not. Yeah, I was I was impressed I'm actually going to use LinkedIn as one of my attempts to get more get plug in mentors for GSOC, because I think it's an interestingly fluid place to encourage people to interact with us. Exactly. And actually the results are content happening about Jenkins for example at some point I discovered the blog post. Yeah, so you just go to content. The same problem is everywhere. Google and for Jenkins is terrible. But yeah, for example, the post from marquee, then there are other blog posts, et cetera, where you can find some additional information. Why not we could also be posted. As you can see, I have been using it a lot. Because you have a 50 right. So marquee everything is automated. I automate everything sometimes too well. Well, it's good to have you in the Jenkins project is about automation. So, yeah, in principle is something we can do. Yeah, I think that just configuring a 50 for LinkedIn and the same for Facebook wouldn't hurt. So let's just do it. And if you have any other ideas how we could use LinkedIn, why not. I put something like can they contribute a job opening, but I'm not sure whether it's possible. Excellent. Yeah, thanks. Yeah, so just a minor thing, but yeah, so for me it's rather playground for 50 to be honest, but I think that I will get it over the line. Well, again, after the JSOX submission design, because right now, the significant part of my capacity goes there. And if you have high five in Jenkins core. Great. Thank you. I think that covers all the topics we had targeted today. Anything else that we need to discuss. All right, thanks everybody. I'll end the meeting and send the record post the recording. Thanks a bunch.