[bisq-network/dao] Using GitHub discussions within the Bisq DAO (#1)

[Chris Beams]

_TL;DR: This message is a "GitHub discussion". I and the other @bisq-network/team-leads will start using them for important announcements and communications, and everyone within the DAO is welcome to use them as well._

If you're receiving this message, it's because you are a member of the @bisq-network/dao team on GitHub. That team includes (or should include) every active contributor.

I'm sending this out now because we've just decided to start using GitHub discussions within the @bisq-network/support team, and @wiz has just started using them with the @bisq-network/ops team as well. For example, see his latest [Ops team announcements][1] post.

Starting to use Discussions changes nothing about our use of Keybase, which is working very well and will remain our day-to-day communication hub. But we shouldn't rely on Keybase for anything that's really important. There are too many messages, and the fundamental nature of Keybase, Slack, et al is that they are ephemeral communication platforms. No one should be expected to have to read all messages in all channels or to catch up on them after being away.

Discussions are great for the kind of communications that we really want others to see and possibly respond to. For example, this announcement about using Discussions is a great use of Discussions! All Bisq DAO contributors will receive this message via email (depending on their GitHub notification settings), and most people do at least scan all their email messages so there's a good chance all contributors will see this.

I've been trying lately to start using the bisq-contrib mailing list more often, but in the end I'll think we'll be much better off embracing Discussions. The mailing list is a completely separate system that requires everyone to subscribe, and most haven't. Furthermore, Discussions allow for broad communications (like this one), or fine-grained communications down to any individual nested GitHub team.

By default, all Discussions are visible to all members of the Bisq GitHub organization. You'll automatically receive discussion notifications for any team you're directly a member of, because when you get added to a team, GitHub automatically adds a "Watch" for you on that team's discussions. However, anyone can put a watch on any team, even if you're not a member of it.

To learn more about the various features of Discussions, I recommend reading the (rather brief) [documentation][2].

Feedback and questions are welcome, of course. Just reply (via email or web) to this discussion!

[1]: https://github.com/orgs/bisq-network/teams/ops/discussions/1
[2]: https://help.github.com/en/github/building-a-strong-community/about-team-discussions

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/orgs/bisq-network/teams/dao/discussions/1
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20200205/6d2fbde7/attachment-0001.html>