Skip to content

Instantly share code, notes, and snippets.

@w0000000t

w0000000t/support_report.md

Last active January 19, 2022 17:50
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save w0000000t/81ee4fccf4c9c4647abcdc57d51d730e to your computer and use it in GitHub Desktop.
Save w0000000t/81ee4fccf4c9c4647abcdc57d51d730e to your computer and use it in GitHub Desktop.
Download ZIP
Bisq / L1 Support Agent / Report template
Raw
support_report.md

Cycle N

Support activity on ... ["keybase", "matrix", "forum", "telegram", "reddit", "github"]

Case (C): support situation requiring 10+ minutes of assistance Request (R): support situation requiring from a single to a few replies Example: 2022/01/01 2R [two requests] matrix; 1C keybase (user had problem X, suggested to do Y and Z, problem was solved)

Details
  • 2022/01/17 1C keybase (couldn't connect, had v2 onion, instructed to move to v3)
  • 2022/01/18 2R telegram; 1R matrix
@w0000000t
Copy link
Author

Please leave comments to direct edits; myself, I think I will keep compiling it verbosely for my own reports, day-by-day and with time intervals, but I see how someone else would prefer making it shorter and only report days with significant events; in this case, you can just trim it down removing the unneeded fields.

@w0000000t
Copy link
Author

New update to remove the "overblown" effect, as per 2022/01/19 support meeting.

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