It's time again to take a state of the union and look at my various toy projects, their scope & state, how they intersect and what/where to go next. I'd like to take one and finalize it. But the first question is what am I trying to achieve, and how these project fulfil that?

Side note: this is a summary. I need to organize my project management too (yet another task) and maybe something like Trello or docs would be useful. Main issue to solve here is fragmentation of the info in different silos and lack of cross-linking.

Projects, in no particular order:

• Timeriffic 2
• Ikaria
• Cloud Bus
• Timer2 (aka T3 the reboot)
• Pixel game
• JS chrome offline app
• Home Music
• Home monitor
• Monitor webcam proxy
• Rig4mm

What I want/need, mostly in this order:

• Useful: Fix Music because I need it, not for the tech itself.
• Useful: Write the webcam proxy because I need it too, although it's a P2 at most.
• Only useful if I follow up with the HMon app rewrite.
• Write CloudBus phase 0 as a base foundation, not much to learn here..
• It's not clear how successful phase 0 would be, so interesting part is understand limitations & usage first. That is, have concrete usage scenarios for it.
• Ikaria is essentially a learning project. It's all about creating a base foundation that I can reuse whilst respecting guidelines and experimenting with testing.
• Same as with CloudBus, part of the design is understanding applications of it.
• Pixel game is the main "client" of Ikaria at this point.
• Timer2 as a T3-reboot is mostly a no-go for now.
• Timeriffic2 has been closed for a while.