TASKS.md

README.md

@@ -66,7 +66,7 @@ What the 01 will be able to do.
 
 ### [Tasks ↗](https://github.com/KillianLucas/01/blob/main/TASKS.md)
 
-Our master task list, seperated by week.
+Our master task list.
 
 ### [Teams ↗](https://github.com/KillianLucas/01/blob/main/TEAMS.md)
 

TASKS.md

@@ -1,48 +1,40 @@
-# Tasks
+**OI**
-
+
-## Week 1 (Jan 15th)
+1. Finish skill library.
-
+   1. Create a system message that includes instructions on how to use the skill library.
-- [x] Create a typeform that asks for skills/interests/city
+   2. Test it end-to-end.
-- [x] Secure a venue for our first meetup in Seattle
+   3. Create computer.skills.teach(), which displays a message asking users to complete the task via voice in the most generalizable way possible. OI should use computer.mouse and computer.keyboard to fulfill each step, then save the generalized instruction as a skill. Clicking the mouse cancels teach mode. When OI invokes this skill in the future, it will just list those steps (it needs to figure out how to flexibly accomplish each step).
-- [x] Create a presentation
+   4. Expose ^ via `interpreter --teach`.
-- [x] Meet on Jan 20th
+2. Add `interpreter --server --expose`.
-- [x] Invite everyone to the Discord server, update it
+   1. Include the 01's --server in the next OI update.
-- [x] Finish notes of the first meetup
+   2. Add --server --expose which will expose the server via something like Ngrok, display the public URL and a password, so the 01 Light can connect to it. This will let people use OI on their computer via their Light — i.e. "Check my emails" will run Applescript on their home computer.
-
+3. Why is OI starting so slowly? We could use time.time() around things to track it down.
-## Week 2 (Jan 22nd)
+4. Create moondream-powered computer.camera.
-
+   1. Computer.camera.view(query) should take a picture and ask moondream the query. Defaults to "Describe this image in detail."
-- [x] Research pre-made hardware
+
-- [x] Sketch out the 01 OS architecture
+**OS**
-- [x] Secure a venue for our second meetup
+
-
+1. Swap out the current hosted functions for local ones.
-Meetup goals:
+   1. TTS — Piper? OpenVoice? Rasspy?
-
+   2. STT — Whisper? Canary?
-- [x] Split into teams
+   3. LLM — Phi-2 Q4 Llamafile, just need to download it, OI knows how to use Llamafiles
-- [x] Make a master task list, split by team
+2. If Light and no internet, open a captive wifi page with text boxes: Wifi Name, Wifi Pass, (optional) Server URL, (optional) Server Pass
-- [x] 01OS basic functionality
+3. Can tapping the mic twice = pressing the "button"? Simple sensing, just based on volume spikes?
-
+4. Add basic TUI to device.py. Just renders messages and lets you add messages. Can easily copy OI's TUI.
-## Week 3 (Jan 29th)
+5. Replace bootloader and boot script— should just run 01, full screen TUI.
-
+6. Package it as an ISO, or figure out some other simple install instructions. How to easily install on a Pi?
-- [ ] 01OS full functionality
+
-- [ ] Start building the skill library
+**Hardware**
-- [x] Order some hardware
+
-- [ ] Secure a venue for our third meetup
+1. (Hardware and software) Get the 01OS working on the Jetson or Pi. Pick one to move forward with.
-
+2. Connect the Seeed Sense (ESP32 with Wifi, Bluetooth and a mic) to a small DAC + amplifier + speaker.
-Meetup goals:
+3. Connect the Seeed Sense to a battery.
-
+4. Configure the ESP32 to be a wireless mic + speaker for the Jetson or Pi.
-- [ ] Test the 01OS on a bunch of different hardware, document constraints
+5. Connect the Jetson or Pi to a battery.
-- [ ] Sketch out the video, launch materials
+6. Make a rudimentary case for the Seeed Sense + speaker. Optional.
-
+7. Make a rudimentary case for the Jetson or Pi. Optional.
-...
+
-
+Misc.
-## Week 4 (Feb 5th)
+
-
+1. Develop default system message for executive assistant.
-...
+2. Determine recommended minimal hardware for the light & heavy.
-
-## Week 5 (Feb 12th)
-
-...
-
-## Week 6 (Feb 19th)
-
-- [ ] **Launch the 01.**