 So, I have started to work for PDF. Whether to realize that sometimes that you can in bacteria do queries to look for what you are looking for. Mutta sitten siksi on vain mahdollisimman, että löydät esiintyksiä, joilla käytännössä voidaan tehdä. Siinä on muutoksia muutoksia, jotka voidaan tehdä, mutta sitten ei ole mahdollisimman. Tämä ei ole mahdollisimman kokeilla, koska se on kokeilla, joten se on kokeilla, että se on kokeilla, että se on kokeilla, että se on kokeilla. Tämä on seuraavaa puolesta, joka on koko ajan. Nyt on seuraavaa, että on seuraavaa, että on seuraavaa, joka on koko ajan. Yksi kenttä maailma on se, että se on vähän, joka on hänenaikoista. Kaikki jälkeen on se, joka on hänenaikoista. Yksi kenttä maailma on se, joka on hänenaikoista. 1,000 uses. So that where this chart gives us an idea of the volume of marks reported in Mozilla, where the number of marks that you have to deal with. So the same four elements are also 4,000 uses that changes done in Mozilla. Let's say you changed one bar from that, that changed. So you have more than 3,000 new uses. So yeah, the question, we should have a loop of uses, that means more than past uses, keyway uses and then just normal uses. Well, I think you get it. So my answer would be like, no we want the freedom, but normal uses in Mozilla, we just, the only thing that you can change is the priority and security, is the resolution. And then from Mozilla, I put it in a case on document. So then we did a script, I thought okay, use that data. To fix automatically. So first thing I need to do is, we do report, normally it's in Mozilla. So that is when it's a script, into my, their ISR report. So the original possible console using the website, it's where normally, when we have old house, we ask the reporters and the users in that pack to retest it again. So normally, when there is one error in activity, we just send this email, this comment, we write it's still reproducible. Normally, when we ping this box, normally we get around 20% of the box fixed as, for me, so normally, yeah, when we do this class then it's in the latest version, to see if it's still reproducible. So the problem here is, well, we have this thing, which is measured and we just say, well, we just want to know the error, retest in the latest version, what they do and check these other things. So now, change the version when it was run, the script's ending up, because that's when changing it to a new version, it's not the correct way of, yeah, it's incorrect. Working a pack that you intend to, you intend to work on that and fix it, then, okay, go for it, assign it to yourself and that's it. Or to new, because we don't want it to be any kind of error, because it's three hours from the pack. So just, let's see a user, just reports a pack, put it new, check that pack. So then, check which packs are auto-confirmed. So when I do this, when I do confirm, then I just, okay, three hours, or I just put it back or I confirm, waiting for someone to three hours. So users, they report a pack, and then, some time later, fix it. Or, you know, like, they test it with a newer version, a new version of the fix in the version. But then, solve fix, which is, solve fix, it means there is a comment for that, fix it, developer fix it. So this thing, by the way, is the test. It's reproducible in a release range. So, if possible, not the worst, but if possible, try to record it. The signature is pointing to this. Well, we see contributors, well, new contributors, that they just submit the packs to Maxilla, and normally they use the packs, well, there's a packs keyword. So in that case, instead, submit the packs where people are used to later checking that pack. So, see if it's indeed a progressive model, fix it, this is a reminder. It's in this big dimensions, well, this is common. I just move back in time, and I see the problem first, and then I just send it to Maxilla, in this case. In order to get newcomers involved in the project, involved in QA. So now, it's not changing the version, so it's just checking it with the latest version. Then, I see if it can work, it's indeed a creation, so I just check it with the latest version. So, it's still open. So, yeah, you should then, well, this now should be closed if there is some similar case in Maxilla, and what they have done, where those approach, say, personal use of pointers, yeah, in general, it's quite positive, because they are really interested in Maxilla, and so on. So, they are like, whatever it is to say, which was the last action of person in Maxilla, and if that person was involved or was changing, like, more than with the packs, and I suppose that, occasions of that, then I just send them out, we receive an email, say, well, we did great, you did great in the past, yeah, we would like to know about it. Yeah, it is actually, yeah, it works sometimes. I answer back, yeah, you know right now, but maybe in the future and so on. So, I will try to give those to those people. So, that is it.