 Okay, so I have good news so Taylor, who is working on the ecosystem side of the CNCF. He was kind of interested because this all of this makes really sense for end users to. So, he wanted to join our meetings moving forward not today because we just talked yesterday but like kind of. Yeah, so I think it's really good for visibility as well so we can find out what. What to do so the end users can find out about all of that so I think that's that's probably going to be really good for us. Moving forward. Oh, and let me just share the agenda so we see that as well. Okay, so on terms of the glossary we have a marketing plan that we need to execute on. So, hopefully, we can start doing that we have lots of ideas. A few things that we did we did have like the glossary stickers at Q that's one of things that I asked if they could do that just because like it would be good to discover. Fun fact, it was gone in the first day. But I don't believe it was because the glossary was so popular just because it looks like the CNCF logo. People just crap that thing because they have the CNCF logo which is huge. And the glossary one was like tiny, and I think people like, not tiny but regular regular size, because the other ones are huge right and I think people just like the smaller ones So hopefully, at some point they're going to be like oh glossary what is it and just check it out. So at least that's what I hope. And so I'm going to ask them if they can do that in in Amsterdam as well because probably like a good way of, you know getting the word out. The cloud native learning journey is stuck. So I'm trying to revive that again because we have that. I think it's a great idea, and I would love to have that by KubeCon EU. And Richard Simon, and I will submit a KubeCon talk like a panel discussion about all these different resources. So hopefully we can, like if that gets accepted that would be great because we're going to talk about how all these things are important for end users and so on and where they are how to find and so on. It would be amazing if we get accepted and we if we also would have that thing live because then we could point people to a page where you find everything together. So fingers crossed I think it's very easily done because it's not like a huge heavy lift to do it because it's not like creating something new is just like linking everything we have so it shouldn't take that long. If we put our minds to it, it should be fairly quickly. And then update on the summary table. So this is like what we've been actively working on. Oh, it's life. Okay. Good, good, good, good. So we had that little so that like for those who haven't seen it it's life like now we need end users to actually and not end users projects to populate all that. So the information that is here is coming from it's being it's being pulled from the landscape YAML and the projects get hop repository. So we need all projects to create a PR. So they can kind of populate all that but we're waiting to kind of reach out to CNCF and send it to the maintainers so we actually have like a little. What is this and I think like I showed it someone and they did not see it was like oh this is crazy. It's like, like all these projects are like it's not if you look like it's not work. It's not useful if you don't filter. Right. It's just, it's just another landscape right it's massive and so yeah, made it bold and blue. I hope that is visible. Right. I know. I'm going to sing a blank screen. I think three blank screen. Yeah, is it can everyone see the screen. I'm going to sing a black screen. Okay, I'll rejoin maybe I can see. Okay, okay. Yeah, yeah something. Yeah. Okay. Okay, so that should be basically ready to go. So, reaching out to maintainers that's ongoing. So I went. I mean, not to all because it was some of them are really busy but at QCON, whenever I had time I went to from project pavilion kiosk to kiosk and the project pavilion and kind of asked maintainers to do that and send them the instructions. I've done it most didn't just like, oh, that's good. But some like I think like three or so have actually submitted up here. Next one is maintainer mailing list. So I'm going to ask Chris and Amy if that's something that they can do I know they're very protective with the maintainer lists but I feel like it's a strong like I mean, it is like a good and important thing so I'm fairly confident that they will do it. I was thinking that to see because they are like, and that's something that you can just do as well. Like we can do like we don't, I mean we can actually send that email because I think that there are like important people there that, you know, or people that know what are and maintainers as well. They're very involved in projects so hopefully that will help as well. I'm going to be doing the set manager one with Ashley tomorrow. If we've videoed it had a little bit of a conversation about what it's about. That would be a good thing to include maybe in some of the mailings that go out do you think could that be useful. If you have what if we've videoed it and she explained what it is we're doing just sort of show how straightforward it is in terms of updating the data. So, I mean we can give it a go and just see what comes out if it's a useful asset to help promote and encourage others to do it then that's a great thing. Yeah. I mean we can wait one more day like I mean like if you do like a video and then like just just there's just like a YouTube link you know like can be. Yeah. I mean I don't know like we never know people have different preferences so I think like the more options we offer them to learn about it or like kind of like the better right. So, yeah sure. We'll do that. Any other things we can do to reach out to projects that you can think of. I think without the maintainer mainland lists. It will be absent right it wouldn't be complete. So, that will be the starting point. Yeah, a lot of people just ignore emails so I'm not like super confident. I mean, the maintenance reach everyone, but not everyone will read it. I think I think the second part is if you have the names at least of the maintainers we can do manual LinkedIn reach out and to reach out or whatever. So, I think the starting point is knowing who is who, and who is doing what and who to reach out than the rest of the operation. Could we raise an issue on the repo for each project, we could do that programmatically and at the maintainers of each project. We're creating the issue effectively to be closed off at some points there's something to assign the work against. And then we have a way of notifying the maintainers kind of natively through GitHub. How would we identify who this is. They won't necessarily but there should be a code owners or a maintainers field on each GitHub repo, which we could programmatically hover up it's it's not going to be a silver bullet it's probably going to get a lot of stuff but not everything depending how maintained the repos are. It's in small projects this will definitely work. Okay. But it wouldn't be a little bit guerrilla, you think. Yeah. But I don't know. I'm just thinking thinking at life. I'm just thinking as a project maintainer I mean. They get a nice they ignore it. They can ignore any house. Yeah. We need to go through several channels, like if this is to like just sending an email and hoping that it will stick is definitely not. So I think like, yeah, it would be good because then it's like, oh, I got an email. Oh, I got this, you know, like, and then I don't know. I think easiest is sending a public public tweets with taking the project and everything because it's community is going to be public. They won't ignore it. It will look bad. If they ignore the project. Yeah. Like, because we said like incubating and, and, and graduated are the ones that we're really going to send boxes like come on. So there are too many it's like, either you you do it or you're going to be left behind kind of like thing right. But how many I think we can in all honesty in two hours we can do hundreds. If you go to it like a three people. It's not a huge effort I think if you have the list. That is the starting point. That is the easiest operation. Search. The landscape has, yeah, the landscape has the has all the Twitter information. Yeah, yeah, yeah. Someone someone like that's like that. People do monitor the Twitter accounts. And it's going to be public. It's not going to be one on one. It's a, it's going to be visible by everyone. So they won't ignore it. That's my assumption. Yeah. Okay, that's a good idea. I think that's a good, that's a really good start, and then we can see how far we go and then like if, you know, I think it's a point when there's a critical mass. Yeah, you don't want to be left behind right like right now. But once like if you have like most of the projects included and yours is not included that looks pretty bad. That's when the urgency starts right. What about what about also taking CNCF industry. Yeah. Let's do that. Pretty candle and CNCF. Yeah. I think that's probably value though in making sure sometimes it's not just the message, but it's where the message comes from. And a great way to get by and from people as if they feel that this is a really legitimate or important thing. So I think maybe, maybe sending something to the TOC, a lot of people subscribe to the TOC list and making the TOC aware of this, for example, could be, and what you do is you establish this is a, like a, this isn't just another, if people aren't exactly clear that this is a CNCF initiative, they're nearly correct. So I'm just trying to think about how to do it so that we're not just like blasting people and saying you need to do this, but rather, you know, I guess getting the tone right and also making them see that this is a really important thing. It might be self. Yeah, I think we should, for all of this, we should, like, you know, like what we did with the email for the maintainers list, you know, like, like, I've been sending it to Richard and Simon and we were like editing. So it's like, yeah, we should not, none of this should be like a quick thing, same thing with the tweets, very few words, it has to be like right tone and so I think like definitely we should not start doing it. We should kind of all agree. This is what we should say. These are not rush anything. And then when we were happy with a tweet, we just got copy paste copy paste copy paste with the exact. Yeah, yeah. Yes. So yeah, we're coming from sales copy bases your friends coming from sales coming from sales copy bases your friends. Yeah, so yeah I think like so basically the next weeks are like our task is basically to come up with all these things and then when we're happy with them just start the mailing the maintainer list we can do because I think like, that's really, I feel like we're, we're in a good place we can share it with the team as well and maybe in the Slack channel I can add that. And but I think that feels like, like a pretty good start. I feel good about really good idea so yeah, really good idea so thank you for that. Yeah and then as mentioned so we're going to submit a panel discussion like we should always kind of think about ways to kind of like stuff that we can, you know, like talk about because it's like there's always an audience it's like, again like one panel discussion one talk will not make a difference but if we can somehow ensure that if every cube condor is like something about all these resources at some point I think it may it will make a difference come, combined with all the other things that we're doing so. Yeah. If you have other ideas as well. Yeah. I think we're five. Let me know we're high. What's the maximum. What's the maximum for four. I think maybe we're five yeah so I think we're four right right now. Yes, because it's if there's an opening please give me in mind. I think I think so I think it's five the maximum right. Yeah, let me check. I'll get back to you. Danielle from the cartographer's group is also on it. I'm pretty sure it's five so let me get back to you. Okay, this is for you. They're super interested. They see the value. They will like to make sure reality, and they will support that's what they said. This is a good site. I think them they said they have an internal meeting this week, and they will get back to me as soon as possible. The project is like the one we get the news, but something else I asked to them is cater maybe this could be a new threat that I forgot to add a speed dating event in, in Kubecon Amsterdam, where project maintainers are owners like in the scope of this presentation idea, and in the next stage 15 minutes, talk about a project stand down, talk about a project stand down and in a day like tens of projects taking stage with the like a speed dating event in a room people come in and leave for interest in the project. This is the idea, and you might be extending the video and introduction and glossary idea to that room, where we can promote it further in the speed dating event. This is what we do do you want to give the information as fast as possible in the brief, briefest manner as possible. And we will have a session hopefully. Okay, so that would be like, like, like a real session and it would have like, but it would be several so we can accommodate all projects or it would be like different. Yeah, there will be different like 15 minutes each. Three hours every day, if you call six hours. Okay. So we will accommodate like about 2430 projects a day max. So two days, 60 projects which will be quite good I will say and I will definitely spend time in that room to hear about these projects. I don't know if anyone has any ideas if you find this is a good idea. I would love to hear feedback. Yeah, I think it's a great idea, especially if we kind of bundle them together so they make sense. I'm interested in databases here like all the pictures about so right like all day like one hour is gone the next hour is going to be all database stuff. Exactly. Yes, yes, per interest group. And with 60% of coupon attendees always being newbies that should be actually a standard, you know, because there's enough people always. Exactly. And I feel like these three 14 summary table glossary, the video and the speed dating event really bundles well together. So we can spread the word real good in this kind of session. Great. Good. And then I potentially have a new project that someone is interested in working on and that is improving the UX of the landscape, because it's so massive and making it in a way so it's digestible, because it's completely out of control. And. Yeah, so making it more like, you know, interactive where you kind of see like the layers first and then you zoom in you see things and then kind of like instead of like seeing everything at the same time you kind of understand oh these are the stack layers like I'm interested in this like zoom in and then the you would see when you kind of see a specific section versus seeing all logos at the same time which is very overwhelming. So someone's interesting on working on that, but doesn't have time right away. And I know someone in the CNCF who was interested, who has a background in UX and was like oh, he'd love to support that were possible so Well, very much needed project as well. I think that's all we had. I think we're, yeah, like main thing is getting the summary table out there. And then some of the marketing things to get the word out, I think that's kind of our. Okay. And then some of the homework with the tweets and stuff so we'll be in touch. Just sending those probably in the slack channel business value slack channel and kind of like we can collaborate in there and kind of see like, make sure they're, they're hit the right tone and, and the urgency and everything and I don't know how many characters. It's going to be much tougher than the email Simon, but it's completely doable, but it will require a team effort. Awesome. Okay, Alexander, what are you saying interested in helping improve. Yeah. Okay, sounds good. I'll let you know when, when we're kick off, kick off, kicking that off. I think it will probably take a little a few more weeks but yeah I'm excited about that one. Okay, that'd be great project really valuable. It's not a slightly off topic but just before we all disappear. I'm leaving cloud reach the end of the year, moving on to pastures new. I'm going to try and rope somebody else in from cloud reach so that we still have kind of a foothold in with the CNCF that's okay. I think Catherine you've spoken to my colleague Merriam before. Oh yeah yeah yeah she's part of the glossary. Yeah the translation stuff. So she's a bit more free now and she doesn't know it yet but she's she's going to inherit this. I'm going to have a chat with her on Friday so if I don't speak to you all before then I will probably still try and keep in touch with new company but please be kind to Merriam when she when she arrives. Of course, Rich. I just wanted to preempt it so yeah so if I'm not there that's why Merriam's there. Yeah, are you going to be able to continue because it's like that's not necessarily linked to your job of course. I'm hoping to. I'm hoping to. I'm going to FinTech company, small startupy thing so it'll be a slightly different change of pace for me so I'm hoping less demanding customers and perhaps just showing focus on some of the stuff that I'm actually really passionate about so so yeah. Well first of all congrats. Yeah, but like if, yeah, sorry to hear that you don't know yet if you're like we hope you can still make it if not if you need a little break. Yeah, yeah, it's kind of hard right because you need to focus, and hopefully you can. But I expect to see me reappear at some point. Immediately. Okay. Cool. Well thanks everyone. Talk to you soon. Bye bye.