Skip to content

hashmesan june 2022 #152

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.

Sign up for GitHub

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

Open
hashmesan wants to merge 1 commit into
base: main
Choose a base branch
from
Open

hashmesan june 2022 #152

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
26 changes: 26 additions & 0 deletions eng/hashmesan/june2022.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,26 @@
# Summary
* Owner: hashmesan
* Dates: 6/1-7/1
* Total: 91 hours
* Overtime: 0 hours
* Github: github.com/hashmesan

| date | work completed with details and links | hours |
|-----------|-------------------------------------------------------------------------------------------|-------|
| 6/6/2022 | Developer growth planning | 2 |
| 6/7/2022 | Developer Growth meeting and planning | 2 |
| 6/9/2022 | Locked collateral staking design (https://github.com/harmony-one/onebtc/issues/106) | 3 |
| 6/10/22 | Locked collateral staking design part 2(https://github.com/harmony-one/onebtc/issues/106) | 3 |
| 6/2/2022 | Elasticsearch OPS / diagnose downtime | 6 |
| 6/10/2022 | Elasticsearch OPS / diagnose downtime | 3 |
| 6/13/2022 | Query ES data for consensys | 1 |
| 6/18/2022 | Response/investigate hack case | 2 |
| 6/20/2022 | Query security case | 1 |
| 6/23/2022 | Incident response | 5 |
| 6/24/2022 | Incident response | 6 |
| 6/25/2022 | Incident response | 3 |
| 6/27/2022 | Incident response | 9 |
| 6/28/2022 | Incident response | 11 |
| 6/29/2022 | Incident response | 12 |
| 6/30/2022 | Incident response | 12 |
| 7/1/2022 | Incident response | 10 |