---
# System prepended metadata

title: FOSDEM presentation

---

# FOSDEM presentation

- [Issue](https://github.com/BitcoinDesign/Meta/issues/58) (lots of info here)
- A [conference](https://fosdem.org/2021/schedule/) about open-source on Feb 6 & 7
- Video needs to be recorded and uploaded by Jan 13
- We have 20 minutes, 15 minutes for the talk, 5 minutes for questions

## Talk outline

As per the [schedule](https://fosdem.org/2021/schedule/event/design_bitcoin_for_everyone/).

**Title**
Design Bitcoin for Everyone

**Sub-title**
How we practice and spread open design to make Bitcoin more intuitive and accessible

**Description**
Since the middle of 2020, an open community has formed around the goal of making Bitcoin more intuitive and accessible. Our big project is a Bitcoin Design Guide to help both designers and developers create better Bitcoin experiences faster. We also work to promote the idea of open design, to bring more designers into the space, and to help open-source projects adopt better design processes. This presentation will provide an overview of all these efforts, where we are (early) and what the future might hold.

## rC3 talk reference

A talk we did on Dec 28, which we **can** use as a starting point.

- Duration was 1 hour
- Live presentation via Jitsi to around 35 people
- Overall approach was to introduce the community and guide as pretty new efforts, explain our goals and where we are, and be open for discussion and collaboration
- This was a talk for very technical Bitcoiners. The FOSDEM audience is different
- Structure (6 parts, each 10 minutes)
    - Intro to bitcoin design (community and guide)
    - Getting started
    - Onboarding
    - Private key management
    - Payments
    - What's next
    - Open discussion
- [Slides](https://www.figma.com/file/1VtKn5VJ13E1RdMGLkiiXZ/rC3-slides?node-id=1%3A65)
- [Video summary](https://youtu.be/XkdE31YE5rc)

## Considerations

- Who is our audience?
    - Open-source designers
    - Can't expect familiarity with Bitcoin
    - Probably very passionate and/or experienced, as they are showing up at an open-source conference

- What do we want people to take away from this presentation?
    - Learn about who we are, what our goals are, what we've done so far
    - Learn about unique aspects of open-source design around Bitcoin
    - Learn about our processes and the resources we are working on to help in their own work

- What do we want from this presentation?
    - Get feedback on our approach and methods and learn from others
    - Get more visibility
    - Open doors for other open-source designers to contribute
    - Spark interesting conversations
    - Find other projects and efforts we can contribute to
    - Meet people
    - Strengthen the concept of open design

## Concept #1

Idea
- Take the rC3 talk as a base
- Collaborate on the presentation slides
- Have one of us record the presentation
- Have all of us be available for Q&A 

Advantages
- Everyone can shape the presentataion and Q&A
- Singular voice for presentation
- Simple recording process as just one person involved

Disadvantages
- Only one person visible in the presentation
- _________________________________________________
- Patricia - This seems like the best option given the deadline. Would be great to see more faces and hear more voices but editing well could take a while to complete.

## Concept #2

Same as #1, but have multiple people record parts of the presentation. One person records the intro, another a portion about the guide, etc.

Advantages
- More people visible to showcase community effort better

Disadvantages
- More complex video editing
- Need to ensure it flows well - more preparation needed

## Concept #3 

Give all participants a chance to talk about their role in bitcoin design. For example, 5 people each have 3 minutes to talk about why they care about bitcoin design, the change they want to bring about, or something else they want to share or have a conversation about.

Advantages
- More diverse voices on more diverse topics

Disadvantages
- Potentially no clear takeaway unless we do sync this beforehand (which we can choose that we want)