Hi everyone, welcome to FOSM 2021 Open Source Design Dev Room. My name is Abigail Makoro and I will be talking to you about the Open Source Designers Toolbox, basically recommended techniques and tools for open source designers.

Now when I thought about speaking on this topic, I had no idea how I was going to structure this toolbox because there is a variety of information and resources that are relevant to designers contributing to open source.

So I have decided to keep it simple and just make it something that every open source designer can refer to when thinking of their own strategy for contributing to open source. So we would start by trying to understand what open source design is all about and this is basically how I have defined it.

It involves introducing creative problem-solving processes to projects that are free and open to read, modify and share. So it is really open source plus design and while preparing this presentation, of

course, I searched for a definition of open source design but it's not surprising that I didn't find a lot of information on that because open source design is an emerging space and it is nice to see more people get interested in what designers are

doing and can do for open source software. So this is how I understand open source design and I hope that it has captured the concept of making open source design contributions. So now that we know what OSD is about, what should you know as an open source designer?

Well, you should know how to communicate. Just by virtue of being a designer, you can already expect that there will be barriers to participate in the open source community. This is because open source is more focused on programming and coding and that is how

it has been for a while. So there is a lot of tech jargon that most designers don't understand like IRC, GitHub or Git or version control. These things are not terms that designers are familiar with and that can be quite discouraging

but you should know as a designer how to communicate and present your ideas, put them forward or put yourself forward in a way that you can build your identity and help people get to know you, understand your ideas and hopefully get your ideas accepted.

So when you post messages in the team chat or you have conversations with other team members, you want to make sure your messages are comprehensible, make sure people can understand what you are asking about and you also want to make sure you have done good research beforehand so you don't weigh down other team members.

So making sure your messages are easy to understand helps it, makes it easier for people to respond to you quickly and also offer their help and all of this helps you to get integrated into the community. So beyond communicating, also know how to engage and become a part of the community.

It shouldn't be one-sided, you always seeking advice or feedback, give back to the open source community. Now most of these communities have events that they have scheduled regularly so try to attend those events because you get to network with other members on the team.

You can also give feedback and also get feedback from these team members and very important too is the fact that you can suggest improvements for the team or for the project, you know, how to make it better and these events really give you an opportunity to do so.

So trying to become a part of the community really helps you to build an identity for yourself as we've mentioned earlier and that identity definitely facilitates your contribution or your work. So definitely know how to contribute.

This is what many designers look forward to when they ask about contributing to open source design, just getting into the nitty-gritty of the design work and that is great. If you're just going into open source design, you can explore some good first design issues like conducting a realistic evaluation, you know, of the project's user interface.

You can design empathy maps and personas based on any existing user research data that really help to get other team members in the room and help them understand who the project is being designed for and put themselves in their shoes. You can design sticker sheets or style guides or design systems which help the design

team to work together, collaborate and really helps the project design to be more consistent, to have a more consistent look and feel. And if you're a more visual design client, then you can definitely design some branding

assets, logos, t-shirts, things that can help the brand image of the project to really stand out. Before I come to document, one thing on making contributions is in open source, it's always

quality over quantity. So you don't want to be the first to make so many design contributions that don't really make sense or that don't add any value to the project. So make sure you're solving the problem and trying to solve for that problem. It's always about the quality, the value you can deliver to that project.

It's not just for the sake of contributing or opening design issues and all of that. So document, document, as designers we document everything because we know we definitely cannot rely on our human meaning. We can easily forget what design decisions were made, when or even why they were made.

So we want to make sure that our design deliverables are presented and documented effectively. Some ways you can do that are by taking advantage of design labels. So when the project already uses design labels, that is it groups issues, design

issues based on categories like UX, UI, branding, research, you know, these labels really help to organize these design issues for others who may be looking to contribute in the future. And if the project doesn't already use design labels, then you can make that suggestion

and you should also check if the project has a file, a contributing.md file for design, you know, somewhere that designers can visit to see how we can make design contributions and how to get started and a point of contact. So you can always look out for that.

You can frame design issues on GitHub as design challenges and this just means providing more context or information about that issue. So what is the problem you're trying to solve? Who are you solving this problem for? Who are you designing for? What solution or solutions are you exploring?

And how can you tell if those solutions are effective? That is how would you test your solution to see that it is successful? Adding this extra information to your design issues basically helps to give more background information and helps anyone to understand what the designer was thinking

when they set up this challenge and they could know easily how to contribute to the problem or to the issue being solved. You should also use issue threads. So every design issue on GitHub would have a thread where conversations on that issue

are maintained. So you don't need to take the conversation out of that thread. But if you do you want to, you know, add some pointers to that conversation in the thread because those threads are really useful for documenting progress and updates and decisions

that were made on that issue. So issue threads are really a nice way to document progress on design issues. One thing I always encourage designers to do is to annotate their sketches and wireframes or user flows. So when you make those diagrams, you want to put some little notes that can help anyone

understand what the process is and that way anyone can make a contribution or can give you valuable feedback. They don't even have to be designers because those notes are pretty much explained in the query and those notes can actually help you document, you know, they are

