BitcoinDesign
      • Sharing URL Link copied
      • /edit
      • View mode
        • Edit mode
        • View mode
        • Book mode
        • Slide mode
        Edit mode View mode Book mode Slide mode
      • Customize slides
      • Note Permission
      • Read
        • Owners
        • Signed-in users
        • Everyone
        Owners Signed-in users Everyone
      • Write
        • Owners
        • Signed-in users
        • Everyone
        Owners Signed-in users Everyone
      • Engagement control Commenting, Suggest edit, Emoji Reply
    • Invite by email
      Invitee

      This note has no invitees

    • Publish Note

      Share your work with the world Congratulations! 🎉 Your note is out in the world Publish Note

      Your note will be visible on your profile and discoverable by anyone.
      Your note is now live.
      This note is visible on your profile and discoverable online.
      Everyone on the web can find and read all notes of this public team.
      See published notes
      Unpublish note
      Please check the box to agree to the Community Guidelines.
      View profile
    • Commenting
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
      • Everyone
    • Suggest edit
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
    • Emoji Reply
    • Enable
    • Versions and GitHub Sync
    • Note settings
    • Note Insights New
    • Engagement control
    • Make a copy
    • Transfer ownership
    • Delete this note
    • Insert from template
    • Import from
      • Dropbox
      • Google Drive
      • Gist
      • Clipboard
    • Export to
      • Dropbox
      • Google Drive
      • Gist
    • Download
      • Markdown
      • HTML
      • Raw HTML
Menu Note settings Note Insights Versions and GitHub Sync Sharing URL Help
Menu
Options
Engagement control Make a copy Transfer ownership Delete this note
Import from
Dropbox Google Drive Gist Clipboard
Export to
Dropbox Google Drive Gist
Download
Markdown HTML Raw HTML
Back
Sharing URL Link copied
/edit
View mode
  • Edit mode
  • View mode
  • Book mode
  • Slide mode
Edit mode View mode Book mode Slide mode
Customize slides
Note Permission
Read
Owners
  • Owners
  • Signed-in users
  • Everyone
Owners Signed-in users Everyone
Write
Owners
  • Owners
  • Signed-in users
  • Everyone
