 And the only thing that determines the 16-pattern is in general, it's easy to get G. So if you want to change policy, you have to change the tools. I see. So you're working with the schools? Yes, of course. For the schools? There was no function there. Well, then does it really make sense to have that in the policy? It's fine. It's fine. It's fine. It's fine. It's fine. It's fine. It's fine. Well, yes, but the version you got there comparison does make sense in policy because the maintainers should be made aware how they are allowed to version their packages. But should we just refer to the users into difficulties in the communication, like we do for the cloud season and several other components and position something like that? To package maintenance are no good documentation measures. Well, that's something that's so useful that it's a problem in a stash problem. It's probably the other problem. Yeah, but the file here is standard. It's something completely different. The version name of the package is an integrated thing that you need to really need to know as a package maintainer. We don't follow the file here, but it's standard. It's a bad thing, but it won't break the complete archive. If you don't really properly version your packages, you are host while it's big because your package won't be upgraded or installed or accepted by dark of the past. So what about the version name? I think the last chart that we have done is telling us that we would have liked to have a test tool for our version compilation. And there's no test tool. I think there was one. And you could point to the developers who wants this free case that you need to use as a policy. And it will be fixed. But if someone has to buy that test tool, then no. The thing that I want to point out was that people don't like to avoid to write tools that do things by documentation or by policy. Because there is a moving target. So sometimes you have to go to the code to understand what happens. And I think that's a problem because in the US we can't use it to execute in HEE. It's like a dash-dash in our versions. And that's detrimental for performance and whatnot. And I'm sure more people will cry at me when they saw my code. Why is that from scratch? Maybe what should be done there is way too liberalized library that can be executed for them. Libraries will be the same way. That is for the language. It should be in C? Yeah. Because it's called in C code. Yeah, it's the messiest, but it's the messiest way to do it. Yes. And make every code you start. Yes, that will be the same. Live version. I mean, live there your version. OK? So that one will probably work. You just say what should be done. The version comparison maybe is some other things that the package does should be put into the library. So it would be elliptical. Yes. No, maybe separation would be nice. One library for 3 and 4. But I think we are wishing for stars to fall down. Do you know what you're saying? We are wishing for things that just don't happen. Do you know if any of the DPKG maintainers is coming? I know several of them are not. My guy is not coming. And the dad is not coming. Dad is also not coming. Dad is not coming. That's a great question, I don't know. But not? But not? My question is not. OK. OK. Ah, thank you. OK. Because we could see for several of the functional people of DPKG, we could check if it's possible to try to monetize some stuff that will also clean the base code of the tool itself. It wasn't of the topic. Only a tiny bit. OK, so we're rewriting the HS1C. I thought you were about to use the word. For the time. For sure. For the time. Maybe they can see. Because the bottleneck with the HST is still the network. No, no, no, of course. No, it would not be for this tool. I only mentioned C for the thing that should be monetized from DPKG. Yeah, but if it's done in parallel with this. Yeah. DPKG. DPKG. DPKG. But not for static tools. DPKG. DPKG. It must be always a static tool. It's not available. It's static. It should be a library, right? But some others are for it. Something that's for it. I think we should get a bonus. For position, right? Derek. Derek. Let's get a room with them. I don't suppose this. I know it's completely a state. It's a very important, maybe okay. The essential part of the team. About the original network in talk. You were essentially redesigning the HST. Yeah. I don't know what you're talking about. It's a personal project. But I don't know if it's about the way mobile data is used. Just one more question on the sector. One more question on the same topic. No. As a goal is to put everything in a single SQLT. So you can run the query. Mixing code, stuff from package.js, VHS, and maybe. It's similar to mobile, but the goal is different because it's mobile that can't run package.js. That's the right way to do it. I don't ask for more. I try to find it. That's another problem with mobile. I think from J. There was a proposal. I had it with my team. I'm so cold. I'm so tired right now. That's a lot of points. No, it's already running. That's the US gate. Yeah. It's kind of sponsored by Google some of the last year. So using us in the future. Last year. The question was, like, did you open the things? So it would work. Okay. There's no one. Well, I was considering using UDD for storing data. So there's no need to duplicate information everywhere. Well, at first I wanted to use some of the applications that I made. There's a lot of problems that are not actually much around mobile. Like, only in the future. No, no. There's a lot of things. There's a lot of things. I think this is a much more accessible approach. I know. There's a lot of points. There's a lot of points. I'm using UDD. It just means using and expiring the database. Make us know what problems are suggested. We can even report all the details as to what services are going to work on. You might be able to fix it by supporting without your pay. Wow. Does anyone know the status of UDD? Yeah, because I met her with me. Yeah, she brought it up to me. So, what about to start coding studies? No. Actually, it works very well. You can run queries. But currently, all the perks are important. That works. So C in packages 5 are important. And the third point is important. How does it work? It depends on the data source. For application support, it's frequently used. It has a lot of minerals and usefulness. For bugs, it's just frequently used. It's frequently used for bugs. How is the access to the data? I'm right with another one. Currently, only the student and the resource are accessed. And as an application, we have the same machine. So you can export some queries. And you can access it from master. You can use it very directly from master. You can also use it for the BTS or something. So you can access it very easily. You see? You can also use it from a net enemy also. Yeah, because you will be able to start the check and drop out. These other things. And it works out. What? And it works out. Actually, the more interesting question is how to get more data in it. Do you have any idea what kind of data you want? I don't know. Some of the staff team was talking about this version and the names. For example, the actual version and the actual names. For example, now I have a problem with how to provide access to the list of all the current packages. Which is the actual name, which is the actual version. And I cannot do that for the rest of the current packages. So how do I keep track of that? So having a software that is for that. I think that, for example, identifying every upstream project is not something that we should solve inside the land. But that is one of the problems used. We can just keep it from below, actually. So it's really, it's not, it's really into collaborating with other projects. And in, maybe, yes, the idea of starting someone, something like a register, like for the port numbers. Like for the port numbers. Yeah, yeah. So something like that, but for the three projects. So you can know that these projects, these packages, they are basically these three projects. And the same projects as these packages, which doesn't have the same name. Because that's something that's needed for our extension by sheet between distributions. That would be a good idea. I'm not sure it would work. Yeah. But was using the complex build, whether like this gets some basic information. That's how it's going to work. But not really. You can actually use it for example. You can take the domain name and use it and compare it. For example, all the, in fact, all the packages in the ranking that have this specific domain name at their home page. Yeah, that this provides some information. Maybe you cannot just, well the thing is that I don't think about any other way to do it. Because for example, this provides a specific page and that page cannot be changed. And for what information are we going to use? For example, for making the relation between a streamer and a stream package. It doesn't need to be a tutorial. It can be something else that can match or can make the relationship between any package, any kind of package. It's not necessarily, it has to be a, for example, if the, for all the sub-forged packages and projects, it could be a code sub-forged plus sub-forged number. So then you have a symbol. Yeah, but there are maps. Yes, but it's more information that you will not own. You thought that you were going to copy many different ways and many different parts. You can see that it's also a symbol. You have certain symbols, slash packages and stuff like that. Some other ways at least. Yeah, no, but you have sort of unified, if you put in, if you put in, if the code package is on CPAN, you can have a unified way to refer to it with the homepage URL. And you have the direct mapping of the given package. Yes, you tried the package number? Yes. It's not the URL, it's not necessary. It's not necessarily easy. Yeah, if you unify the way how to refer to CPAN packages, code packages, your efforts. I think it's not, there's not any universal way to do it. There's some exceptions always. It's almost in Chinese. No. I think there's some problems there. We have reported many times about the official defeats, I mean. Sometimes I don't hear answers. I would be surprised. I think I should have specialized the knowledge. But I don't think that they have found basically a way to do something. No, wait. It's interesting to get the first list of the information. Yes, yes. I'll start that case with a list of the information. I wanted to show you the kind of information you can put inside the other in the list. Yeah. Yeah. There's a list of the information. There's a list of the information to describe a business project. There's a list of the information to describe a business project. To describe a business project with the efficiency from the I think it would be difficult to be in the L.S.N. When you look at what you get to say, it's very meaningful. Yes, well, it's pretty complicated now. It's what? Yes, of course. Some of the information that we have been collecting on the L.S.N. can be used. Okay, you've talked about the L.S.N. Monday. The L.S.N. Monday, yes. And we still have to prepare it. Yes. But it's a great linearity. Most of the information comes from the source package. Does it interface with the S.B.N.? The quality is the S.B.N., yes. But it takes information from the S.B.N., from the guide, from the B.T.S., from the watch price after you. I'm just thinking about S.B.N. because it's not the L.S.N. No, no, no, it's similar. Well, it's different on the idea behind the L.S.N. Yes. How do you name what's the difference? How do you name what's the difference? Well, this process tries to get all the information from all the packages on the S.B.N. Firstly, it doesn't depend on reading. Yes. It does watch files, I think, with the S.B.N. as well. It uses EHS, I think. I thought it uses the most important controls as well. So watch files. The most important control system as well. Ah, I don't... I don't drive very fast ones. Which two do you use? S.B.N. and S.B.N. packages. S.B.N. knows that. I'll just start. Yeah. I'll leave it at that. Take it. Yeah. I can't show you. Yeah. Shhh. We have many that. Please don't show it to the camera. Who's actually one of these? I don't know you. Yeah. So that's it. And let's say you're going to take a picture of us. There it is. Yeah, yeah, yeah. No. Because it's one of the repositories. Well, there was an idea floating on the group some time ago about having some interaction with this and trying to measure the information because one thing that is very useful from this is the building of the big dogs and I don't remember which... Choose it. There also needs to check out this. I think I'll remove that. Lean that? No, okay. No, lean that one more. Lean that. Lean that. Now I'm good. That's my idea. Yeah. There's not much information that's really important. So your sony is great, isn't he? I think that the client is like, is QI built that? Yes. What's nice are you? We can still change to be RPM based. I couldn't react. I don't know if we can already have icon fires in our packages. Actually we could do like, you know, one big group would do everything in CVS. I think there are a lot of CVS. I'm not sure it's CVS. Can I develop CVS? You won't be able to read stuff. The first thing I thought about was CVS. What's CVS? What location was it? CVS. You said that Fedora has all these things. I'm not sure it's CVS. I'm not sure it's CVS. I don't remember. What's it called? It's called CVS. It's called CVS. It's called CVS. What's CVS? CVS. It's called CVS. I don't remember. I was never able to remember. In Spain, I thought it was nice. We did the early MMO. It was quite easy to do. Why? But I don't remember. What's CVS? It's ARC. It's a posterior file. What's CVS? It's ARC. It's ARC. ARC. ARC. It's very easy to do. It's very easy to do. It's very easy to do. It's usually... It's also ARC. It's also nice to do the ARC. I just blinked that. Sorry. I just don't know why your family doesn't blink. I'll learn to do this. I think that's a different... ...the grid. So let's break. I'm not sure. Feed the right seed. It's CVS. Ouch. Another reason to... I'm not sure. They talk about CVS. They talk about CVS. They talk about CVS. So... Do you have a certificate? No. Do you have a pass? Do they mention something about the system? Chura. Chura. Would you like to give a name? The one I didn't mention. So scotch is major. So scotch is major. I don't think I want to be scolded. It's very easy to learn. I just need to learn. Thank you very much, it was a pleasure to have you here on the control side. Thank you very much.