Skip to content

Commit

Permalink
Discord move & design review updates (#518)
Browse files Browse the repository at this point in the history
Replaced all Slack references and links with Discord ones. Except for links to specific conversations, and the domains doc, which seems a bit like a contract which I'll treat separately.

Also renamed the design crits back to design reviews, since I have taken that process over again a few months ago and find that title simpler.
  • Loading branch information
GBKS authored Apr 20, 2023
1 parent aee29a8 commit a32d213
Show file tree
Hide file tree
Showing 6 changed files with 25 additions and 26 deletions.
2 changes: 1 addition & 1 deletion Code-of-Conduct.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@

## No Scam Rule

The Bitcoin Design Slack is not intended to be used for discussing trading or investment strategies. Please do not post in a channel about, or direct message any member to discuss, the following:
The Bitcoin Design Discord is not intended to be used for discussing trading or investment strategies. Please do not post in a channel about, or direct message any member to discuss, the following:

- Crypto trading
- Investment strategies
Expand Down
2 changes: 1 addition & 1 deletion Collaboration.md
Original file line number Diff line number Diff line change
Expand Up @@ -13,7 +13,7 @@ An existing project is looking for resources and expertise to improve their prod
Ways the project can choose to interact with the community:

1. Review the [guide](https://bitcoin.design/guide/) to find a direction or solution
1. Engage in Slack conversations to share ideas and get feedback
1. Engage in Discord conversations to share ideas and get feedback
1. Participate in a design review session

Our role in this scenario is to be a helpful partner in providing resources and feedback.
Expand Down
15 changes: 8 additions & 7 deletions Community-Calls.md
Original file line number Diff line number Diff line change
Expand Up @@ -31,21 +31,21 @@ Some examples:

- An issue is created 1-2 months earlier
- They appear on the [calendar](https://bitcoin.design/calendar/)
- Two @channel message are sent out on Slack, the first one 1 week ahead, and the second one 1 day ahead of the call
- A regular Slack post in the #general channel is sent out shortly before the call
- Two #announcement messages are sent out on Discord, the first one 1 week ahead, and the second one 1 day ahead of the call
- A regular Discord post in the #general channel is sent out shortly before the call
- For Twitter Spaces, the Space is shared via a Tweet when it starts

**What tools do we use?**

For most calls, we have used [Jitsi](https://jitsi.org), which is open-source, doesn't require you to create an account, and is available as web, mobile and desktop applications.

More recently, we have switched to Twitter Spaces to experiment with the audio format and allow for a more publicly accessible conversation.
More recently, we have experimented with Nostr Nests and Twitter Spaces to experiment with the audio format and allow for a more publicly accessible conversation.

**Are calls recorded?**

We did not record Jitsi calls initially but started to do so due to community requests. Calls are only recorded if all participants agree, and are uploaded to our [BitcoinTV]([BitcoinTV](https://bitcointv.com/a/bitcoin_design/videos)) account, and [YouTube channel](https://www.youtube.com/channel/UCXKST1b8Wmq8Zt6b6S_-k3Q) in the [Community Calls playlist](https://www.youtube.com/playlist?list=PLpV0KfVOMoja_zmmFNSJXREVKE4PSU0M1).
We did not record Jitsi calls initially but started to do so due to community requests. Calls are only recorded if all participants agree, and are uploaded to our [BitcoinTV]([BitcoinTV](https://bitcointv.com/a/bitcoin_design/videos)) account, and [YouTube channel](https://www.youtube.com/@BitcoinDesign) in the [Community Calls playlist](https://www.youtube.com/playlist?list=PLpV0KfVOMoja_zmmFNSJXREVKE4PSU0M1).

Calls via Twitter Spaces are automatically recorded by Twitter and public in nature. They are audio-only, but we still post them on our video channels (with a static image for the visual).
Calls via Nostr Nests and Twitter Spaces are automatically recorded by Twitter and public in nature. They are audio-only, but we still post them on our video channels (with a static image for the visual).

**Are calls transcribed?**

Expand All @@ -61,12 +61,13 @@ Recordings uploaded to BitcoinTV or YouTube should include timestamps, so viewer

**Things to consider when hosting calls**

- It can be a two-person job. One person to lead the conversation, and a second person to post on Slack and Twitter, take notes, keep an eye on time, etc
- It can be a two-person job. One person to lead the conversation, and a second person to post on Discord and Twitter/Nostr, take notes, keep an eye on time, etc
- It's a community call - make sure to open the floor to everyone interested in chatting
- In open chat sessions, it is helpful to quickly gather topics at the beginning. This helps participants understand what to expect and makes it easier to manage time
- Announce the 1-hour mark of the call, make it OK for anyone to continue chatting or leave
- Twitter Spaces calls initially require inviting speakers and co-hosts, pinning relevant Tweets to the space, and tweeting links that were discussed
- Nostr Nests and Twitter Spaces calls initially require inviting speakers and co-hosts, pinning relevant Tweets to the space, and tweeting links that were discussed
- Twitter Space recordings can be obtained by downloading an archive of the Bitcoin Design account, which takes 24 hours until it is available
- Nostr Nests calls need to be recorded by a participant during the call

**Who organizes calls**

Expand Down
22 changes: 10 additions & 12 deletions Bitcoin-Design-Crits.md → Design-Reviews.md
Original file line number Diff line number Diff line change
@@ -1,28 +1,28 @@
# Bitcoin Design Crits
# Bitcoin Design Reviews

Bitcoin Design Crits are opportunities for bitcoin products to get design critiques (crits) on a particular feature, page or aspect of their product. Actionable suggestions for improving usability, user interface, interaction, and visual aesthetics are given by members in the Bitcoin Design Community.
Design reviews are opportunities for bitcoin products to get design critiques on a particular feature or aspect of their product. Actionable suggestions for improving usability, user interface, interaction, and visual aesthetics are given by community members.

## How does it work?

1. A bitcoin product submits a page or section they want reviewed on Bitcoin Design Crits in the [#bitcoin-design-crits](https://bitcoindesign.slack.com/archives/C019MTNFKL7) channel in our Slack.
1. A bitcoin product team submits a page or section they want reviewed in a design reivew in the [#design-reviews](https://discord.gg/ss2ZbNcv32) channel in our Discord.

We will only focus on a specific part of your product, so we can give the highest amount of value. Reviewing a whole product is an extensive and involved process that is better suited to be dealt with by a dedicated Product Designer. If you need a Product Designer for your bitcoin product, reach out in the [#opportunities](https://bitcoindesign.slack.com/archives/C016D659EU9) channel in our Slack.
We will only focus on a specific part of your product, so we can give the highest amount of value. Reviewing a whole product is an extensive and involved process that is better suited to be dealt with by a dedicated product designer or a more involved process than a single call. If you need a designer for your bitcoin product, reach out in the [#opportunities](https://discord.gg/uBUHHkwTZe) channel.

2. The proposal is discussed by members of the community and a call is scheduled as appropriate.

3. Product designers interested in reviewing jump into a collaborative Figma file **PRIOR** to call, where they crit the product page or section submitted. This will all be public and open for anyone to view, in classic open-source fashion.
3. Designers interested in reviewing jump into a collaborative Figma file **PRIOR** to call, where they crit the product page or section submitted. This will all be public and open for anyone to view, in classic open-source fashion.

4. Product designers who crit the product present their feedback to the product team in the scheduled calls.
4. Designers who review the product present their feedback to the product team in the scheduled call.

Follow up help and suggestions on the feedback given is always available.
Follow up help and suggestions on the feedback given is always available. The product team and interested designers can independently organize this.

## Who can take part?

Anyone who is working on a bitcoin product. Whether its a new page or user flow you want reviewed before release, or an old one that needs polishing, Bitcoin Design Crits can help. Open-source products get priority over closed-source products.
Anyone who is working on a bitcoin product. Whether its a new page or user flow you want reviewed before release, or an old one that needs polishing, Bitcoin Design Reviews can help. Open-source products get priority over closed-source products.

Calls are recorded and published on the [BitcoinTV](https://bitcointv.com/a/bitcoin_design/videos) and [YouTube](https://www.youtube.com/@BitcoinDesign) channels, and open for anyone to join in. We greatly appreciate the pseudonymous and private nature of bitcoin and are more than happy to accommodate those who would prefer not to reveal their identity.

## What information do I need to provide for a crit?
## What information do I need to provide for a review?

- The section or page you want reviewed. We can help you identify an area that needs work if you're not sure
- Links to any design files you use in your product if you have them: Figma/Penpot file, design system, icon set, brand assets
Expand All @@ -39,6 +39,4 @@ Calls are recorded and published on the [BitcoinTV](https://bitcointv.com/a/bitc

The calls are organized to best fit the availability (and time zones) of interested participants.

Upcoming and previous Bitcoin Design Crit can be found [here](https://github.com/BitcoinDesign/Meta/issues?q=is%3Aissue+%22Bitcoin+Design+Crits%22).

You can also subscribe to our auto-updating calendar. More info [here](https://bitcoin.design/calendar/).
Subscribe to [our calendar](https://bitcoin.design/calendar/) to keep up with upcoming design reviews. Or you can browse event issues [here](https://github.com/BitcoinDesign/Meta/issues) for all upcoming and past calls.
4 changes: 2 additions & 2 deletions Projects.md
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,7 @@ Many projects start as simple ideas and grow over time with the help of many dif

### 1. Idea

- Formulate your idea and discuss it on Slack (#project-ideas) to get feedback
- Formulate your idea and discuss it on Discord (#project-ideas) to get feedback
- References, prototypes, sketches and other materials that help explain the idea are great for communicating clearly
- An idea does not have to be so specific that the outcome is clear

Expand All @@ -25,7 +25,7 @@ Many projects start as simple ideas and grow over time with the help of many dif
- A more mature idea can be posted as an issue on GitHub (in the most appropriate repository and project board) after some discussion
- We may want to create an issue template to help people enter at least the minimum information needed for others to understand and evaluate the concept
- The concept can be fleshed out further in the comment thread of the issue
- The issue becomes the central place for the concept (unlike Slack where things get lost in the feed)
- The issue becomes the central place for the concept (unlike Discord where things get lost in the feed)

### 3. Proposal

Expand Down
6 changes: 3 additions & 3 deletions README.md
Original file line number Diff line number Diff line change
@@ -1,9 +1,9 @@
# Bitcoin Design - Meta
`community`, `project-management`, `process`

Activity in the [Bitcoin Design Community](https://bitcoin.design/) largely happens in the Slack workspace and here on Github, but also in the various projects our members are involved in (see some of them [here](https://bitcoin.design/projects/)).
Activity in the [Bitcoin Design Community](https://bitcoin.design/) largely happens in the Discord server and here on Github, but also in the various projects our members are involved in (see some of them [here](https://bitcoin.design/projects/)).

Community activity is fluid, see the [contribute page](https://bitcoin.design/contribute/) on the website for all the important starting points and links, and also join the [Slack workspace](https://join.slack.com/t/bitcoindesign/shared_invite/zt-10sxfovaq-isViijl4RThKRs_TsAQnuA).
Community activity is fluid, see the [contribute page](https://bitcoin.design/contribute/) on the website for all the important starting points and links, and also join the [Discord server](https://discord.gg/K7aQ5PErht).

This repository is used for organizing calls, group consensus and coordination. The [Guide](https://github.com/BitcoinDesign/Guide) repository is for the [Bitcoin Design Guide](https://bitcoin.design/guide/) we are working on, which is a design reference for anyone building open-source bitcoin products.

Expand All @@ -13,5 +13,5 @@ Documents of note here:
- [Collaboration](Collaboration.md) - the types of design needs projects looking to collaborate with the community may have
- [Community calls](Community-Calls.md) - how we organize and run community calls
- [Domains](Domains.md) - an agreement on how domains owned by the community are governed
- [Design reviews](Design-Review.md) - how we organize and run design review calls
- [Design reviews](Design-Reviews.md) - how we organize and run design review calls
- [Social Media Guidelines](Social-Media-Guidelines.md) - how we present the community on Twitter, newsletters, etc.

0 comments on commit a32d213

Please sign in to comment.