- Build effective working groups that completed their tasks with measurable results. Celebrate the work of each of the working groups
- Documentation upgrade (fritzing examples, API prototypes, some calls are missing line pin interrupts/pulldowns etc.)
- Update the
tessel.io
website, it's too "business-y", need to change expectations to an OS project. It's not just something for hardware, it's for everyone to get involved in (including designers, web devs who don't have specific interest in microcontrollers). Would be good to also make it easier to put out updates. Change the CTA from "Order" to "Contribute". Include compatibility to J5 and the J5IK. Reconsider the "Trusted By" section. Would be great to be able to have links to educational material (ie Sparkfun's endeavors)
- USB to module port (including kevinmehall/starfish)
- Explore possibility of better working with web APIs (like canvas, etc.)
- Making CLI extensible to other hardware platforms
2) Demonstrate projects and create new tools that prove Tessel is a production-ready (robust, reliable, and extensible) platform for modern hardware development
- Guide to production-scale deployment
- Research group: What do people need to use T2 in production? Why aren't they using it?
- Build Reach
- Tessel 2.1, Minor hardware revision: more RAM and Flash: legitimize the platform and build out the capabilities so there is less user experience friction
- Rust API parity, documentation, and JS-Rust inter-exection
- Mesh Communication API: this would open up the use case scenarios and create a differentiating factor for T2 that other platforms just don't have
- PouchDB Support: this would get our users the ability to use a legitimate database on T2
- T3 where we completely update the chips, memory, etc. potentially shoot for ARM-based, cheaper
- FPGA-based alternative
- Logic Analyzer (building an actual logic analyzer)
- Fractal
- More modules?
Have done in a year's time:
Not have done in a year's time: