Slack Admin

[cbeams]

This role is responsible for owning (in Slack terminology) and administering Bisq's Slack workspace at https://bisq.slack.com.

• Slack: #slack-ops
• Issues: https://github.com/bisq-network/slack
• Invites: https://bisq.network/slack-invite

---

Docs: none, other than the above
Team: @bisq-network/slack-admins
Primary owner: @m52go

[cbeams]

I've just added @ManfredKarrer as an assignee to this role, reflecting the fact that he and I in fact have Owner rights in Slack.

[cbeams]

Note that I've just created a repository for this role at https://github.com/bisq-network/slack. See bisq-network/dao#19 for details.

[cbeams]

2017.12 report

• Created the #slack-ops channel and bisq-network/slack repo to track requests and work related to Slack administration
• Did lots of normal Slack admin activities, e.g. creating channels etc.
• Kept an eye on all channels to make sure that infrastructure is working for everyone, that channel design is useful and well-understood etc.
• Encouraged everybody to keep as many conversations public as possible. As seen in the data below, it seems that this is beginning to work.
• We have 333 members currently, and had 325 at the turn of the month, which was +68 more members than we had at the beginning of December.
• The 10,000 message limit is starting to get painful. I often cannot search back to older messages, for example. I looked into how much it would cost to get on a paid plan and have unlimited message history, and it was around $1500 USD. Pretty steep for an out-of-pocket expense, so we'll hold off for now and keep making do with the limited free version.

/cc bisq-network/compensation#26

[ManfredKarrer]

1500/month or year? Per months would be really heavy...

[cbeams]

1500/month or year? Per months would be really heavy...

Per month, given our current number of active users.

[cbeams]

2018.01 report

As I mentioned a few days ago in #general at https://bisq.slack.com/archives/C0336TYTG/p1516633849000423, we're doing amazingly well at keeping our conversations public:

Otherwise, nothing remarkable to mention, other than that we've been growing our total users and active daily/weekly users pretty nicely.

As a point of reference, the Bisq Slack workspace has about 400 members and the Lightning Network Developer Slack workspace has about 1400. Not bad by comparison, given how much attention Lightning has (deservedly) been getting lately!

Anyway, here are the usual monthly stats:

/cc bisq-network/compensation#35

[cbeams]

2018.02 report

From https://bisq.slack.com/admin/stats. Note how our weekly active users stat continues to grow month over month.

/cc bisq-network/compensation#40

[cbeams]

2018.03 report

From https://bisq.slack.com/admin/stats:

/cc bisq-network/compensation#57

[cbeams]

2018.04 report

From https://bisq.slack.com/admin/stats:

We're now at 568 members.

Interesting that we doubled our storage used (from 2.6G to 5.2G) in one month this month. I imagine this has to do with how much more we're uploading Zoom call videos now, but I'm not sure.

/cc bisq-network/compensation#68

[m52go]

2019.05 Report

Nothing to report.

Slack stats for the past month are in the image below.

/cc bisq-network/compensation#294

[m52go]

2019.06 Report

Nothing to report. Been researching Riot as an alternative to Slack.

Slack stats for the past month are in the image below.

/cc bisq-network/compensation#304

[m52go]

2019.07 Report

Nothing to report.

Slack stats for the past month are in the image below.

/cc bisq-network/compensation#323

[m52go]

2019.08 Report

Nothing to report.

Slack stats for the past month are in the image below.

/cc bisq-network/compensation#361

[m52go]

2019.09 Report

Nothing to report.

Slack stats for the past month are in the image below.

/cc bisq-network/compensation#372

[m52go]

2019.10 Report

Nothing to report. As Keybase usage grows, we should probably start removing Slack links throughout docs, website, etc. and make Keybase the main communication channel (discussion needed).

Slack stats for the past month are in the image below.

/cc bisq-network/compensation#408

[m52go]

2019.11 Report

Slack is basically dead now. Slack links across the website and documentation were switched just after the month ended.

We should accomplish a full switch-over within the next month or two (see here), and at that time, this role will be closed.

/cc bisq-network/compensation#442

[m52go]

2019.12 Report

Nothing to report. Slack will be completely retired in Cycle 10 (upcoming cycle).

/cc bisq-network/compensation#471

[wiz]

@m52go since we're burning slack to the ground, can you close this role issue?

[m52go]

2020.01 Report

Slack is already effectively retired right now, as no one can sign up for a new account, but I still keep it open as a convenient way to manage IRC and Matrix messages, both of which have been getting more activity lately. In Cycle 11 we'll split up who follows IRC and Matrix to make this use of Slack unnecessary.

/cc bisq-network/compensation#497

[m52go]

Cycle 11 Report

I only monitored Slack for the #chat-bridge channel, which we're working on migrating to Keybase with a new matterbridge server. Hopefully that gets done in Cycle 12, otherwise, those channels will need to be followed separately so Slack can actually be shut down.

/cc bisq-network/compensation#513

[m52go]

Cycle 12 Report

I stopped using Slack entirely, using separate means to occasionally follow IRC and Matrix. Slack can now really really be shut down, but I think only the primary workspace owner can do it, so I'll need to arrange for that to happen. Once that's done, this role can be closed.

/cc bisq-network/compensation#540

[m52go]

The Slack workspace was deleted during the past cycle, so this role is no longer relevant. @cbeams this issue can probably be closed.

https://bisq.slack.com

[m52go]

@cbeams this issue can be closed.

[cbeams]

Closed as no longer relevant, thanks @m52go.