 Hello, everyone. My name is Brian Davis. I'm a software engineer at the Wikimedia Foundation working on the technical engagement team. My preferred pronouns are he and him. I'm here today to talk to you about the Toolhub project that Shreesee Sethi and I have been working on for the last year. Folks should leave the session with a general understanding of where the idea for Toolhub came from, how it builds on past innovations from the technical community, and what core features it provides. There's a rich ecosystem of tools built by volunteers and staff to help fill in workflow gaps in the Wikimedia movement. There are thousands of bots, user scripts, web services, gadgets, desktop apps, and phone apps out there. Maybe even one that makes the exact thing you are trying to do easier. But how do you find them? This is a problem that individuals and projects within the community have struggled with for years. There are many, many lists of tools on Wiki pages across the movement. There are also lists and spreadsheets, mailing list messages, chat archives, and very likely even physical papers sitting on someone's desk. These lists are great, and I think they could be even better with some help. The Wikitech L discussion that the poll quote on the previous slide was taken from inspired volunteer Rekori Samoa to create a fabricator task that collected links to existing parcel solutions. I discovered this task in early 2016 while researching ways to help volunteer developers working in what we now call Toolforge. I think it was and still is a brilliant idea and a thing that many, many people have asked for over the years. Toolhubs are an attempt at solving this ticket. Our initial release of Toolhub is focused on a set of goals on this slide. We're working towards a core product that makes collecting and reusing information about tools as open as we can. Rather than yet another one-time list of tools, we want a platform that makes it possible to extend and remix the catalog. Critical to this openness is our API-first design. A web API is a fancy way of saying that a web application has features that can be used via their software rather than just by humans. And in our case, Wikimedia volunteers should be able to build tools that interact with the data stored in Toolhub in many ways. Personas are a tool that's used in user experience design to help us think about who will be using the software and why. So I'd like to quickly walk through a set of personas that we've been using when we think about designing Toolhub. Our core personas include editors, developers, researchers, movement organizers, and readers. I'd now like to quickly show you some screenshots taken to the Toolhub demo server, giving you an idea of what the screens allow you to do. This shot is of the homepage, which gives access to Toolhub's full-text search feature. It also displays featured lists of tools which have been curated by the community. Both the search results and lists will show info cards providing summary information about tools. Lists have detail pages, which also allow you to share deep links to them from outside of Toolhub. Each tool info card links to a more detailed page listing all the information that Toolhub has about the tool, including links to the tool itself and, if available, links to source code, bug trackers, et cetera. Tool records have a history view, similar to the Wicked pages, where you can see what has changed over time and who made the pages. Changes. When you're using search, users can search through tools and refine those searches by selecting common values from the match documents. These facets are a sort of search navigation that you've probably seen on e-commerce sites where a list of departments or sizes or colors is shown along with the results, and you can click them to add that attribute and value to the search constraints. Users can create new tool info records using the add or remove tool screen. Tool maintainers can also submit URLs to JSON files, which use a tool info schema to describe their tools. This is similar to the process used for the existing Hayes directory product. Toolhub will periodically visit these URLs, read the tool records from them and update the catalog. They have a crawler history screen, which displays analytic information about past runs of the URL crawler. On this screen, details of errors in reading a URL or parsing its tool info content can be viewed for each crawler run. Audit log screen keeps track of actions taken on Toolhub, things like when a user joined, when the tool was added, when something was removed, et cetera. You can think of this as a combination of special recent changes and special log on a media wiki wiki. Toolhub has a web API, which implements all of the features needed to power its integrated user interface and there's nice documentation available for viewing on the platform itself. Our API requires that any create, update and delete actions be made by an authenticated user. We've chosen not to allow anonymous edits. Toolhub provides its own OAuth service to allow you to register a tool that needs to authenticate users so that they can change content via the API. Currently, only confidential webflow clients, which is a really obscure OAuth detail are supported by the server. Members page lists all current members and the groups that they are in. Members of the bureaucrats group can also use this page to add or remove users from other groups. You can think of this like special list users on a wiki. Lists of tools are possible to create from the your lists page. Editing and deleting lists is currently available via the API, but we've not built user interface for these actions quite yet. So help us make this awesome. Hopefully you've heard something as presentation that gets you a little bit excited about Toolhub. We'd love to have any and all of you join us in making the project a success the movement deserves. You can play with our demo server, help translate the user interface and report bugs and feature ideas via fabricator. You can also follow our progress each week on Meadowiki and I hope you all stay tuned for more direct calls for help as we near our launch date. So I'd like to thank Shristi Sethi for helping me prepare this presentation and these slides will end up posted on comments certainly before the end of the Wikipedia, possibly before the end of the day today. And we have additional sessions in the unconference track for anyone that is interested in further deep dive discussions about Toolhub. Thank you very much.