For deadlines, I’ll use the convention that a given day means the end of that day in local time.
Required tasks
0. Derive daily schedule from this plan to see if it actually fits and with enough openings for the unplanned; update if needed. Due Tuesday (though probably should have been done already).
1. Issue WoT ratings: 1h. Due Tuesday.
2. Re-genesis yrc and keksum to include patch name prefix: 0.5h. Due Tuesday.
3. Finish accounting from Uruguay trip: 0.5h. Due Friday.
4. Catch up on #ossasepia log (6th-9th): 1h. Due Tuesday. (So far I’ve just skimmed).
5. Catch up on #trilema log. It’s looking to be on the heavy side; I’m thinking to skim and focus just on parts that seem relevant to me, understanding that this isn’t ideal. 6h as a wild guess. Due Thursday Friday.
6. Digest the extensive comments MP gave on my blog, at least for a first pass: 2h. Due Thursday Wednesday.
7. Catch up on remaining feeds: 4h as a wild guess.
8. Wallet: finish online component’s commands: 5h, due Wednesday Friday.
9. Wallet: start work on offline component: 8h.
11. Take delivery of FG parts shipped from USA (should be quick but hard to predict timing).
12. Daily blogging: 0.5h prep + 1.5h daily. Initial topics to include: reflections and photos from Uruguay trip; preliminary analysis of the polarbeard “sendrawtransaction” patch.
13. Forum reading + interaction: 3h/day.
14. Next weekly review + plan: 4h, due Sunday but preferably Saturday.
15. Training session: 2h, 21:00 UTC Wednesday.
Time permitting
15 16. Test newly acquired iron: 2h.
3 17. Finish accounting from Uruguay trip: 0.5h. Needs done next week for sure.
I’ve made a detailed schedule per #0 and indeed it’s still quite packed; the only slack I’m seeing here is whatever might exist in #13. Updated some deadlines accordingly; in particular and otherwise:
#6 seems a higher priority than #5, it being my own blog and all.
For #11, the courier I used is one of the smaller operations and only delivers once a week; I’m assured this will happen next Monday.
I had missed noting #15 altogether.
#3 moved to time permitting.
Comment by Jacob Welsh — December 11, 2019 @ 4:47 am
At this time I suppose the #t log can wait for after the wallet deadline, if need be. But in any case, it seems to have been useful to you to do this more detailed plan.
Comment by Diana Coman — December 12, 2019 @ 7:04 pm