Owners Signed-in users Everyone
Engagement control Commenting, Suggest edit, Emoji Reply
  • Invite by email
    Invitee

    This note has no invitees

  • Publish Note

    Share your work with the world Congratulations! 🎉 Your note is out in the world Publish Note

    Your note will be visible on your profile and discoverable by anyone.
    Your note is now live.
    This note is visible on your profile and discoverable online.
    Everyone on the web can find and read all notes of this public team.
    See published notes
    Unpublish note
    Please check the box to agree to the Community Guidelines.
    View profile
    Engagement control
    Commenting
    Permission
    Disabled Forbidden Owners Signed-in users Everyone
    Enable
    Permission
    • Forbidden
    • Owners
    • Signed-in users
    • Everyone
    Suggest edit
    Permission
    Disabled Forbidden Owners Signed-in users Everyone
    Enable
    Permission
    • Forbidden
    • Owners
    • Signed-in users
    Emoji Reply
    Enable
    Import from Dropbox Google Drive Gist Clipboard
       Owned this note    Owned this note      
    Published Linked with GitHub
    • Any changes
      Be notified of any changes
    • Mention me
      Be notified of mention me
    • Unsubscribe
    # Figma Config 2021 - Proposal Planning _[Call for proposals](https://sessionize.com/config2021)_ _[FOSDEM planning notes](https://hackmd.io/ffdomNWPRCiW2eQbXda9PQ)_ - Audience - Figma users - Designers who may be unfamillair with bitcoin, open design, and open source - Goals of the presentation - ... - Represent many voices in the community - Define the ideas of open design, open collaboration, and the role of an "open designer" ## Concept #1 - Challenges of designing a new, borderless version of money (5m) - What is Bitcoin and why it is unique - Design communities (5m) - Why we gathered - Open design (5m) - See [page in the guide](https://bitcoin.design/guide/getting-started/open-design/) - A familiar design processes (5m) - Research - Workshops and design sprints - Taking a UI inventory - Project Briefs - Collaborating - Figma - difficulties around public collaboration and lack of Github-like features - How can you contribute? (5m) - Remote collaboration - Participating in calls - Why we have calls? - Contribute to the guide - Review others work ### Talk format ideas See the [FOSDEM planning notes](https://hackmd.io/ffdomNWPRCiW2eQbXda9PQ). FOSDEM was pre-recorded, so we had flexibility with editing. We need to find out if and how we can have multiple people present together. - Idea 1: Like FOSDEM, play a community intro video, then one person presents (logistically easy) - Idea 2: Like rC3, multiple people present, one section each ### Planning Call Notes - We're figuring it out, in open source. Embrassing the mess. - We are shifting what it means to even be a team. A group of people with a common interest that is bitcoin. Sharing resources, learning, creating design processes, and collaborating with projects to solve UX issues. #### Goals - introduction to bitcoin design - raise awareness that we exist - appreciation of why designing for bitcoin is different from in-house design or open design because of its global nature. - output. projects that have kicked off, and the processes we have. - differences between open design and in-house design. - Principals, What we value - Embrace diversity - Your contributions have an impact. **FOSDEM abstract for reference** 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. #### Goals as a story #3 - We want to introduce attendees to the bitcoin design community, and provide some foundations on what it means to work in design for an open, global financial protocol without leaders. - There are no leaders, but there are principals that bind individual contributors and collective efforts of others in the ecosystem. One of the goals of our design community is to educate new designers in the space about these principals, and provide a friendly enviroment to learn and experiment. while making outputs that have a tangiable impact. - Coordinating such a community, takes effort, and tools are limited, ... knowledge sharing ... and even the smallest contributions have can have a direct and tangiable impact... - We have a diverse set of people, with just as diverse perspectives. We want to give a glimpse of our community, and share what we have learnt with the Figma Config audiance. To give them a perspective they may not have had to a new style of work and collaboration. --- Embrace diversity - example of baking potatoes ~~and chainsmoking~~ on Jitsi :) - be yourself, countries, time zones, etc Principles as what ties us together - while many other things are messy. --- Things to maybe bring up - Design community - Mix of volunteers and dedicated - A loosely organized group of people with varying backgrounds - New, seasoned, technical, etc - Code review vs design review - Volunteer, paid, funded --- Reviewing culture in the bitcoin design community. - Lead by example. - Point out the faults. - Not as subjective as something like art. A lot of things you design are not for your self. - With the guide youre not creating things for yourself, its for others to be useful. - Like client work, you have freedom, not so corporate. - Developers already go through a lot of scrutiny for their code. How do they deal with that feedback? - Code editor helps you keep consistent. - Variable names are too short. - When you compile your code, it - Archetecture. - Externally imposed rules and group rules. guide resources collaborations - individuals - groups you can do ssomething alone. but if you want to acheive something bigger, there will be compromise and you need to work within a larger group. its up to you to choose if youd like to do something more indepemend, or soemthing more collective colalboration which can have a bigger impact, but would require you to be more flexible, and participate more. in either case, you have acccess to peers who also care very deeply about these topics to get feedback from. we#re building the future of money so you will not be able to solve all the problmes alone. we need to have synergy!!!!! concensus building. ###### open design / participants finding a systematic way to deal with these things. if everyone had to do it themselves, it would take a lot longer. ###### improving design in a space which is under represented or deserves more attention and effort bringing creativey to industries which ###### increasing inclusion in parts of the world that need to be developed market and societal dynamics do not support certain areas and there needs to be more funding to fill those gaps. ux clinic - are there other rooms going on? --- Figma call asks Opportunities to showcase community & diversity 1. 3-4 presenters, each one going over one section 2. Start with a community video 3. Showcase people in the content 4. Open session (chat room) at the Conference 5. Event before or after the conference Call setup - Is it one video conference call that gets broadcast, making it easy for multiple people to join - Prerecording at FOSDEM was great for the intro video because it allowed us to avoid technical switcheroo - Is it one stream or are there multiple tracks happening at the conference? - Are there any other open design or bitcoin talks? ### UPDATE 2020-03-17 / CALL WITH FIGMA CONFIG TEAM - Unfortunately only two speakers, Johns and Christoph. This did not go the way we wanted and what we had discussed together. Going to weave more personal stories in the presentation, see if we can do another community intro video and get more people involved during the presentation via chat, breakout rooms, etc - Next week we will be doing tech checks with the producers of the conference. - Find out how we can use pre-recorded video - Learn more about using polls during the presentation - Are there options for breakout rooms where more of us can participate After the conference we can follow up with attendees - Figma is able to distribute a message with a call to action to the particpants as a follow up after the conference. Idea: We can write up a welcome letter with a link to the newsletter and website. - The Youtube description on the uploaded video will be timestamped, and can have additional links and information included. Other details - Anyone is free to sign up, watch all talks, and join chats. - They like our rough [presentation outline in Figma](https://www.figma.com/file/aWb4a85YPlKhucQNAMt45P/Figma-Config-slides?node-id=165%3A0) (work-in-progress, a variation of the FOSDEM presentation). How can you participate? - Help come up with some short poll questions to send out during the talk. [Edit the poll ideas document](https://hackmd.io/@BitcoinDesign/ByNBXngNu/edit). - Register for the conference as an attendee and attend the talk. [Fill out this form to be notified when registration opens](https://docs.google.com/forms/d/e/1FAIpQLSdx8-ouptgaSoET_R4ICKIizIB0ns7Kw6t03_r5LUqngGkDfA/viewform). - Help [review the presentation](https://www.figma.com/file/aWb4a85YPlKhucQNAMt45P/Figma-Config-slides?node-id=165%3A0). - Attend the work session on [Tuesday @ 9:00am PST](https://everytimezone.com/s/67974f1f) - Have some people from the bitcoin design community hang out in the chat room for the talk with "(bitcoin.design)" in their name to help answer questions. Please state your interest. --- ## March 23 work session Structure 1. Cover/intro 2. The case for a Bitcoin design community 3. What we're doing 4. Primer on open design 5. How you can get involved 6. Wrap-up ### 1. Cover/intro Figma will have a slide introducing the talk, so we may not need one. Still good to have a brief "We're so and so, here to represent the Bitcoin Design Community, etc". ### 2. The case for a Bitcoin design community Point of this section is to frame Bitcoin in a specific way that leads us to why there is a need for design community. - Bitcoin is global money - As such, it's only as good as it is accessible and usable by as many people as possible - Technically so much is possible, but user experiences are lacking - There's a global audience of users and builders, so keeping the community decentralized is natural (there's no single, "correct" UX) - Designers were scattered, a community can help provide a healthy place to flourish - Bitcoin is open-source, so we're embracing open design ### 3. What we're doing Show the practical output of the community. Distinguish between the more formal organization by regular contributors and the independent solo and project efforts. So what does this community do? Go over... - Website - Slack - Github - Newsletter - Calls - Solo projects - Design guide - Design resources - Collaborations A complex web of activity. ### 4. Primer on open design Provide the framework of how to think about all this activity, the role of the individual participant. This is the theory behind the previous section. - It's about lowering barriers of participation - Balancing individual freedom and passion with projects for the "greater good" - Focus on community - Letting efforts grow through organic collaboration - Process of review, critique and consensus-finding - Reference Project life-cycle document? - Embracing diversity - backgrounds, countries, languages, expertise, availability, etc - Discuss volunteering ----- Funding ### 5. How you can get involved Offer simple methods that viewers can choose to get involved. Provide a one-line (short) vision that might get 'em pumped. - "Cutting-edge design of the future of money with a ton of creative freedom" Methods - Join, hang out, share your perspective - Review work - Pick up a small task (banner image, icons) - Join a project - Initiate a new project ### 6. Wrap-up Say thanks. Where to find us. Offer direct contact in chat, post-conference events, etc. --- ### Tech check notes Azra Daniels - Marketing & events Vanessa Chung - Community Tim McAfee - Premier events Design system to culture to the state of the world 4 talks, 60 speakers Two monitors, notifications off, look straight, drink water, solid color shirt, download stuff beforehand? Dont look down or off to the side. Wired internet connection if possible. No one else on the connection if possible. Reduce CPU and memory usage. Natural backgrounds and light are best. Eye level camera. Headsets are best with attached mic. Can use free account in free streamyard Polls are possible, should plan for them OK to have community members in the chat to answer questions

    Import from clipboard

    Paste your markdown or webpage here...

    Advanced permission required

    Your current role can only read. Ask the system administrator to acquire write and comment permission.

    This team is disabled

    Sorry, this team is disabled. You can't edit this note.

    This note is locked

    Sorry, only owner can edit this note.

    Reach the limit

    Sorry, you've reached the max length this note can be.
    Please reduce the content or divide it to more notes, thank you!

    Import from Gist

    Import from Snippet

    or

    Export to Snippet

    Are you sure?

    Do you really want to delete this note?
    All users will lose their connection.

    Create a note from template

    Create a note from template

    Oops...
    This template has been removed or transferred.
    Upgrade
    All
    • All
    • Team
    No template.

    Create a template

    Upgrade

    Delete template

    Do you really want to delete this template?
    Turn this template into a regular note and keep its content, versions, and comments.

    This page need refresh

    You have an incompatible client version.
    Refresh to update.
    New version available!
    See releases notes here
    Refresh to enjoy new features.
    Your user state has changed.
    Refresh to load new user state.

    Sign in

    Forgot password

    or

    By clicking below, you agree to our terms of service.

    Sign in via Facebook Sign in via Twitter Sign in via GitHub Sign in via Dropbox Sign in with Wallet
    Wallet ( )
    Connect another wallet

    New to HackMD? Sign up

    Help

    • English
    • 中文
    • Français
    • Deutsch
    • 日本語
    • Español
    • Català
    • Ελληνικά
    • Português
    • italiano
    • Türkçe
    • Русский
    • Nederlands
    • hrvatski jezik
    • język polski
    • Українська
    • हिन्दी
    • svenska
    • Esperanto
    • dansk

    Documents

    Help & Tutorial

    How to use Book mode

    Slide Example

    API Docs

    Edit in VSCode

    Install browser extension

    Contacts

    Feedback

    Discord

    Send us email

    Resources

    Releases

    Pricing

    Blog

    Policy

    Terms

    Privacy

    Cheatsheet

    Syntax Example Reference
    # Header Header 基本排版
    - Unordered List
    • Unordered List
    1. Ordered List
    1. Ordered List
    - [ ] Todo List
    • Todo List
    > Blockquote
    Blockquote
    **Bold font** Bold font
    *Italics font* Italics font
    ~~Strikethrough~~ Strikethrough
    19^th^ 19th
    H~2~O H2O
    ++Inserted text++ Inserted text
    ==Marked text== Marked text
    [link text](https:// "title") Link
    ![image alt](https:// "title") Image
    `Code` Code 在筆記中貼入程式碼
    ```javascript
    var i = 0;
    ```
    var i = 0;
    :smile: :smile: Emoji list
    {%youtube youtube_id %} Externals
    $L^aT_eX$ LaTeX
    :::info
    This is a alert area.
    :::

    This is a alert area.

    Versions and GitHub Sync
    Get Full History Access

    • Edit version name
    • Delete

    revision author avatar     named on  

    More Less

    Note content is identical to the latest version.
    Compare
      Choose a version
      No search result
      Version not found
    Sign in to link this note to GitHub
    Learn more
    This note is not linked with GitHub
     

    Feedback

    Submission failed, please try again

    Thanks for your support.

    On a scale of 0-10, how likely is it that you would recommend HackMD to your friends, family or business associates?

    Please give us some advice and help us improve HackMD.

     

    Thanks for your feedback

    Remove version name

    Do you want to remove this version name and description?

    Transfer ownership

    Transfer to
      Warning: is a public team. If you transfer note to this team, everyone on the web can find and read this note.

        Link with GitHub

        Please authorize HackMD on GitHub
        • Please sign in to GitHub and install the HackMD app on your GitHub repo.
        • HackMD links with GitHub through a GitHub App. You can choose which repo to install our App.
        Learn more  Sign in to GitHub

        Push the note to GitHub Push to GitHub Pull a file from GitHub

          Authorize again
         

        Choose which file to push to

        Select repo
        Refresh Authorize more repos
        Select branch
        Select file
        Select branch
        Choose version(s) to push
        • Save a new version and push
        • Choose from existing versions
        Include title and tags
        Available push count

        Pull from GitHub

         
        File from GitHub
        File from HackMD

        GitHub Link Settings

        File linked

        Linked by
        File path
        Last synced branch
        Available push count

        Danger Zone

        Unlink
        You will no longer receive notification when GitHub file changes after unlink.

        Syncing

        Push failed

        Push successfully