gobot.io/x/gobot/v2@v2.1.0/ROADMAP.md (about) 1 # Roadmap 2 3 This is the roadmap of what we as a community want to see happen with Gobot. It should be considered more as a statement of direction then a list of tasks. 4 5 Requests for changes to the roadmap should be made in the form of pull requests to this document. 6 7 Anything tied to any implementation, including requests for platform support, bug reports, or other specifics should still be made by creating a new issue here: 8 9 <https://github.com/hybridgroup/gobot/issues> 10 11 ## core 12 13 - standardized logging 14 - use Context to allow for graceful exits. 15 16 ## api 17 18 - ability to plug in your own router to handle API calls, for example to serve a custom web app. 19 - restrict API calls to only specific set of entrypoints. 20 - serve other transports/protocols other than HTTP/REST for example CoAP. 21 22 ## gpio 23 24 - support for epoll/interrupt based gpio events. 25 - helper method for interrupts to handle "ping" timing-based devices. 26 - Windows 10 support. 27 - use variadic constructor functions to allow for additional params, similar to i2c drivers. 28 29 ## aio 30 31 - support for epoll based aio events possible? 32 - Windows 10 support. 33 - use variadic constructor functions to allow for additional params, similar to i2c drivers. 34 35 ## i2c 36 37 add support for the following i2c devices: 38 39 - MAG3110 40 - MMA8452 41 - T5403 42 - TMP006 43 - VCNL4000 44 45 ## 1-wire 46 47 - add support for 1-wire protocol. 48 49 ## serial 50 51 - create a common serial Adaptor, so different serial devices such as GPS, LIDAR etc only need to implement drivers. 52 53 ## ble 54 55 - improve the ble package to allow support for multiple peripherals. 56 - Windows 10 support.