effective for doing that. So you should also explore there are a lot of really an open source tools and resources for you that you can use in your work. You can get free assets and all that but as you search you want to understand the

different types of licenses for these assets. Are they permissive licenses or not? Did they require attribution or not? You know, so you should understand the different types of Creative Commons licenses so that you can very carefully use these assets because if you don't you end up putting not just yourself at risk for the entire project.

So you want to make sure that the assets you are using are well licensed and you are able to use those assets in your work or in the project. So I have included a link to a web page that explains the different types of Creative Commons assets that you should definitely look at.

Grow the great thing about open source design is it gives designers an opportunity to expand and to grow in their career so you can take part in open source internships or projects like Google Summer of Code or Outreaching which really gives designers

the opportunity to contribute to open source. And it's a great experience because not only do you get to make meaningful contributions to actual open source projects, but you get to interact with the community and see what it is like. You get to present your work and receive feedback or criticism on your work and you

already get used to the whole open source space. So you should definitely look out for that. And because we know that open source design is just coming up, you can advocate and let more people know about it and how to contribute to open source as designers. We definitely love to see more designers get involved in open source and make

open source software more usable. So all of this will help you expand your portfolio not just as an open source designer, but as a designer in general and that is really great for your career. So here are some tools and leaves that I have included for your reference.

Pencil and paper are some of my favorite tools and designs, but you can also use tools like Draw.io for diagramming like your user flows and site maps. Figma and Adobe XP are prototyping tools that you can use for open source projects,

but it really depends on what tool has already been adopted for that project. So if a certain tool is already in use, you want to try as much as possible to stick to that so that other team members can be on the same page with you. The choice of prototyping tool, like I mentioned, really does depend on what

is already in use. But if you feel something else will be better, then you need to suggest it to the project maintainer. Pencil is a free and open source prototyping tool that I just discovered. I think it's interesting. And you can definitely check it out. Inkscape is a vector graphics editor, but it's also free and open source.

Blender is a free and open source 3D graphics tool. GIMP is a data manipulation and editing software that is also open source and free. And Simpig is a 2D animation tool that's free and open source as well. These are just a few of the free and open source tools that are available for

your use as an open source designer. So you don't have to invest in expensive software just to contribute to open source if these tools are readily available. And all the links you find here, when you get the slides, you can actually just click on them and you'll be taken to the web page for that tool or project.

So these are some reads that I found pretty interesting. This paper on barriers faced by new commands to open source projects would really help you understand some of those things you can expect as you start to get into the open source space and how you can overcome those challenges. Barriers for designers is also a very nice article for

designers and also for open source project maintainers. It helps them see how they can encourage more designers to contribute to their open source project. So here's a link to the 10 usability heuristics you can use when conducting heuristic evaluations for an open source projects UI.

On tools, that is tools for better thinking. It's really nice for developing your problem solving and thinking capability as a designer and you should definitely check that out. Checklist design is a collection of checklists that help you make sure you're not forgetting any important elements when designing screens for your open source project.

And open design now is a book that talks about open design, which is a very similar concept to open source design. So reading this book would help you understand the future of design and open design as it is. And here's a link to CC licenses that help you understand the different types of creative licenses and creative commons licenses available and how

you can take advantage of each one. So the great part is you can find more of these links on opensourcedesign.net slash resources. I feel this is a goldmine for every open source designer

and it's definitely something that you should check out. You'll find a lot of free tools and resources that you can use in your work. So thanks to these amazing people. We have all these beautiful images. I have showcased in my presentation and the resources

were obtained from opensourcedesign.net. So thank you to these amazing people and thank you for listening to me while I talked about the open source designers toolbox. I hope that you will find some of these resources and tools beneficial and valuable in your work. And I hope they encourage you to continue in your open

source design career. You can find me on Twitter at Abigail, Abigail underscore map, or you can visit my website, AbigailMakubo.com where you'll find links to my other social media profile. So thank you for listening. I really do look forward to seeing more designers

contribute to open source. Let's make open source more beautiful and usable. Thanks.

Okay, the Q&A should be starting soon. Keeping an eye on the main room. Lots of claps.

Okay, we are in the main room. We have a, there is a first question. It is, what are some good resources to find background images for websites and also icons? Do you know, do you have any recommendations, Abi?

Yes, I would recommend on splash and pixabay and there's also the creative commons gallery. So I think there are links to that in my presentation slides as well. So there's a lot actually.

So lots of praise coming in for your talk and the presentation, like the layout of the presentation. I have a question if nobody else has a question. What do you, what do you want to see more of from

designers in open source Abi? I definitely love to see more programs encouraging designers to contribute. So we have like GSoC and Ritchie and as at the last time I checked out Ritchie, I noticed that there were a lot of projects for developers, but not as many

for designers and that was very encouraging. So seeing more projects and programs like that would be great. I'd also like to see more conversations between designers contributing to a particular project and I'll also love to see more designers work collaboratively with other designers on projects that are just open like

open design. I definitely love to see more of that. For sure. Yeah, me too. I cannot agree more about that last point about more designers collaborating together. We might get cut off really soon. So we're