-
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 #79
Comments
@m52go Is it OK if I assign you for now. Once we migrate we need to check out who will actually take the role.... |
@m52go since this was never implemented and we're on keybase now how about we close this role |
Closing as dropped. I believe nothing ever happened with Rocket Chat and Keybase has become our chat hub in the meantime. |
okay so close the keybase issue and rename this one to keybase and change the strings in the app to say keybase instead of rocket chat |
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.
Per @wiz's plan at #79 (comment):
|
Cycle 13 ReportNothing particularly notable to report, aside from an overzealous altcoiner who added a lot of Bisq people to their own Keybase team. Keybase the company was acquired. |
Cycle 13 reportI have proposed to post bond as the Keybase team owner in bisq-network/proposals#223. Nothing else to report. |
Cycle 14 reportA proposal has been submitted at bisq-network/proposals#232 for @kbteamowner to take over this role from me. I will continue to own the role until their proposal is approved and their bond is posted. At that time, I'll hand over ownership of the Keybase team to them and remove the owner role from my user. Assuming everything goes to plan, this will be my last cycle report, and @kbteamowner will report here going forward. |
Per bisq-network/proposals#232 (comment), I have just made @kbteamowner the owner of the Bisq keybase team. For some reason, though, I am unable to assign them to this issue. I have removed myself as an assignee in any case. |
Cycle 15 reportAs mentioned above, this role has been handed off to @kbteamowner, and this will be my final cycle report. Note that I have successfully removed myself from this issue now (I was unable to do so before, as mentioned above). I have also removed myself from the @bisq-network/keybase-admins team and granted @kbteamowner the Maintainer role there. |
Owners and Admins of the public
bisq
Keybase team at https://keybase.io/team/bisqDocs: https://bisq.wiki/Keybase
Team: @bisq-network/keybase-admins
The text was updated successfully, but these errors were encountered: