Roadmap discussion:
- FreedomBox in Debian installer. Current status of the discussion in Debian. What can we do?
- FreedomBox blog/news. FreedomBox updates should become part of Debian planet to reach more Debian developers.
- Next generation hardware. How to help existing partner and bring new partners. FreedomBox can play multiple roles at home and become much more enticing for buyers. This is, however, secondary compared to the primary goal of protecting privacy and digital rights.
- Contribution/donation links for each app. Encourage user connection and contribution to upstream projects.
- Show app maintainers. Acknowledge the work for app maintainers. Invite contributors to pick more responsibility.
- SPDX license header. Simplify license headers using SPDX license identifiers in source code.
- Drop outdated apps. Apps disabled for 1 year and with no prospects of re-addition should be dropped. This eases some framework level changes.
- Nextcloud. Is Debian fasttrack as suitable answer for Nextcloud? If not can we use Snaps? What should be expected from an app that is added to FreedomBox implemented using Snaps or similar approach? (Security updates, data storage location, backup/restore, duplication of services such as database, webserver and letsencrypt)
- Fediverse. What should be our priorities?
- Documentation Wiki. Problems with current wiki approach for creating manual. How to do this in future?
Technical discussion
- Future components. Are components working out alright. Plan for introducing new components (info, user groups) and component level actions (diagnostics, setup). Further clean up of code using components (app.init, module loader) and using manifests to automatically create components in a app.
- Functional tests. Has using English like description served us better than would be otherwise possible? Should we allow alternatives. Split tests and their utilities into individual apps. Speed up functional tests by avoiding wait times for negative queries and unnecessary re-navigation to app pages.
- Toolbar UX. Consolidation of ideas around of UX improvements using a toolbar.
- Running actions from DBus. Instead of using the command line, we could consider D-Bus protocol for performing superuser operations. Command line interactions are retained and will be exposed as in a simple, uniform way in the level of framework. This will eliminate a lot of boilerplate code and will eliminate issues such as problems when passing secrets. Further it will provide better performance as loading python interpreter for each command results in very large number of system calls.
Edit 1: Add documentation wiki item.