 So thank you for coming this session and thank you for David Kong team in David Kong. There are many first thing for me, the first trip to abroad and the first presentation by English, so it's a challenge too. I hope I could tell you correctly what I mean, so this session is a rethinking of the review and watch with third experiment of the youth camp. Sorry, so summary of this talk, current review and watch fire is set as two complicated, so after the new format service, this one can serve it. This is a general detail about first, who am I, I serve introduction and why I'm curious about David Walsh, introduction about David Walsh, their own watch, current statistics, and social measurements of David Walsh and last conclusion. So I do my self-intervention, so my name is Kintaro Hayashi and I'm acting as a contributor for David, and I'm a final point, especially soft-dome one, not for a cross-scale or a third-party, and also working for Kray-Korey, Kray-Korey encourages an employee to do free software activity and my trip to David Korn are also sponsored, it's awesome. As a contributor, I'm doing some package maintenance, Grunga, Karmstadt database engine, and Absorbing Releases Monthly, so I'm periodically meeting these packages. And next topic is why I'm curious about David Walsh. This is Torrigate One Bag Report, this is about a redirector for David Walsh. This bag report says about four several mincho, David Walsh far and he's too complicated, so many use many mangroves, Peji mangrove, then your mangrove, you bring your mangrove. So originally a bag report, Hideki Yamanne, he's also, he's David Walsh. He says this situation derived from pre-empting WALT, so it's annoying. So my motivation is it seems that something David Walsh far and too complicated, so I look into, I decided to look into David Walsh. So next topic is introduction about David Walsh. As you know, David Walsh far is useful to check a new version. And about David Walsh, Wikipage are good start point. And Wikipages, it is brand new, are listed, so you can refer it. And Wikipages, common mistake takes to avoid also listed, not escaping wrong fire extension, not anchoring the version, not starting the version part, not flexible enough path, not mangrove upstream, not mangrove deviant versions, not support cryptographic signature, so many pitfall. If it's okay once, David Walsh far is prepared for package, but as you know, some pitfall are there. So David Walsh far is very useful for package maintenance, but sometimes too complicated, so it should be more simple, I think. Next up is a current study disk. But I think it could be more simple demo version part, but we can judge, the idea is good or not, we can judge it. So we need to discuss based on the fact, especially data. So I decided to correct David Walsh data. And so David Walsh far provides API for it, well documented. And so David Walsh far provides package list API, so we can correct source package list. So list of package list like this. And also provides package info API, so you can get suit information about package. Here's an extra example about Grunger case. So you can use this API to correct specific release, GCE or a storage or a browser and so on. The response is about Grunger package info is like this. So you can see Grunger package info. And it also provides file info API, so you can get pass to grow your rail. So in this slide, the latest keyword is described. And actually it compared to actual latest version, so it's useful. So low URL API, low URL in response here. So if you access low URL, you can get content of David Walsh far itself. Actual response is like this, David Walsh far. So now we are ready to correct data. So just correct source package list in stable using API. Correcting each David Walsh far if a variable via API and analyzing on the visual data by myself. It has to manually correct the Walsh data, so I write some utility for it. And for analyzing David Walsh far, it needs to parse option also. So I also developed several modules extracted from UCA, System Comprehensive Diagramming this year. Actually almost 27,000 square source packages are there, so it comes to some question about David Walsh. Walsh far is how many packages you think David Walsh far or which version he uses or whatever the popular hosting site. The answer is 84% packages using David Walsh far. And version 3 Walsh far is frequently used. Next to David Walsh far. Top far hosting covers 58%. Detail is, Walsh use is GitHub and the cheaper source for it and the director for Piper and Hackage is the top far. So 84% source packages are already supporting. So if something good way to improve it, it's better to try. Another point of view are opt usage. It is classified to pull part, not use, early use, central use, or open use part. These options are not used and rarely used option are here. Central use option are here. And open use option are here, as you know. So this is a graph for frequency. What option is used? Very few option already used. So the first is top far hosting site are using. Option are very limited usage. So estimation is we can simply different Walsh far for specific site. So what is truly a required information? There are some information to be pearls or hosting owner project. It is summary two, three information. So I saw news, central idea. So hosting corresponding type, owner corresponding to lower project, corresponding to project, right? So all the rule and statistic, a new rule are here. And difference, it could be more simplified one. New rule statistic were like this. There are many pros and cons. For maintainer, easy to maintain. And flexor enough, if a WRA change, you can avoid pitfall by common mistakes, mainly introduced by a regular expression. And there are some cons for user developer. Supporting each hosting file is needed. And some puncturing nerve is lost contrast to previous rules. And new rule does not have full functionality. So traditional rule and new rule need to maintain. Back to new rule, it is not verified. How actually, practically enough or not. So need to experiment. Here is a step to verify and modifying use can and running soft bar keys. We are to previous version for use can and execute use can with current rule and modified barring. Comparing DHS result, DHS is an external health status. So it's a machine readable output of use can. So I prepared a test case. One is new rule for GitHub. It's a typical use case. I prepared for OSD, but currently it does not work well, so I'll omit. Again, recall new rule for GitHub is here. And it needs to modify use can. So if I think version are on the regular expression, signing by new rule to emeritus previous rule, such work are required. So I'll show some demos. Here is a previous rule. Then execute previous one and new rule. This is all new rule is applied. And this is new rule. So you can see same functionality is guaranteed. This behavior is easily accomplished by very small patch. I did GitHub.com, but OSD.net not worked well, so I need to do more tests. Here is conclusion. So there is a bit redundant case in Devon watch. So Devon watch can be simplified by a new suggestive rule, but not very diversified. So I need more testing and feedback. You're welcome. Thank you.