/Meta

Discussions around the processes and coordination of the Bitcoin Design Community

Bitcoin Design - Meta

community, project-management, process

Activity in the Bitcoin Design community largely happens in the Slack workspace and here on Github, but also in the various projects our contributors are involved in.

This repository is used for organizing calls, group consensus and coordination. The Guide repository is for the Bitcoin Design Guide we are working on, which is a design reference for anyone building open-source bitcoin products.

Community activity is fluid, but here are a few important starting points:

How to get involved in the community

  1. Join the community on Slack
  2. Subscribe to the newsletter to stay up-to-date
  3. Read up on our project life cycle
  4. Browse issues for upcoming calls and discussions around processes and coordination
  5. Subscribe to our calendar to stay up-to-date with calls and events we organize

How to get involved in projects

  1. Browse issues labelled as projects
  2. Browse and post ideas in the #project-ideas Slack channel
  3. See projects for a few project ideas
  4. Contribute to the Bitcoin Design Guide

Bitcoin Design Guide

Further Slack channels

The Bitcoin Design calendar

Our calendar (an .iCal file) includes upcoming calls (community calls, design review calls, etc). Qualified issues are automatically added to the calendar, which you can then subscribe to via your favorite calendar tool.

  • Copy this URL: https://raw.githubusercontent.com/BitcoinDesign/Meta/calendar/events.ical
  • In Apple Calendar (desktop), use File -> New calendar subscriptions
  • In Google Calendar (web), click the small + icon next to Other calendars in the sidebar and select From URL
  • Paste the URL and save. New events (if there are any scheduled) should show up right away
  • In Thunderbird (desktop), New Calendar > On my network > iCalendar (ICS) and paste the calendar link in the location field.
  • Calendar tools regularly reload subscribed calendars for updates. How often this happens varies by tool

There are two requirements for an issue to be included:

  • The issue needs to include a UTCTime meta property following this format: UTCTime: 2020-10-14 9:00 UTC -7. You can seen an example here
  • A maintainer needs to add the call label to the issue (this prevents spam)
  • The calendar auto-updates whenever a new issue is created, or an existing issue is edited