New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Slack Admin #23

Open
cbeams opened this Issue Sep 4, 2017 · 21 comments

Comments

Projects
None yet
4 participants
@cbeams
Member

cbeams commented Sep 4, 2017

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


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

@cbeams

This comment has been minimized.

Member

cbeams commented Nov 20, 2017

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 cbeams changed the title from Slack team operator to Slack workspace owner Nov 20, 2017

@cbeams cbeams referenced this issue Dec 18, 2017

Closed

Create #slack infrastructure #19

9 of 9 tasks complete
@cbeams

This comment has been minimized.

Member

cbeams commented Dec 18, 2017

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 added a commit that referenced this issue Jan 2, 2018

cbeams added a commit that referenced this issue Jan 2, 2018

@cbeams cbeams changed the title from Slack workspace owner to Slack Admin Jan 2, 2018

@cbeams cbeams added role and removed role:op labels Jan 3, 2018

@cbeams

This comment has been minimized.

Member

cbeams commented Jan 4, 2018

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.

screencapture-bisq-slack-admin-stats-1515073313463

/cc bisq-network/compensation#26

@cbeams cbeams referenced this issue Jan 4, 2018

Closed

For December 2017 #26

@ManfredKarrer

This comment has been minimized.

Member

ManfredKarrer commented Jan 4, 2018

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

@cbeams

This comment has been minimized.

Member

cbeams commented Jan 8, 2018

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

Per month, given our current number of active users.

@cbeams

This comment has been minimized.

Member

cbeams commented Feb 1, 2018

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:

image

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:

screencapture-bisq-slack-admin-stats-1517445943399

/cc bisq-network/compensation#35

@cbeams cbeams referenced this issue Feb 1, 2018

Closed

For January 2018 #35

@cbeams

This comment has been minimized.

Member

cbeams commented Mar 1, 2018

2018.02 report

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

screencapture-bisq-slack-admin-stats-1519866154081

/cc bisq-network/compensation#40

@cbeams cbeams referenced this issue Mar 1, 2018

Closed

For February 2018 #40

1 of 1 task complete
@cbeams

This comment has been minimized.

Member

cbeams commented Apr 4, 2018

@cbeams cbeams referenced this issue Apr 4, 2018

Closed

For March 2018 #57

1 of 1 task complete
@cbeams

This comment has been minimized.

Member

cbeams commented May 3, 2018

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.

screencapture-bisq-slack-admin-stats-2018-05-03-19_26_47

/cc bisq-network/compensation#68

@cbeams cbeams referenced this issue May 3, 2018

Closed

For April 2018 #68

1 of 6 tasks complete

@cbeams cbeams removed the a:role label May 4, 2018

@cbeams

This comment has been minimized.

Member

cbeams commented Jun 1, 2018

2018.05 report

We're now at 602 members.

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

screencapture-bisq-slack-admin-stats-2018-06-01-14_42_23

/cc bisq-network/compensation#74

@cbeams cbeams referenced this issue Jun 1, 2018

Closed

For May 2018 #74

0 of 5 tasks complete
@cbeams

This comment has been minimized.

Member

cbeams commented Jun 30, 2018

2018.06 report

We're now at 616 members. Interesting to note in the stats below that our "Weekly active users posting messages" has been hovering at around 30 for as long as we've been capturing these reports. So while the number of people joining the workspace grows, the number of people actively using it has pretty much stayed the same.

screencapture-bisq-slack-admin-stats-2018-06-30-19_04_17

/cc bisq-network/compensation#89

@cbeams cbeams referenced this issue Jun 30, 2018

Closed

For June 2018 #89

6 of 6 tasks complete
@cbeams

This comment has been minimized.

Member

cbeams commented Jul 31, 2018

2018.07 report

I have a hunch that no one cares about the Slack analytics screenshots that I post here every month, so I'm going to leave it out this month and see if anybody asks for it back.

Otherwise, nothing to report.

BSQ requested: 25

/cc bisq-network/compensation#101

@cbeams cbeams referenced this issue Jul 31, 2018

Closed

For July 2018 #101

@ripcurlx

This comment has been minimized.

Member

ripcurlx commented Jul 31, 2018

I am mainly interested in the information of new members added every month for the analytics report. But as this information is not visible in the free plan I deduct the couple of members that were added in the following month (e.g. August) to get the increase of July. Of course this works only as long as we don't add more than 6 new users until I gather the report.

@cbeams

This comment has been minimized.

Member

cbeams commented Aug 31, 2018

2018.08 report

Nothing to report.

screencapture-bisq-slack-admin-stats-2018-08-31-16_33_27

BSQ Requested: 25

/cc bisq-network/compensation#114

@cbeams

This comment has been minimized.

Member

cbeams commented Sep 30, 2018

2018.09 report

Nothing to report.

screencapture-bisq-slack-admin-stats-2018-09-30-17_14_00

BSQ Requested: 25

/cc bisq-network/compensation#139

@ManfredKarrer

This comment has been minimized.

Member

ManfredKarrer commented Oct 31, 2018

2018.10 report

There have been a case of a scammer who impersonated my slack account and tried to trick people into stupid scam. The users contacted me and sent me the conversation. He also mentioned cbeams in that conversation.
I was quite shocked to disover that Slack has zero protection against such impersonation scams. One can simple set the user name and deplay name to my name, add profile pic and it looks like the same account. I reported to Slack and they said they forwared it to their dev. Shocking to see that they have zero consciousness for security!
I strongly would be in favor that we get rid of slack. Beside that severe risk there is the annoying business model where your get locked out of your own content if you don't pay their hefty fees for the pro plan.

As soon any contributor will make it his project to operate a Slack alternative I am in favor to move. But it must happen in a way that it does not consume time from the core contributors and founders as we are too busy with other things....
I must also be one who has a good reputation already as it would include probably hosting and we need to have a certain trust on reliability to that person.

/cc bisq-network/compensation#155

@cbeams

This comment has been minimized.

Member

cbeams commented Oct 31, 2018

2018.10 report

@ManfredKarrer wrote:

As soon any contributor will make it his project to operate a Slack alternative I am in favor to move.

I've just created a WIP proposal for this at bisq-network/proposals#54.

Here are this month's analytics, from https://bisq.slack.com/admin/stats:

screencapture-bisq-slack-admin-stats-2018-10-31-21_58_39

BSQ Requested: 25

/cc bisq-network/compensation#160

@cbeams

This comment has been minimized.

Member

cbeams commented Nov 27, 2018

I've made @m52go a Slack admin, at least for the time being, so as to facilitate data migration to the new Rocket.Chat instance.

@ManfredKarrer

This comment has been minimized.

Member

ManfredKarrer commented Nov 30, 2018

2018.11 report

Helping to get the migration to Rocket.chat organized.

/cc bisq-network/compensation#180

@cbeams

This comment has been minimized.

Member

cbeams commented Nov 30, 2018

2018.11 report

@chirhonul and @m52go stepped up this month to start building out a Rocket.Chat alternative to Slack. A role for Rocket.Chat Admin has been created at #79. To follow what's going on there, see bisq-network/proposals#54. In the meantime, here are our Slack stats for this month:

screencapture-bisq-slack-admin-stats-2018-11-30-21_59_31

BSQ requested: 25

/cc bisq-network/compensation#179

@cbeams

This comment has been minimized.

Member

cbeams commented Dec 7, 2018

@m52go has agreed to take on the role of Slack Admin. I already gave him admin access to Slack (see #23 (comment)), and I've now removed myself as an admin completely. Thanks Steve!

@cbeams cbeams removed their assignment Dec 7, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment