Updated 2024-05-13
This commit is contained in:
parent
dc3b9dc2ab
commit
ea9f161392
|
@ -0,0 +1,39 @@
|
|||
# 2022-05-13
|
||||
|
||||
## Scoping
|
||||
|
||||
- Wallet Router
|
||||
- I began work on reading and building context of the Route `status-go` logic.
|
||||
- This work is tricky to track, but I have begun making notes of the logic. I plan to continue to build out a description or documentation detailing the analysis.
|
||||
- Torrent dependencies in mobile build
|
||||
- https://github.com/status-im/status-go/issues/5146
|
||||
- Scope work for this issue requires more time, I've identified the imports and dependencies for implementing the backup distribution logic.
|
||||
|
||||
|
||||
## Schedule
|
||||
- [x] 10:30 – 11:30 : Discussion and sync with Sale about planning and scoping of Wallet Router work.
|
||||
- Discussion giving context on the structure of the Router
|
||||
- Discussed work done last week in : https://github.com/status-im/status-desktop/issues/14638
|
||||
- We decided that we need to:
|
||||
- spend time understanding the code
|
||||
- determine what work can be parallelised
|
||||
- [x] 12:00 – 12:30 : Wallet Router Sync
|
||||
- https://meet.google.com/amj-krdp-dta
|
||||
- **Attendees:**
|
||||
- Alisher
|
||||
- Andrea
|
||||
- Emil
|
||||
- Ivan
|
||||
- Jamie
|
||||
- Sale
|
||||
- Myself
|
||||
- **Notes**
|
||||
- Discussed what should be priorities
|
||||
- Decided the following:
|
||||
- Scope the Wallet Router to understand the logic
|
||||
- Tests should be writen to validate any changes the Router code, but we do not build tests out without introducing changes.
|
||||
- Tests can be written in the context of demonstrating / exploring how code works.
|
||||
- Alisher was meant to present the product expectations, but we ran out of time.
|
||||
- [x] 14:30 – 15:00 : team update
|
||||
- https://meet.google.com/vnx-agcb-nao
|
||||
- A very sombre meeting, discussing the recent layoffs
|
|
@ -1,7 +1,7 @@
|
|||
# Tags
|
||||
|
||||
| Name | Description |
|
||||
| ------------- | ---------------------------------------------------------------- |
|
||||
|---------------|------------------------------------------------------------------|
|
||||
| `addressed` | Denotes that an item has received resolving attention |
|
||||
| `approved` | Related to Pull Request (PR) requests for review |
|
||||
| `closed` | Denotes that an item was closed to further discussion |
|
||||
|
@ -22,4 +22,4 @@
|
|||
| `scoping` | Denotes that an item was scoped for how much work needs doing |
|
||||
| `submitted` | Denotes that an item was submitted for review |
|
||||
| `watched` | Denotes that an item was watched. Example a video lecture |
|
||||
| `voted` | Denotes that an item was voted on. Example feature prioritising |
|
||||
| `voted` | Denotes that an item was voted on. Example feature prioritising |
|
||||
|
|
Loading…
Reference in New Issue