Bernard Tyers

Every year we take some time to introduce the Open Source Design collective, what we do, where to find us and how to get involved.

In this session, FOSS projects as given time to present and ask for contributions to the designers in the room. Each project is given 2 minutes to present. In those 2 minutes, they should briefly introduce the project, explain what design help they need, and provide contact details so designers can reach them after FOSDEM.

The Open Source Design collective will use the information to submit a "job" for each project to the Open Source Design "jobs board" (https://opensourcedesign.net/jobs/), so that the request for design help reaches not just the designers in the room, but also the wider design community.

In 2020, with funding from Mozilla and CZI, the pip packaging team improved pip for all users. These focused on improving the depedenecy resolution for Python packages, and the user experience for all Python users.

We carried out usability testing, user research and improved error and information messages for pip.

This talk will be about these improvements - we'll explain how the new dependency resolver works, what it can (and can't do!), how we improved the user experience of pip, the challenges we faced, and why improving user experience is important for open source software.

This talk with be given by members of the pip team - Pradyun Gedam, Georgia Bullen, Bernard Tyers, and Nicole Harris

During 2020 we spent the year working with the maintainers of pip, the Python package manager. The project was to implement a new dependency resolver and improve pip's usability. It was a difficult project as personally, I knew very little about software package managers apart from doing "pip install". How do you do UX design with a piece of software used by hundreds of thousands (possibly millions!) of users on a small budget? Where do you find those users? Combined with this the maintainers were under pressure to do a lot of complicated work in a short period of time.

This session will be a recorded discussion between the UX designers and the pip maintainers. We'll talk about what it was like to spend a year working together, the challenges, and the lessons we can teach others. We'll leave 5 minutes (approx) at the end for Q&A.

Every year we take some time to introduce the Open Source Design collective, what we do, where to find us and how to get involved.

If you contribute to a free / open source project in need of design contributions, come and pitch it to the designers in the room.

In this session, FOSS projects as given time to present and ask for contributions to the designers in the room. Each project is given 3 minutes to present. In those 3 minutes, they should briefly introduce the project, explain what design help they need, and provide contact details so designers can reach them after FOSDEM.

The Open Source Design collective will use the information to submit a "job" for each project to the Open Source Design "jobs board" (https://opensourcedesign.net/jobs/), so that the request for design help reaches not just the designers in the room, but also the wider design community.

A brief introduction to the Open Source Design collective.

Every year we take some time to introduce the Open Source Design collective, what we do, where to find us and how to get involved.

We will close the Open Source Design devroom with a few words from all the collective and some comments from the people attending.

This is one of the sessions we run every year.

This talk will be about establishing good ethical guidelines and standards for user research for the SecureDrop project. The 2 speakers have contributed to SecureDrop, an open-source software platform for secure communication between journalists and whistleblowers.

This talk will be about how we established good ethical guidelines and standards for user research for the SecureDrop project. The 2 speakers have contributed to SecureDrop, an open-source software platform for secure communication between journalists and whistleblowers.

It will focus on why ethical research is important in user-centred design, how to do ethical user research in open source projects. It will also explain how to establish a trusting relationship with participants.

This session will be the opening session of the Open Source Design devroom. We will have a short introduction to the Open Source Design collective, what we do, who we are.

We also welcome new comers to FOSDEM, user-centred design, or open source to introduce themselves, tell us a little bit about the work they do, and what they're looking to learn or find out.

It is a good opportunity to meet potential collaborators and make new friends. ☺️

Getting HCI MSc students involved in open source software!

Whats not to like!

I've had agreement from a university in London to propose a number open source software projects to a HCI masters programme for studnets to carry out usability evaluations as part of their MSc in HCI programme.

I would like to do a short 10 maybe 15 mins proposal to members of established open source projects which would be able to take the feedback from "the top 2%" of student evaluations and incorporate them into their software.

I would outline what the criteria for the projects would be (still to be decided), and also what the students would do for the project and how they would send the recommendations to them.

Essentially, it's a gathering of interest exercise. It'll be super quick. Please accept me!

I'd be happy to do this at the end of the day combined with something else if necessary.

"How can I contribute?" is a panel discussion for everyone who works in "design" (visual designers, graphic designers, interaction designers, researchers).

This discussion panel is for people like me: people who use open source software daily, who promote open source software to others, and who want to contribute to open source projects but aren't sure where to start. The panel will be made up of designers, researchers, and developers who are already working in open source software.

The goal will be to give the audience some beginning steps to make a start in contributing to OSS projects. The panel will begin the discussion, and the objective will be to take questions from the audience.

This panel is for people like me: people who use open source software daily, who promote open source software to others, and who want to contribute to open source projects but aren't sure where to start.

The goal of the panel will be to give the audience some beginning steps to make a start in contributing to OSS projects. The panel will be made up of designers, researchers, and developers who are already working in open source software, and the discussion will focus on:

• How to identify what project(s) you want to contribute to (What are you interested in?)
• Where to find open source projects (Github, Sourceforge)
• How to make the first connection with a project
• How to make your first contribution

The panel will begin the discussion, and the objective will be to take questions from the audience.

4 years ago, the UK set up Government Digital services. The objective was to build "digital by default" government services for the UK public which were "simpler, clearer and faster".

User research, user centred design and open source technologies are central to building services that meet GDS's standards.

This session will be an overview of some projects I've worked on showing how user research and design is done in the open, and will discuss limitations of the government "open source" approach.

4 years ago, the UK set up Government Digital services. The objective was to build "digital by default" government services for the UK public which were "simpler, clearer and faster".

User research, user centred design and open source technologies are central to building services that meet GDS's standards.

Right now the if a member of the public has some research or design input, they themselves are unable to commit a change to it, it's not possible for them to get their "patches" seen, or it is very rare. Why is this?

This session will be an overview of some projects I've worked on showing how user research and design is done in the open, how we try to open source our work where possible, and why we don't when it is not possible.

The session will ask the following questions:

• Is this really open source?

• How could that be improved?

• Does it matter?

Closing remarks for the Open Source Design devroom