 So, yeah, my name is Chesco Fowli, I am from Valencia, Spain, but I live in Granada, and I am the QA engineer in the Document Foundation. Well, it was about finding interoperability regressions in LibreOffice. It's based on a tool created by Milo Sareb, something like that, I don't know how to pronounce it. And, well, he gave a talk in LibreOffice conference in Brenno, so I've been working on this tool and, well, my talk in first-time was about this. Basically, what we check with this tool is if we introduce interoperability regressions in the documents, so we compare it with Microsoft Office 2010 and we see if documents are displayed correctly or we have introduced regressions in the display of the document. With this tool we check how the documents are imported into LibreOffice, but we also check how they are exported. So what we do is we open it with LibreOffice, we export it, and then the resulted document we have, we check it and we open it with Microsoft Office and see if everything is correct. It's kind of, let's say it's 80% automated, so all the scripting and import, export and comparing the documents is automated, but in the end we have to check it manually if we have introduced a regression or not. The more documents we test, the better, because we have a better coverage. So right now we are working with a thousand documents, but it has been moved to a virtual machine recently, so the idea is to, let's say, 5,000 documents or even 10,000 documents, so that would be ideal. Yeah, we take them from the backtrackers, from different backtrackers, Baxila, well, from LibreOffice backtrackers, we also take them from Abigual backtrackers, Caddy backtrackers, so from different backtrackers we gather all these documents here. I knew about LibreOffice, the day it was forked, I read it on the internet, so I got curious about the project and I joined the mailing list and so on, and the same year I was able to participate in the Google Summer of Code, so it was in 2011, and yeah, I succeeded in this Google Summer of Code and since then I've been contributing to the project every now and then when I had some spare time. I did some development and I also contributed in QA and then this year I had the opportunity to join the team as QA engineers, so yeah, it's useful to us nowadays to the QA team because we can more or less find how many classes or how many users are affected by that class, so that's kind of important information to us, so we can set the priority based on these numbers. That's one of the priorities we have nowadays and I think it's going well because when I joined the project, well, I didn't say it but I joined the project in September 2016 and at that time the numbers were around 750 and right now are around 500 or even sometimes even 450, which is, well, we got a good gain here, so we reduce it a lot, the numbers. Well, it's important that everything is as much detail as possible, then we appreciate if there are some clear steps to follow in order to reproduce the bug, then it's also important to have a document in order to reproduce the bug and I think it's important that reporters try to find if the same bug was reported before, otherwise we are reporting the same bugs again and again, so then it's more work for us to do in order to find this duplicated bug. So we have different communication channels, we are going to leave them here in this video, in the description and I think that's the direct approach just to go to this communication challenge and contact us directly. Otherwise, well, we have some easy tasks for newcomers and one of them is to try to confirm and confirm bugs and we also have some old bugs that need to be re-tested, so that's another task a newcomer can do, so basically go through the list of bugs and see, okay, I'm interested in this bug, let's see if it's fixed in the latest version or not and there's another interesting task which is when a bug has been fixed just to confirm that the bug is indeed fixed, so just to verify that the bug is fixed, so it's basically you just download the latest version, the latest master version and then you check that the bug is fixed. Then we have all the interesting tasks which need a bit more of knowledge but yeah they're all in the wiki page or they can just ask us in the in the channel and that's all.