 Rhaen i, fyddech chi yn ein gyrdd yng Nghymru, yw'r pryddysgu sgol i gyrdd ffwrdd ddiwedd. Gydag yna yng ngyfwng y dyn fuelio, a ydych chi'n ddweud yn llei'r email. Felly rydyn nhw'n rhaid i'r llyfr ar gyfer y llyfr, ond... Maen nhw'n rhaid i'r ddweud yng Nghymru, oedd y lanscape ydw yng Nghymru, yng Nghymru'r mwyfyr yng ngyfredig, mae'r ddweud yng Nghymru? Mae'r ystyried mae'n llwyffaeth i gael ei miliwyr, fel Luma, ac mae'n gweithio'n gweithio'n cael ei chyfnod addysg o'i gweithio'n adrodd o'r llyffyr yn llyffyr â'r adrodd o'r cyfnod a'r cyfnod sy'n cadw i'r cyfnod hynod. Mae'n gyfnod i'n gweithio'n gweithio'n cyfnod, ac mae'n gweithio'n gweithio'n gwyllus. I know the idea comes from there and obviously open source developers, as developers they thought that they wouldn't do manual work ever and a PDF, so they decided to automate it and make it a bit more complicated. And it turns out that it's made with YAML and JavaScript, which I quite dislike both if I'm honest with you. It turns out that it's quite useful regardless of that, right? So this is the, what I'm going to describe here is my failure to deliver on the landscape. This is the CNCS by the way. I'll show the SPDX in a minute at a current state. But also it's a cry, well it's a request for help so that we all commit pull requests to the specific repo that I'll show. And I'm happy, although I don't have approval powers privileges for those pull requests, I'm happy to vet them because I've gained a bit of experience in managing this. So this is the CNCS landscape. I think it's very valuable for a project like CNCS, which is humongous, huge, but also for SPDX. I think SPDX covers so much ground from way more verticals and industries than the CNCS. I mean I haven't compared any, but I would say so. So therefore having a fully populated landscape for the SPDX, it would be great. And one thing that people under use of this one specifically, this one's usually, back in the day there was jokes about this. I can't remember his name. He used to work for PagerDuty. EveryCubeCon he would print this and then he would copy this and print this in a, what's the name of this, a puzzle. So he would, and it's impossible to, as you can imagine, right, to get it together. Anyway, so but one of the beauties of it is that it does have a guide that walks you through each one of the categories, right? I think it's very valuable provision in runtime that those are relevant to the CNCS, but I do think that if we come up with good categories for the SPDX landscape, which I'll show you in a minute, then navigating the landscape, the community, the tooling ecosystem, everything will be much, much, much easier. But as you see, there are way many more companies than what you can see here, but I have failed to add them. But we only have two categories, right? We have no guide, which should be here. We have less, wait, how do I control tab, is it? Yeah, there you go. We've got way less categories, so categories would be these boxes, right? And then I'm a bit confused by why the CNCS would have a serverless sort of like division and a wasm one. I'm not sure why that is, but maybe it's just internal politics of the project. I mean, it's not that it doesn't make sense, but eventually, again, we would be able to come up with tabs for this. Well, the card mode is a different vis. It's just seeing each one of the companies or projects in a card mode, but members and so forth. So that is... There you go. That's it. These categories will be relevant in the discussion that we will hold at the end of this meeting because they are up for discussion, right? How are we going to structure a landscape? Do we need to follow the NTIA's division that they provided for what was it, product? Can someone remind me of the three divisions they came up with? For the behaviours that a tool... They divided the tooling landscape in three categories, produce, consume and analyse, am I right? Exactly. And then each one of these three categories into other three subcategories, right? Maybe following that structure would make sense and so forth. Anyway, the way to add new companies and projects, so this is my request for the community, is to go to the SBDX GitHub project and there's entity, probably the right word, but anyway there's a specific repo there, right? Which one is it? I can't see anything. Oh, there you go. This is the search bar, right? Is it landscape? Is it shipping? There you go. That's the repo. A few of you, except for Rose, Kate, a few prominent members, will have privileges in this repo to accept pull requests and so forth. So what you need to do is fork it and make a clone it to your own GitHub instance profile entity and then from there on make the changes to the settings YAML. This is my arch enemy because it's very, as any YAML file, is very picky on syntax and I'm quite clumsy and I just mess up all the time. But basically you just need to add this information for each one in the category that you find the product or project should be added to. So this is adopter, the category adopter and just another one. I think it was tools. And then just add each one of the required values over here, right? For each one of the projects. And then there's one thing that cannot be avoided because it's obviously a visualization, so it requires a logo and it requires an SVG logo, by the way. But there's a, and that's quite, not every project has a SVG logo. By the way, I did find out everything that the landscape project as a visualization project is not documented, so don't look up any dogs where there aren't any. But there's a really neat Slack channel or community in the CNCF Slack instance that is called the Landscapers if I'm not wrong, which used to be private but since I joined and I asked so many questions, I think they've made it public. And yeah, that is a great resource to get your question solved. There's a few people that know the ins and outs of the YAML, but anyway. They told me about vectorize, I think it's vectorize AI. I mean, maybe this is stupid to show, but I didn't know about this project. You just put in the logo of, because this is a requirement to have a logo of the project that you are adding to the YAML file. And if you have it in PNG or any other format, you just drop it there and it will make a very neat SVT version of it. And that's all, yeah. Again, I guess the project welcomes as many contributions to the landscape as possible. I won't have the privilege to approve any of the pull requests, but I'm happy to help you with the most like with the errors or interpreting the errors that the build process will produce, because I've been fighting those for months lately and I've become a bit of an expert with that. And yeah, that's all. I'm committed to fill in that landscape because there's plenty of companies that I need to add to that landscape and by the end of this year, so I know that in the next minute summit we will see something much, much better than that, than this, right? Hopefully similar to the CNCS one, mostly because the numbers are, I mean, not similar, but if this was reflecting the amount of companies involved in SPDX it would be much bigger. And yeah, and that's all.