2020-04-09 @team-leads call

cbeams commented 4 years ago

Previous call with an agenda was #58. We started doing these calls bi-weekly recently. We skipped one call, and did another one informally without an agenda.

Agenda

Next steps with response to Apr 7th incident

Do 1:1s with individual victims

[x] @cbeams to ask mediators to put victims in touch with him
[x] @cbeams to do 1:1 calls with (willing) individual victims

Discuss chimp's repayment proposal at https://github.com/bisq-network/proposals/issues/205

[ ] Continue offline discussing different proposals

Establish new security practices

Formalize security process

bisq.security subteam?
security officer/committee/panel role/team?
bug bounty program
create, e.g. bisq-security@protonmail.com address (for responsible disclosure, etc)
establish new internal commitments around how we deal with security issues / reports

Commission security review

[ ] Commission pragmatic security review of trade protocol
- [ ] @cbeams to reach out to candidate

Issue follow-up communications

[x] @m52go to publish initial blog post at https://bisq.network/statement-security-vulnerability-april-2020 (https://github.com/bisq-network/bisq-website/pull/361)
[ ] Plan next communications (regarding new security practices, repayment proposal, etc)

Unfail trades PR

[x] @wiz to discuss getting https://github.com/bisq-network/bisq/pull/3809 merged after all to deal with current support issues
[ ] @sqrrm to finish putting together new unfail patch PR
[ ] @ripcurlx to put together one-off binary with unfail PR patched in asap
[ ] @cbeams to communicate that to victim #1
[ ] announce in bisq.support subchannel so all agents / mediators can get this to their people

~Refund Agent~ Arbitration role hand-off and documentation

[ ] @cbeams and @m52go to discuss new documentation https://github.com/bisq-network/admin/issues/70#issuecomment-607890856
[ ] @cbeams and @wiz to discuss candidates for taking the role over
[ ] HIGH-PRI: we must find candidates for this
[ ] Have a follow up call about nailing down how arbitration will work going forward. Wiz, cbeams.

Hand off support lead role

[ ] @cbeams to discuss

Simplifying compensation requests starting in Cycle 13

[ ] @cbeams to discuss plan to simplify compensation request format in such a way that makes budget accounting more automatable

Git LFS PR

[ ] @cbeams to discuss getting the Git LFS PR merged, green light $120 a year paid by GitHub Admin role for sufficient (2) GitHub LFS storage data packs. https://github.com/bisq-network/bisq/pull/4114

API

[ ] @cbeams to give update

cbeams availability / priorities

[ ] @cbeams to give update about his availability, priorities, things to be handed off or dropped
- Following up on Q1 update,

cbeams commented 4 years ago

@bisq-network/team-leads, please do your best to review the agenda above and familiarize yourself with the linked issues before the call. Please add any agenda items here as comments.

m52go commented 4 years ago

Issue follow-up communications

I forgot to mention this on the call, but I think it's important that we publish a thorough and thoughtful post-mortem when it's possible to do so.

If desired, I can open an issue with pre-requisites for this post (i.e., what needs to be decided/finished before writing it) along with points we want to hit.

bisq-network / admin