Git-Mirrors/Reticulum
1
0
Fork 0
mirror of https://github.com/markqvist/Reticulum.git synced 2024-10-01 03:15:44 -04:00
Code Issues Actions Packages Projects Releases Wiki Activity

Updated roadmap

Browse Source
This commit is contained in:
Mark Qvist 2023-10-01 23:46:01 +02:00
parent f79f190525
commit 875348383d
1 changed files with 10 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
Roadmap.md
View File

@ -14,14 +14,14 @@ This document outlines the currently established development roadmap for Reticul
## Currently Active Work Areas ## Currently Active Work Areas
For each release cycle of Reticulum, improvements and additions from the five [Primary Efforts](#primary-efforts) are selected as active work areas, and can be expected to be included in the upcoming releases within that cycle. While not entirely set in stone for each release cycle, they serve as a pointer of what to expect in the near future. For each release cycle of Reticulum, improvements and additions from the five [Primary Efforts](#primary-efforts) are selected as active work areas, and can be expected to be included in the upcoming releases within that cycle. While not entirely set in stone for each release cycle, they serve as a pointer of what to expect in the near future.
- The current `0.5.x` release cycle aims at completing - The current `0.6.x` release cycle aims at completing
- [x] Reach feature-completion of the Reticulum API
- [x] Improve performance and efficiency of the `Buffer` and `Channel` API
- [x] Add bluetooth pairing code output to rnodeconf
- [ ] Overhauling and updating the documentation - [ ] Overhauling and updating the documentation
- [ ] Performance and memory optimisations of the Python reference implementation - [ ] Distributed Destination Naming System
- [ ] Fixing potential bugs - [ ] Create a standalone RNS Daemon app for Android
- [ ] Network-wide path balancing
- [ ] Add automatic retries to all use cases of the `Request` API - [ ] Add automatic retries to all use cases of the `Request` API
- [ ] Performance and memory optimisations of the Python reference implementation
- [ ] Fixing bugs discovered while operating Reticulum systems and applications
## Primary Efforts ## Primary Efforts
The development path for Reticulum is currently laid out in five distinct areas: *Comprehensibility*, *Universality*, *Functionality*, *Usability & Utility* and *Interfaceability*. Conceptualising the development of Reticulum into these areas serves to advance the implementation and work towards the Foundational Goals & Values of Reticulum. The development path for Reticulum is currently laid out in five distinct areas: *Comprehensibility*, *Universality*, *Functionality*, *Usability & Utility* and *Interfaceability*. Conceptualising the development of Reticulum into these areas serves to advance the implementation and work towards the Foundational Goals & Values of Reticulum.
@ -40,12 +40,12 @@ These efforts are aimed at improving the ease of which Reticulum is understood,
- Update NomadNet screenshots - Update NomadNet screenshots
- Update Sideband screenshots - Update Sideband screenshots
- Installation - Installation
- Add a *Reticulum On Raspberry Pi* section - [x] Add a *Reticulum On Raspberry Pi* section
- Update *Reticulum On Android* section if necessary - [x] Update *Reticulum On Android* section if necessary
- Update Android install documentation. - [x] Update Android install documentation.
- Communications hardware section - Communications hardware section
- Add information about RNode external displays. - Add information about RNode external displays.
- Packet radio modems. - [x] Packet radio modems.
- Possibly add other relevant types here as well. - Possibly add other relevant types here as well.
- Setup *Best Practices For...* / *Installation Examples* section. - Setup *Best Practices For...* / *Installation Examples* section.
- Home or office (example) - Home or office (example)