Bisq has had a Keybase team since @cbeams created it a couple years back, and since then over 100+ people have joined it. A few months ago @cbeams set me as the "admin" and I created some new channels and added a bunch of people and now we are starting to see daily conversations. However as the Keybase team gets used more, and especially in light of #127, I think we should formalize the role and responsibilities.
Keybase Administrators
This role would held by primary @wiz (current keybase admin) and secondary @m52go (current slack admin).
The goal for this role is to maintain the Keybase channels, ban abusive users, and generally grow the Bisq community on Keybase and promote useful collaboration between the users.
Role Issue
TBD upon approval
Role Team
TBD upon approval
Duties
Moderate channels
Remove abusive users
etc.
Rights
N/A; no additional GitHub rights.
Bond
0 BSQ
Other Considerations
Ongoing costs will be based on work delivered.
Bisq has had a Keybase team since @cbeams created it a couple years back, and since then over 100+ people have joined it. A few months ago @cbeams set me as the "admin" and I created some new channels and added a bunch of people and now we are starting to see daily conversations. However as the Keybase team gets used more, and especially in light of #127, I think we should formalize the role and responsibilities.
Keybase Administrators
This role would held by primary @wiz (current keybase admin) and secondary @m52go (current slack admin).
The goal for this role is to maintain the Keybase channels, ban abusive users, and generally grow the Bisq community on Keybase and promote useful collaboration between the users.
Role Issue
TBD upon approval
Role Team
TBD upon approval
Duties
Rights
N/A; no additional GitHub rights.
Bond
0 BSQ
Other Considerations
Ongoing costs will be based on work delivered.