-
Notifications
You must be signed in to change notification settings - Fork 16
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
Keybase Admin #60
Comments
2017.12 reportI set up the We now have 10 members in the team, but no real activity yet. We'll see where this goes. |
2018.01 reportOur |
2018.02 reportNothing to report. |
2018.03 reportNothing to report. |
2018.04 reportNothing to report. |
2018.05 reportNothing to report. |
Do you think its worth to keep that channel? |
2018.06 reportFinal report (for now). I'm closing this issue as no one is using the Keybase |
Reopening as the Keybase group is now seeing more activity. |
Cycle 7 reportThe Bisq team has been restarted, and the community has mostly migrated from Slack to Keybase for the security and privacy it provides. I've taken over the Keybase Admin role together with @m52go, and we are gaining more users every day. Keybase is great! |
@cbeams actually if you check bisq-network/proposals#128 you can see @m52go was assigned secondary keybase admin role with me... but if you really want to fire him, we can do that too! 🔥 |
Yeah, this was my bad. @m52go pinged me about it as well. I've re-added him to @bisq-network/keybase-admins and re-assigned him here. Sorry, Steve. |
Per bisq-network/roles#79 (comment) Note that the ROCKET_CHAT_ADMIN enum label has not been renamed for the backward compatibility reasons discussed in BondedRoleType Javadoc. See also bisq-network/roles#60.
Closing as superseded by the new Keybase Admin role at #79 (formerly Rocket Chat Admin, see #79 (comment) for details why it was necessary to do this). |
Closed as superseded by #79.
The text was updated successfully, but these errors were encountered: