 All right, so I work for the Public Knowledge Project, or I have an affiliation with the Public Knowledge Project. I've been working here for 10 years, and most people know the Public Knowledge Project because of OJS, but I want to just give you just a very quick of what PKP is. The Public Knowledge Project is a project, just like the name suggests. It's actually a project at a university. It is not an organization that actually exists with any, as an actual legal entity in any way. It is really just a project primarily based out of Santa Fe University Library. The mission of the project and the goal of the project that's now been going on for 20 years is to increase the quantity and the quality of the knowledge that's available to the public and to increase the quantity and the quality of the global participation in the creation of that knowledge. And we do that in a bunch of different ways. For like I say, for most people, this is the way that we do this is just by thinking about open journal systems, the open source software that we do for managing and publishing academic journals. And the reason that I think people just sort of associate PKP with OJS primarily is because there's over 10,000 journals using open journal systems. They are distributed around the world with participation that's a lot in Latin America in North America, basically everywhere in the world where there's just a lot of journal publishing going on. But PKP is actually, we do a lot more than just the software. So we do have software that's open journal systems. We have a conference software that's similar, although that one we sort of shelved a little bit, but it's still out there and being used by a very dedicated community. We have software for managing monographs, so academic monographs and edited volumes and so on. And we're working on a type setting stack as well to be able to do conversions and manuscripts to XML. And we do a lot of work around, we do a lot of research to inform of these activities and to help inform and have us engage with the community. So we do research around open access, research around metrics to understand audiences, around intellectual property issues, around economic models, I have a project around incentives. And we do a lot of this participating in meetings and doing advocacy work and trying to sort of shape the conversation around what global scholarship should look like and a lot of doing advocacy work around making sure that the perspectives of the kinds of journals that tend to use our software journal based out of places that are not just the US and Europe, that their perspectives and their needs are also being considered and taken into account when we're doing any of this work that we do. And we're also providing services, including hosting services that we're doing now to try to also sustain ourselves. So we do publishing services, but we also provide free services as well primarily for journals around preservation and indexing. A lot of people think of OJS, the old version of OJS, which was ugly. OJS 3 is new and now it looks modern, so I just wanna flash through some nicer looking OJS instances to try to dispel that notion that this 10 year old, 15 year old software was ugly. Now these journals look like actual professional journals published in 2018. Not like journals that were being published in the web of 1995, right? This is, you know, so just to give you a sense here, so just a few, I had a little sprinkling of different journals. You may have noticed that some of these examples, you can't read them because they're not in English because we are a project that really takes, are really a global project with participation from journals from everywhere around the world. Okay, thank you. That inside of OJS also looks nicer. This is in the, you know, and one of the nice things about new versions of OJS is that all of the OJS 3, the front ends can be skin separate from back end, which makes so much sense now, but that when we made OJS 2, maybe it was not one of their considerations. So the inside of OJS is also much nicer and it has sort of a, and I could go in and start discussing what are some of the changes around what that workflow and so a lot of the pain points around OJS, a lot of the things that you might have heard around why people didn't, were not sort of satisfied with OJS, we were getting a really positive and great reception from OJS 3 addressing a large number of those issues, if not all of them. And I sort of was asked to say, you know, what is sort of on our roadmap? Sort of interoperate with all of the things. Basically OJS already out of the box, they sort of, we've already have been thinking about how we integrate with all of the pieces of the workflow, and so it already plays nicely with a lot of the tools and services that are out there. And if it doesn't, it can. So there's a lot of things that sometimes we just don't have the developer resources to build, but that we're always happy if someone from those organizations or some of the other projects wants to say we like an OJS integration and is interested in developing, devoting some resources towards it. It's something that we're always happy to do. One of the things that we're doing, which is also just opening up, we have an API that was also built into OJS 3 to be able to interact with the content. And we are, in every subsequent release, adding more and more endpoints to that API to be able to do more things. So at the beginning it was just to be able to pull out content from OJS, and now we're trying to also build in that API so people can sort of actually modify files and do different sort of steps in the workflow also through the API, so that it's easier for integration with more of the things. So I like to say that we are the very model of modern open source for open science tool. We do all of the open source, all of the multi-lingual open source for scholar-led, and we're interoperable. And so we can just put a hashtag around that and I'll end it there. Thank you.