 I'm here to talk about open source design and a project that I've been working on called Open Design. This is about how to engage with designers on open source. I'm a designer, I work at Ushahidi. We create humanitarian open source tech tools. I'm very new to open source. My first experience of it was through Ushahidi. I was like, okay, this is really cool, but how do designers become more aware of open source and how do you start getting more design contributions to open source tools? How do you do all of the different kinds of complicated advocacy work within open source to understand the value of what design can offer these tools? Likewise, how do you break into the design industry, which largely doesn't get told about these tools, to get them to contribute and let them know that they are able to contribute to these tools? Why aren't there many design-related contributions to open source software? What we found out through starting a project at Ushahidi called Open Design was that designers are really ready to contribute to things that do good. The thing that they could understand relatively easily was the kinds of tools that Ushahidi created, which were humanitarian open source tech tools. We started at that from a basis. We used the introduction of humanitarian to help them be introduced to open source. We started by doing challenge gatherings, a typical hackathon or design jam approach. We did one in Berlin in 2018 around one of Ushahidi's tools 10.4, which is now open source, and one in Seattle in 2019. What we found was that when you have a design group get together around issues that might be needed within your repos, unless you're really well defining your issues, designers tend to go off on these kinds of design fiction tangents. They'll start creating different things that might solve problems for your tools in the future, but maybe not solving problems for the issues that you have in your repos right now. This can be really useful for your open source projects, much in the future, but if you're looking for active contributions right now to things that you know that you need, it's not really going to help right now. This is one of the things that we learned from these first two events that we did. We've subsequently started to plan events for this year. We've got one coming up in Bangalore and one coming up in Nairobi. There are much more around structuring clear issues and clear needs but from designers for the open source softwares. Again, going back to the question of why aren't there many design contributions to open source. There's actually many more reasons than I have time for, but the main one, designers don't really have a clue about open source. Like I said myself at the beginning, my first introduction to it was with Ushahidi. One of the main things that's a challenge here is getting more designers to know about open source and what you can do there is go to design conferences. Like a designer here at open source conferences, you can cross-pollinate. You can go to these places and talk about these tools. Even if designers know about open source, GitHub can be a barrier. Sometimes it can be actively scary for designers, so helping them understand how they can interact with things like GitHub or where you host your project is really, really useful. Suggestions on engaging designers, your first issues in your repos. There's some really great things that if you're not quite sure how to ask for design contributions to begin with, I really recommend the two links on the screen here. One is from Brad Frost, the interface inventory, really useful for any project. And heuristics. Asking designers to produce design heuristics for your projects, it's really, really useful. Take a look at these links, create issues for these in your open source repos. You'll get a wealth of information. Some suggestions on structuring repo issues for designers if you're ready to add them. Make a tag for designers, make a label for designers. Very clear, very obvious. But also maybe split these into different design asks. So you might have one for graphics, for icons, for UX or UI. Give as much information as possible in your issues. Give the background information about your users as much as you can. Design documentation, super useful. Edith's just produced a load of design documentation that you can use. And learn how to critique design. Finally, follow the open design project. Get involved if you have an open source project you want represented. Thanks.